Scattered like the debris after a Kansas tornado, they are. Not to mention, there isn't consistency to where they are between firmware revisions for the same drive, much less for firmware versions of two different drives.

Sure, but you have to know how and where they are stored, and that is the problem. Reengineering the table layout might take about 2-4 weeks for the first firmware and another week for each firmware with a different layout plus about 1-2 days for each firmware revision to figure out if it is a known layout. Of course you never can be sure that you really found all tables.
This is what I mean with 'it is not maintainable'.

oh, that sucks

@ala42 - in the other forum you took a look at one of the firmwares for a LVW-5005 supplied by thrunner. Think Media Code Speed Edit will work?

I figured I post this question in the Media Code Speed Edit Forum

Thanks

...and the DDW-451S firmware looks a bit like the LDW-451S firmware, big surprise...

It should. At least it dumps the tables without any problem, including the unexpected +R9 codes. Btw, Omnipatcher detected the DDW813 firmware as 1633 class, which matches the SONY DW-D22A id inside the firmware.

@code65536 and ala42 - we might be on to something here that'll bring a lot of needed help to us 5005 users. YYIIIPPPPPEEEE!!!!!


And the ddw-451s firmware id as ldw-451s/851s in omnipatcher when I pulled the media table

General Information
--------------------------------------------------------------------------------
Drive type: LDW-451S/851S
Vendor string: LITE-ON
Product string: DVDRW DDW-451S
Firmware revision: G2BD
Firmware timestamp: 2005/01/11 19:52

MediaCodeSpeedEdit V1.0.4.17 is out
I am looking for alpha testers having NEC 3520, 3530, 3540, 6650 drives.

Download Changelog

" - verified support for Liteon LVW-5005 drives DDW-451S G2BD, DDW-813S B208"

Damn that looks good, now I gotta try it


Thanks ala42!!!!

I had to change nothing to support the DDW firmwares, as they are just 451/1633 firmwares.

@ala42

Any news on swapping the write strategies of +R media in the TS-H552U with US06 yet?

I guess you should ask for beta testers in the NEC forum. I don't know how many of them read this one.

ala42, I have tried this question and it seems like what FactFinder said.
I tried three types: no manufacture ID disk, Yuden000 T01, Yuden000 T02.
These three types are all replaced by 16X disk strategy, then DVD identifier
and nero can only give 2.4X speed.

I will if the number of responses stays at zero .

hehe... Ala 42, I'm your man, owning an 3520... but I really want to keep it working not blowing it with wrong firmware. Your last MCSE tool can load the firmware (1uf in this case) but the speed reported are weird.

The released version is compiled without the NEC adaption as you can see from the corrupted media code list and missing firmware id, so do not even think of using it for patching NEC firmware. I got support from Quikee and Liggy so I already know some traps . I will contact you later.

ala42 looks like you're expanding this growing project to the NEC people too, that is very nice indeed. How's your MCSE beta coming along? Hope to see it out soon, if you need an alpha tester just PM me, I know there's a lot of people that would like test your software too .

NEC Support That's excellent news!

But how about NEC3500? I wonder if there's a reason not to include support for this particular drive too? It is a 16x burner after all, is not that old ... and I guess the FW structure is very much the same with the other (slightly) older brothers? ...

The 3500 is not old, but different. The details why I start with the 3520 type firmwares is explained here.

ala42 - I was wondering if doing away with the higher speeds in the media table of the ddw drives would force the ddw to write at the slower speed. They record real time so speed is not a factor. I used tyg02's in the 5005. It would prepare them (I guess it's the equivalent of the lead in) fine, write to them. I was able to watch what was recorded to the ty as long as it stayed in the drive unfinalized . Upon ejecting it and then reinserting it, the ddw had a hard time recognizing the dvd it burnt. Sometimes it would take multiple ejects to recognize it and then sometimes not at all. Funny thing the ddw drive plays all the tyg02's I make in either my 832s or 1633s. I gotta do a test burn to the ty in the ddw and finalize it before I eject it to see what happens. I have not done that yet cause stopped using them in the 5005 after the trouble started.

Or maybe the ddw drive just doesn't like to write to the ty's I dunno.

Edit - we can't pick the burn speed, only the mode 2, 3, 4, 6 hours to a dvd.

Thanks for all your help.

Your 451 type drive burns -R media at a max speed of 4x, so there is not much you can take away. If it can read the disks before ejecting and has problems after, this sounds like a software and not like a recording quality problem.

Ok I was thinking about maybe putting in 2.4 or 2 or 1 x to slow it down....some of the PI/PIF are high. Right now it is burning memeorex 8x -r's with a PRODISC MIC fine. In and out unfinalized and back in record and a out then record until I finalize it with no problems.

Thanks again for the help, we all appreciate it


Edit - changed Ricoh to Prodisc

At the moment I only know that the 8x@16x +R strategy swaps do not work even with the TS-H552B TS02 firmware. Looks like firmware write lock for non 16x +R media.

Thanks for the reply, ala42.

MediaCodeSpeedEdit V1.0.5.0 is out
I am looking for alpha testers having NEC 3530, 6650 drives.

Download Changelog