Personally i don't think its a good idea to allow strat changes for RW media for that very reason.

Yikes....I guess deep down I knew that but I was so anxious to start writing at 8X I pushed it out of my mind
I guess now I'll have to wait for a firmware update before I can test out the ones I've already tried.

Thanks for the feedback!

-Greg

i notice the liteon firmware media code editor allows you to exchange media code and also their burn speed... how come this one is grayed out and all you could do is swap media code? a limitation on programming part?

On old Liteon 811 firmwares you could simply change the speedid byte from 4x to 8x and 8x burning worked. The 8x strategies were already implemented in the firmware, but they were disabled. Later Liteon model and also NEC, LG and Benq firmwares do not have faster strategies waiting to be enabled by a simple one bit patch, so you have to swap the strategy to achieve higher burning speeds.
MCSE allows to disable burning speeds on Benq and LG firmwares, because there is an easy way to do so. With NEC firmwares this is a bit complicated. A minor problem in locating the speed table could mess up alot, so this feature is not available for safety reasons.

Hi ala42,

thanks for your excellent work. I am using the latest version of MediaCodeSpeedEdit for the rpc1 firmware 2.f9 for my NEC 2510.

There is the following problem: In MediaCodeSpeedEdit, there is no Ritek G05 media code found - only Ritek G01 - G04. But NECDump also displays Ritek G05 strategy, so it must be there.

Is it possible that the media table is not complete?

Thanks for your help.

Correct, the table scanner stops too early and misses major parts of the table. I will release the fixed version when I am home.

MediaCodeSpeedEdit V1.0.6.6 is out.
Download Changelog

Hi Ala! Thanks for the update. Now the media table is displayed completely. But there is another problem. When I replace the writing strategy of Ritek G05 media with another strat (for example G02), I can only select 4x burning speed (no other writing speed is available). But I need to burn @ 2x since my drive is connected to a Celeron 400 notebook. Do you know how to solve this?

Strange. I have checked that the patch does what it should do. Post the DVDIdentifier output of your RITEKG05 media, including the Write Descriptor list, of the original and patched firmware.

Hi! Here is the information for the patched firmware. I replaced the G05 strategy with G02 strategy. According to MediaCodeSpeedEdit, 2x should be the only writing speed, but only 4x can be selected in Nero:


** INFO : Drive = _NEC DVD_RW ND-2510A [FW 2.F9]
** INFO : Write Capabilities = DVD+R DVD+R-DL DVD+RW
** INFO : Write Capabilities = DVD-R DVD-RW
** INFO : Disc = [DVD-R:RITEKG05]
** INFO : Reference Speed : 1x DVD = 1385 kBps
** INFO : An Writeable Disc Is Recommended For Accurate Results
** INFO : Write Speeds (Supported By This Drive On This Disc) Listed Below

** INFO : GET PERFORMANCE Write Speed Descriptor(s)
Descriptor #1 = 5408 kBps ( 4.00x) - [CLV/Non-Pure CAV]

** INFO : MODE SENSE Write Speed Descriptor(s) [Legacy Command]
** WARNING : MODE SENSE Is Obsolete And Not Always Properly Supported
Descriptor #1 = 5645 kBps ( 4.00x) - [CLV/Non-Pure CAV]
Descriptor #2 = 4234 kBps ( 3.06x) - [CLV/Non-Pure CAV]
Descriptor #3 = 3528 kBps ( 2.55x) - [CLV/Non-Pure CAV]
Descriptor #4 = 2822 kBps ( 2.00x) - [CLV/Non-Pure CAV]
Descriptor #5 = 1411 kBps ( 1.00x) - [CLV/Non-Pure CAV]
Descriptor #6 = 706 kBps ( 0.51x) - [CLV/Non-Pure CAV]

Here is the information with the original firmware:


** INFO : Drive = _NEC DVD_RW ND-2510A [FW 2.F9]
** INFO : Write Capabilities = DVD+R DVD+R-DL DVD+RW
** INFO : Write Capabilities = DVD-R DVD-RW
** INFO : Disc = [DVD-R:RITEKG05]
** INFO : Reference Speed : 1x DVD = 1385 kBps
** INFO : An Writeable Disc Is Recommended For Accurate Results
** INFO : Write Speeds (Supported By This Drive On This Disc) Listed Below

** INFO : GET PERFORMANCE Write Speed Descriptor(s)
Descriptor #1 = 10816 kBps ( 7.81x) - [CLV/Non-Pure CAV]
Descriptor #2 = 8112 kBps ( 6.00x) - [CLV/Non-Pure CAV]
Descriptor #3 = 5408 kBps ( 4.00x) - [CLV/Non-Pure CAV]
Descriptor #4 = 2704 kBps ( 2.00x) - [CLV/Non-Pure CAV]

** INFO : MODE SENSE Write Speed Descriptor(s) [Legacy Command]
** WARNING : MODE SENSE Is Obsolete And Not Always Properly Supported
Descriptor #1 = 5645 kBps ( 4.00x) - [CLV/Non-Pure CAV]
Descriptor #2 = 4234 kBps ( 3.06x) - [CLV/Non-Pure CAV]
Descriptor #3 = 3528 kBps ( 2.55x) - [CLV/Non-Pure CAV]
Descriptor #4 = 2822 kBps ( 2.00x) - [CLV/Non-Pure CAV]
Descriptor #5 = 1411 kBps ( 1.00x) - [CLV/Non-Pure CAV]
Descriptor #6 = 706 kBps ( 0.51x) - [CLV/Non-Pure CAV]

I can definitely say that "MediaCodeSpeedEdit" when being embadded with Liggy/Dee_2TG ( on NEC3500) has no any effect as far as increasing the ripping speed concern and absolutely does not increase the ripping speed over LD_2TG of NEC3500. but the same tools (MCSE) increase ripping speed on BenQ 1640 by %30 to %40. May be ala42 has some answer.

It has the same effect as using the FAST firmware instead of the ORIG firmware.

Here are the NEC related changes of MediaCodeSpeedEdit V1.0.6.7:
Download Changelog

Also many thanks to you ala42

The increase speed patch is of any use?
The 4550 is already riplock free

Good question. The VIDEO_TS string is still in the firmware, but I do not know if removing it makes any change.

thank`s --->>ALA42<<--- for support NEC 4550
great work

I am looking for testers with NEC 3530 or 3550 drives.

Send me a free 3550 and I will be glad to test it.

Pay Ala42 a good salary for his hard work and he'll be glad to release MCSE for you with some sort of warranty that your 3550 drive won't suffer from the operation.

Maybe anyone is willing to downgrade his 4550 drive

Is that an actual request, or in reference to the rip speed thing? I just obtained a 4550 (Mad Dog MegaStor Triple Format MD-16X3DVD9-8X) and flashed it to your 1.X3 firmware. If you need a guinea pig, give me a PM or reply (now or any time in the future). I had to replace my NEC 3500, so I can no longer be of service to you for that particular model.

It was just meant as a reply to people who were asking for a free 3550 drive in order to be able to test MCSE's 3550 support

Which was my apparently unsuccessful attempt to interject a little levity into this otherwise overly serious subforum.