Pioneer BDR-206DBK locked at 2x speed READ?

[timoteo]

Hi:

 

I just noticed that my second optical drive is locked into reading at 2x speed.  I don't think it was doing this before, it seems to just have started after a session of backups.  

Here is what I have observed:

 

1. Does not matter whether it is a commercial (pressed) disc or a DVD-R.
2. My other drive, a Lite-On iHAS-324-98B, quickly ramps up to at least 4x and within a minute is passing 8-10x on a read of the exact same disc.
3. Write speed is fine ... can run both drives writing at the same time with zero impact on performance.
4. Firmware is 1.56.  A strange (but not unheard of) firmware for these drives.  Most are 1.05 -> 1.06, but my drive will not update to 1.06.  There is a 9.56 which is supposed to be for 1.56 firmware drives, but I am awaiting confirmation from Pioneer.  I am doubting it is a firmware issue, since it seemed to not have this issue until very recently.
5. I just did a Verify on a disc I burned and read back at a max of 8.2x during the verify read with the Pioneer drive.  
6. Finally, I was running ImgBurn 2.5.6, but have upgraded to 2.5.7, however that did not help.

I've included the debug log in hopes maybe you can see something that would indicate why this is occurring.  Thanks for any and all help.

 

Best,

Tim

ImgBurn - debug mode 2x Pioneer BDR.log

[timoteo]

Ok, I just noticed that the reported "supported read speed" is 2x for a few particular discs, which happen to be DVD-R media.  I thought maybe that was it, but then tried a pressed disc and the same result came up.  I then tried another DVD-R disc and it came up as 12x read capable.

 

Forgive this noob question, but ... is it possible certain DVD media only allows a low read-back speed in certain drives?   Again, these same discs have higher read speeds in my other drive, so it can't just be the media alone.

[LIGHTNING UK!]

Read and Verify are the same thing really. One just writes out what it reads to a file on the hdd.

 

So if Verify is fine, Read should be too - assuming it's not a hdd issue.

 

Debug mode doesn't really help with speed issues. The program always works as quickly as the rest of the system will let it. It's the drive that controls the speed.