BlizzardUK Posted July 25, 2023 Posted July 25, 2023 (this post is regarding 2 different but similar issues) I tick verify so after I have burnt a blu-ray disc it will verify it, but it sticks during verification, for instance it might get to 7% or 16% (last 2 examples) verified and then stay there for 30+ minutes until I give up with it. Then when I try and cancel it won't, it stays on "Waiting for Read Thread (Device)". My drive is a Pioneer BDR-206D and it is inside a Primera Bravo SE and has a SATA to IDE convertor, not sure if that makes any difference. Imgburn will burn the BD-Rs fine it just won't verify discs either via immediate verification of disc post burn or a compare verification against a disc image. It's driving me a bit nuts as I have to use a different drive for verifications. On the below log when I came in at 32 minutes it was just stuck at 7%. No error, just 0x speed and nothing happening. When I clicked cancel it then said "Waiting for Read Thread (Device)" and wouldn't cancel until I used task manager to close it as no amount of clicking cancel did anything. Unfortunately I can't show logo info or a graph as shutting down via task manager means it doesn't write one. But it does seem this only happens on the BDR-206D and not my other Pioneer that isn't in the SE. Why would the BDR-206D not be able to verify BD-Rs ? I managed to copy and paste the below info from the log that appears under the software. Why would a drive be able to burn but not verify ??? I 23:53:56 Cycling Tray before Verify... I 23:54:19 Device Ready! I 23:54:20 Operation Started! I 23:54:20 Source Device: [0:0:0] PIONEER BD-RW BDR-206D 9.56 (T:) (USB) I 23:54:20 Source Media Type: BD-R (Disc ID: RITEK-BR3-000) I 23:54:20 Source Media Supported Write Speeds: 2x, 4x, 6x, 8x, 10x I 23:54:20 Source Media Sectors: 11,890,848 I 23:54:20 Source Media Size: 24,352,456,704 bytes I 23:54:20 Image File: G:\myBDR.iso I 23:54:20 Image File Sectors: 11,890,848 (MODE1/2048) I 23:54:20 Image File Size: 24,352,456,704 bytes I 23:54:20 Image File Volume Identifier: mybdr I 23:54:20 Image File Volume Set Identifier: 563E39A900B57011 I 23:54:20 Image File Application Identifier: ImgBurn v2.5.8.0 I 23:54:20 Image File Implementation Identifier: ImgBurn I 23:54:20 Image File File System(s): UDF (2.50) I 23:54:20 Read Speed (Data/Audio): MAX / MAX I 23:54:21 Read Speed - Effective: 0x I 23:54:21 Verifying Session 1 of 1... (1 Track, LBA: 0 - 11890847) I 23:54:21 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 11890847) I 00:26:12 Abort Request Acknowledged --------------------------------------------------------- One other small issue, when I compare discs to an ISO (on my other drive) it often sets the read speed to 2x when the drive I am using to compare/verify is a Pioneer BDR-X12 which is quite new (I have 2 different BD-Rs, the one in the SE and this as an external drive). I have to use this drive to verify due to the above SE one not being able to. It will compare some at 12x but just wondered why some (same media brand) stay at 2x ? I would say it is 50/50 whether it will compare a blu-ray disc at 2x or the full 12x. Below is info I got from the log when it verified at 2x. I 22:51:06 Operation Started! I 22:51:06 Source Device: [0:0:0] PIONEER BD-RW BDR-X12 1.03 (K:) (USB) I 22:51:06 Source Media Type: BD-R (Disc ID: RITEK-BR3-000) I 22:51:06 Source Media Supported Read Speeds: 12x I 22:51:06 Source Media Supported Write Speeds: 2x, 4x, 6x, 8x, 10x, 12x I 22:51:06 Source Media Sectors: 11,703,904 I 22:51:06 Source Media Size: 23,969,595,392 bytes I 22:51:06 Image File: G:\anotherISO.iso I 22:51:06 Image File Sectors: 11,703,904 (MODE1/2048) I 22:51:06 Image File Size: 23,969,595,392 bytes I 22:51:06 Image File Volume Identifier: anotheriso I 22:51:06 Image File Volume Set Identifier: 56462A0200B295FA I 22:51:06 Image File Application Identifier: ImgBurn v2.5.8.0 I 22:51:06 Image File Implementation Identifier: ImgBurn I 22:51:06 Image File File System(s): UDF (2.50) I 22:51:06 Read Speed (Data/Audio): MAX / MAX I 22:51:07 Read Speed - Effective: 5x - 12x I 22:51:08 Verifying Session 1 of 1... (1 Track, LBA: 0 - 11703903) I 22:51:08 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 11703903) I 23:35:35 Exporting Graph Data... I 23:35:35 Graph Data File: C:\Users\name\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-X12_1.03_24-JULY-2023_22-51_RITEK-BR3-000.ibg I 23:35:35 Export Successfully Completed! I 23:35:35 Operation Successfully Completed! - Duration: 00:44:27 I 23:35:35 Average Verify Rate: 8,780 KiB/s (2.0x) - Maximum Verify Rate: 8,842 KiB/s (2.0x) Thanks for any advice.
dbminter Posted July 25, 2023 Posted July 25, 2023 Unfortunately in your case, it's probably hard to say much of anything. This rig you've made is some kind of Frankenstein type affair, if memory serves me correctly. Parts from different manufacturers and a specialized firmware. In that kind of scenario, it's hard to say what might cause an issue. One thing that might cause a problem is the RITEK media. I've never used anything other than VERBAT-IM BD-R SL so I can't say what quality the RITEK media would be. As for the read speed, unfortunately, it really is down to the drive itself as to what it will or won't do. It may say I'll read at X max speed but not get nowhere near that.
dbminter Posted July 25, 2023 Posted July 25, 2023 Oh, forgot something. Operations that suddenly drop to 0x, don't do anything, and the software can't recover, e.g. waiting for read threads, are common with external drives that fail an operation. In this case, a read operation for Verify. Reads that behave this way are generally the result of failed Verifies, being unable to read the burned data back from the disc. However, in this case, manual Verify seems to work on another drive, so the problem is somewhere in that particular hardware regarding reads.
BlizzardUK Posted July 25, 2023 Author Posted July 25, 2023 (edited) Yeah, it is a Frankenstein machine, haha. The SE came with a DVD drive in it, so I replaced it with a BD-R drive, but it could only be a specific drive as it uses its own firmware. I had to use a SATA to IDE adapter as the machine was made in 2007 and only had IDE. Recording in ImgBurn works fine, just verifying is an issue. I do have Verbatim BD-Rs too, will have to give those a go too, they were going to be used when my Acu-Disc blu-rays (the Riteks) ran out. Right now I am burning 12 Blu-Rays in ImgBurn using the queue function and it is working great, just won't verify unless I put the discs in my other burner. It is funny but I am obviously so late to the game, as Lightning has old posts on here from 2010 where he changed the drive in his Bravo SE. Edited July 25, 2023 by BlizzardUK
dbminter Posted July 25, 2023 Posted July 25, 2023 Yeah, I think it might be worth trying a Verbatim BD-R and see if you get the same results. If you just burn one, you can tell if you get a complete Verify. If you don't, I would say it's something buried in the hardware changes here. I'd be a bit inclined to blame the SATA to IDE bridge.
BlizzardUK Posted July 25, 2023 Author Posted July 25, 2023 Thanks. I will try tonight. I have found a way to connect directly from the sata drive to the internals of the SE too while still giving the drive power from the internal cable (most converters only had external power cables which wouldn't have been much use), but after testing (at that point I didn't know about verification issues so didn't test that) it oddly seemed to burn smoother with the bridge, less up and down of the buffering hence why I went back to the bridge, which is weird given SATA to USB was a more direct connection than SATA to IDE to USB. But I will try the same device out again tonight. Primera should give me a job as I know the insides of their machines better than them now probably, haha.
BlizzardUK Posted July 26, 2023 Author Posted July 26, 2023 (edited) Your hunch may be correct, I don't want to speak too soon but I just swapped over the SATA to IDE bridge and replaced it with a direct SATA to USB and it has verified the last 2 discs without issue, which never happened before. It wasn't the discs though as it still did it with a Verbatim with the SATA to IDE bridge. The reason though I preferred to use the SATA to IDE bridge was because the buffer stayed more consistent on burns, the buffer wouldn't fluctuate much like it does with with the direct to USB connection. Does the buffer going up and down occasionally matter much ? Below is a graph from the SATA to USB burn, does it look okay ? This was using a ACU-DISC which uses the Ritek Media ID. Thanks. Oh and if interested the inside of the SE machine has a USB port, so for instance with SATA TO IDE it literally just connects as normal but with the bridge attached, the normal USB socket stays plugged in. When I use SATA to USB I bypass the IDE board completely and connect the USB cable to the internal USB socket, I just unplug the the one. Took me a long time to find a SATA to USB adapter that didn't work via external power, I can use the molar cable. Edited July 26, 2023 by BlizzardUK
dbminter Posted July 26, 2023 Posted July 26, 2023 I generally don't take buffer fluctuations into account. My LG drive buffers up and down and I've not had an issue with it in like 10 years. I really don't know how to read the graphs. I never pay attention to those.
BlizzardUK Posted July 26, 2023 Author Posted July 26, 2023 I just saw this thread where Lightning says the bottom graph of the 3 is a good burn, mine seems to compare a bit to that....
Recommended Posts