dbminter

Good to have both on hand. That way, when you get one, you can test it and if it doesn't work, send it back. Then, you'll have the other on hand, too, to try next. That model of Pioneer is the one I have always used. In fact, I have 2 of them. The 2nd one I got I still use and the first one I got still works. Just sitting around to swap in. Pioneer's have a few flaws of their own. After a few months, the eject button doesn't always work the first time it's pressed. Pressing it again works. Issuing an Eject command in ImgBurn does the same thing. However, all eject commands issued after a write if directed by ImgBurn seem to work. The current firmware is borked for Ritek 8x DVD+RW media. However, it's a moot point as you can't find 8x DVD+RW new anymore. The quality of that drive may have declined if my experience is any indication. I don't know yet. Can only relate my story. As I said, my first 2 drives have performed well. My first is almost 3 years old and still works. My current one is almost 2 years old and still works. The 3rd one I had, though, I had to replace after 7 months. The 4th one I got I had to send back to Amazon.com because it was borked for writing Verbatim BD-R out of the box. However, with all that said, I'd still recommend trying a Pioneer first for a BD burner.

Discovered another LG/Verbatim incompatibility after testing more 1.03 media burns. The LG's never liked writing to Verbatim 6x DVD-RW media, either. 1.03 does nothing to fix this. They still fail at the, guess where? Verify! My Pioneer writes them fine.

The problem is with LG drives and Verbatim BD DL. I updated the firmware to 1.03, performed another BD-RE DL test. Of course, it STILL failed Verify at the layer break change. I 15:23:00 Operation Started! I 15:23:00 Source File Sectors: 15,957,344 (MODE1/2048) I 15:23:00 Source File Size: 32,680,640,512 bytes I 15:23:00 Source File Volume Set Identifier: 4B8B79FA00F37D0A I 15:23:00 Source File Application Identifier: ImgBurn v2.5.8.0 I 15:23:00 Source File Implementation Identifier: ImgBurn I 15:23:00 Source File File System(s): UDF (2.60) I 15:23:00 Destination Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.03 (S:) (SATA) I 15:23:00 Destination Media Type: BD-RE (Disc ID: VERBAT-IM1-000) I 15:23:00 Destination Media Supported Write Speeds: 2x I 15:23:00 Destination Media Sectors: 24,438,784 I 15:23:01 Write Mode: BD I 15:23:01 Write Type: DAO I 15:23:01 Write Speed: MAX I 15:23:01 Hardware Defect Management Active: No I 15:23:01 BD-RE FastWrite: No I 15:23:01 Link Size: Auto I 15:23:01 Lock Volume: Yes I 15:23:01 Test Mode: No I 15:23:01 OPC: No I 15:23:01 BURN-Proof: Enabled I 15:23:01 Write Speed Successfully Set! - Effective: 8,992 KB/s (2x) I 15:23:02 Filling Buffer... (40 MiB) I 15:23:03 Writing LeadIn... I 15:23:27 Writing Session 1 of 1... (1 Track, LBA: 0 - 15957343) I 15:23:27 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 15957343) I 15:23:27 Writing Layer 0... (LBA: 0 - 12219391) I 16:08:25 Writing Layer 1... (LBA: 12219392 - 15957343) I 16:22:34 Synchronising Cache... I 16:22:58 Exporting Graph Data... I 16:22:58 Export Successfully Completed! I 16:22:58 Operation Successfully Completed! - Duration: 00:59:57 I 16:22:58 Average Write Rate: 9,000 KiB/s (2.1x) - Maximum Write Rate: 9,560 KiB/s (2.2x) I 16:22:58 Cycling Tray before Verify... W 16:23:05 Waiting for device to become ready... I 16:23:20 Device Ready! I 16:23:24 Operation Started! I 16:23:24 Source Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.03 (S:) (SATA) I 16:23:24 Source Media Type: BD-RE (Disc ID: VERBAT-IM1-000) I 16:23:24 Source Media Supported Read Speeds: 2x, 4x, 6x I 16:23:24 Source Media Supported Write Speeds: 2x I 16:23:24 Source Media Sectors: 24,438,784 I 16:23:24 Source Media Size: 50,050,629,632 bytes I 16:23:24 Image File Sectors: 15,957,344 (MODE1/2048) I 16:23:24 Image File Size: 32,680,640,512 bytes I 16:23:24 Image File Volume Identifier: 12 - December I 16:23:24 Image File Volume Set Identifier: 4B8B79FA00F37D0A I 16:23:24 Image File Application Identifier: ImgBurn v2.5.8.0 I 16:23:24 Image File Implementation Identifier: ImgBurn I 16:23:24 Image File File System(s): UDF (2.60) I 16:23:24 Read Speed (Data/Audio): MAX / MAX I 16:23:25 Read Speed - Effective: 2x - 6x, 6x - 2x I 16:23:25 Verifying Session 1 of 1... (1 Track, LBA: 0 - 15957343) I 16:23:25 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 15957343) I 16:23:25 Verifying Layer 0... (LBA: 0 - 12219391) I 16:59:06 Verifying Layer 1... (LBA: 12219392 - 15957343) W 16:59:10 Failed to Read Sectors 12219616 - 12219647 - Reason: L-EC Uncorrectable Error W 16:59:16 Failed to Read Sector 12219616 - Reason: L-EC Uncorrectable Error W 16:59:16 Sector 12219616 maps to File: \12 - December\12 - December-00-03.mrimg E 17:31:27 Failed to Read Sector 12219616 - Reason: L-EC Uncorrectable Error E 17:31:27 Sector 12219616 maps to File: \12 - December\12 - December-00-03.mrimg E 17:31:27 Failed to Verify Sectors! I 17:31:33 Exporting Graph Data... I 17:31:33 Export Successfully Completed! E 17:31:33 Operation Failed! - Duration: 01:08:03 I 17:31:33 Average Verify Rate: 5,987 KiB/s (1.4x) - Maximum Verify Rate: 32,591 KiB/s (7.4x) Notice how it failed Verify with less than 300 sectors into the 2nd layer? The issue is an inherent problem with LG drives and (at least) Verbatim BD-RE DL. Since it happens on your drive, too, it happens on all Verbatim BD-R DL and BD-RE DL. And it may even happen on ALL manufacturers of BD DL media. Nothing had ever been written to this Verbatim BD-RE DL before. It had only been "written once" when it was formatted in a Pioneer drive. So, it's highly unlikely the disc is bad. And it's highly unlikely that the Pioneer formatted it wrong because the Pioneer and my USB ASUS write to these kinds of discs fine. Only the 5 LG's I've tested do this. They all fail Verify except for one Verify, and the contents were NOT written correctly to the disc when I compared the written contents with the source. Ergo, the problem is with all LG drives. QED.

Wait, there's a 1.03 firmware update to that drive? I have that LG drive because it writes properly to all other media except for BD-RE DL and firmwarehq only lists 1.02, my firmware. Found the firmware on LG's site for the drive. It appears it was just released 3 days ago. After over 3 years of no new firmware updates, it seems LG finally updated this drive. Seems it didn't fix the BD-RE DL issue, but I'll test it out, anyway. If it makes you feel any better, I, at least, found some useful information from this post. Thanks!

I still will fall back on it's the fault of the LG drive. See this thread for a similar issue that was "resolved." http://forum.imgburn.com/index.php?/topic/24807-errors-when-verifying/

Unfortunately, the bottom line is LG is a corporation, and all they care about is money. The profit margins are drastically shrinking on optical products, so manufacturers just don't care anymore. Not that they ever cared before. I told Pioneer about their latest firmware borking 8x DVD+RW Ritek media. Do you think they fixed it? No, because they don't care. You can try swapping LG's all you like. I still say you'll find the same result. ASUS did the same thing. The USB ASUS I have worked on all media tests I threw at it. So, I had high hopes for their internal burner. But, it's borked! Destroys rewritable media! Did this on 2 copies of the same drive. So, which is more likely? That I just happened to get 2 bad drives in a row from different batches or that the drive itself doesn't work right out of the gate?

Could be the LG burner you're using. I've tried 5 different LG BD burners for burning Verbatim good quality BD-RE DL and only 1 didn't fail Verify. So, I've come to the conclusion that LG drives are not good at writing BD DL media. Now, I've never burned a BD-R DL before, but I would think if all the LG's I've ever tested BD-RE DL failed more times than succeeded, I would say it's the fault of LG burners. I only use my Pioneer BD burner for writing BD-RE DL, which writes to them perfectly. So, you may want to try a Pioneer BD drive if you can't get this issue resolved on your LG.

Yes, if you get the same results with another LG drive of the same model, you will know it's the drive. My conclusion is based on 5 LG's I've had, 3 of the latest model, and 2 others, and those 3 of the latest don't burn BD-RE DL right at all. Out of 5 burns, only 1 completed write and verify. Your discs shouldn't be the problem. The DID indicates they're the good kind of Verbatim BD media. However, you could always have a bad batch of discs, but I doubt it. No, I don't find it strange at all that all LG drives may be bad at writing BD DL media. If they don't do it right out of the research and development facility, then, they all will not do it right out of the factory. Take ASUS's latest BD burner. It's bad out of the factory, too. Destroys 8x DVD+RW and Verbatm BD-RE and BD-RE DL when it writes to them. It did this on 2 copies of the same drive I tried out, so it's a manufacturing defect. I don't think it's bad batch of drives since I had 3 of the LG's over the course of 3 years that all did the same. LG's are also terrible writers at writing BD-RE SL as giant floppies. They write at half the speed as the Pioneer does. Even writing BD-RE DL as giant floppies are no go on LG drives. They will write the files, but the files will be utterly useless on the disc. All will have had write errors and their contents will be corrupted. LG's are also terrible readers. Yet, oddly enough, I had a disc that my Pioneer wouldn't read but my LG would. Go figure. The only reason I still have an LG is because Pioneer borked the firmware for writing Ritek 8x DVD+RW discs. They will always fail verify and all drives writing afterwards will always fail verify until fully formatted in another drive. My LG is perfectly fine for writing all other kinds of media that I tested it with, Even BD-R SL and BD-RE SL. However, I absolutely always avoid BD-RE DL in it. It's not a reliable drive for writing BD-RE DL, so I can't see it writing BD-R DL well either.

Probably the fault of the LG drive. I've had about 5 models of different kinds of LG BD burners and they all failed to burn properly to Verbatim BD-RE DL. Constant errors on Verifying the second layer. So, while I've never used BD-R DL to burn in an LG drive, I've come to the conclusion that LG's are terrible writers when it comes to burning BD DL media. And while I've never burned a BD-R DL in my Pioneer drive, I would recommend trying a Pioneer drive for burning BD-R DL. They burn my Verbatim BD-RE DL fine, so I can't see why they wouldn't work fine on Verbatim BD-R DL. Also, have you burned any BD-R DL without playback problems before? Or are all your BD-R DL's burnt doing these playback problems? And notice how your Verify errors occur right at the exact start of the 2nd layer?

I can't either. It'll happen, though, unfortunately. I guess I'll have to switch to flash drives and USB HDD's for external storage when that time comes. I bought the last 3 cake stacks of 8x DVD+RW available on the Internet. So, I've got some to last for as long as they'll last.

You're right. I didn't take into account multiple layer discs. I was thinking entirely of CD-R/W, DVD-+R/W, and BD-R/E SL.

I have a question about how ImgBurn, or I guess reading in general, is done with recordable discs that have images written to them. Hypothetical: say you have a recordable disc, CD, DVD, BD, I don't think it matters. And you've written an image that takes up half of the available space on the media. The other remaining half is unburned dye/media. Let's say a deep scratch occurs in the unburned area that does not go into the recorded area. When ImgBurn/anything goes to read the disc to an image file, would this scratch prevent ImgBurn from reading the disc? Does ImgBurn only "scan" the burned area to determine what is burned on the disc and thus what to read? Thanks!

What does the 2048 number next to Mode 1 mean in the settings? It's a multiple of 1024, so it's a binary value, that much I know.

Yeah. I was wondering what was the point.

Got my wires crossed with that other thread where the poster had problems with BD-R DL media not playing on his player. I had forgotten he had resolved that by coming to the conclusion that his player was the problem. Anyway, SOME of what I said still applies. The next step is getting the player to recognize a DVD+R DL had been inserted. Then, testing it by playing to see if there any playback problems like skips, pauses, hisses, or pops.

Now might come another problem. The verification problem has been resolved by the higher quality Verbatim media, but your player may not particularly like DL BD media, regardless of the manufacturer. Or it may just be picky on Verbatims. It really is a sort of crap shoot of trial and error. For instance, I know my Playstation 3 will play BD movies written to Verbatim BD-RE DL, but I've never written a single BD-R DL before. And I know that the PS3 is picky about BD media. It will play Verbatim BD-R fine but will not properly play Memorex BD-R made by Ritek. Verbatim BD-RE, back when they made them and not CMC, also play fine in the PS3. What you'll want to look for first is that your Blu-Ray player even recognizes that you inserted a BD-R DL to play. If it finds it, that's the first hurdle overcome. Then, what you'll want to look for is playback of the BD-R DL. You'll want to look for skips, hisses, pauses, and pops in the audio/video. Especially if it stops playing and then "skips" ahead.

I've never owned an Xbox, so I couldn't say anything about it. Sorry.

My parents never had an 8-track player, so I never had a cassette. But, where my mother worked up until about 1985, the owner of the place played 8-track tapes over a speaker system in the store. So, I have seen the players and held some tapes. I had a PC where you stored programs I wrote in BASIC on audio cassettes. Back when programs consisted of the fabulous 10 PRINT "HELLO WORLD!" or the infamous 10 GOTO 20 20 GOTO 10 My first x86 PC was a 286 I got for high school work in 1992. It had a whopping 40 MB hard drive. 2600 baud modem. 5.25 and 3.5 inch floppy drives. Had one of the infamous Turbo buttons I snapped off putting the case back together after swapping in a 14.4 k modem. Luckily, the button was in the on Turbo position at the time. I think it ran MS DOS 4.x and Window 2.x. Did you know that even in today's modern PC BIOS, there is the basic interface for hooking up a cassette recorder for audio tape saved programs? For backwards compatibility. In case anyone ever would need to do something so archaic. Just like when you type. When you type on a PC keyboard, the BIOS converts your typing into punches for the system to read. Yes, just like on those old punch cards.

Ancient? I can still remember rethreading video tapes that have snapped. I'm also not too young to remember 8-track tapes.

There's no image. The link just opens the main imageshack page. Post the log. That's what we need. Under Help, choose ImgBurn Logs, open the log, find where there error is, and post the entire log of that burn that failed.

Hm, interesting. You'd think Mode 1 would have been only for CD's since CD's came first. Therefore, you'd think the first mode would be for CD's and thus Mode 1. Ya loin sumtin new every day.

Found this: http://www.cdrlabs.com/forums/mode-versus-mode-discs-t8075.html Seems the difference between the 2 modes is Mode1 has more error correction built in. It devotes more available disc space to error correction than Mode2. Mode2 will let you store more data on a disc than Mode1, but you sacrifice the extended error correction in Mode1. So, you probably do want Mode1 versus Mode2.

I use Mode1, UDF 2.60 for all of my data archives to Blu-Ray media formats. However, I don't know anything about Linux, so I don't know if UDF 2.60 is supported on it. I would think these options should make a disc readable on Windows 7. I've used these options for Windows 8.1 Update 1 and all flavors of Windows 10 that have been released without problems accessing the data on the discs later. I know this is forwards compatible with Windows 8.1 Update 1 and all versions of Windows as discs I've created on Windows 8 were readable on Windows 10. Your instance, though, is backwards compatibility, so I'm not certain on that. I don't know the difference between Mode1 and Mode2. If a file name is too long, ImgBurn should notify you before it starts creating the image after you press the "burn" button that it's too long. It will tell you the file name/folder structure and ask you if you want to continue.

Tools --> Settings --> General --> Page 1 --> Options --> Check the box next to Don't Show Status Bar Messages (*) Now, disabling the status bar messages might prevent some troubleshooting messages from appearing, right? Sometimes, like when ImgBurn just locks up, that the only "error" you'll get will be from the status bar messages.

Not all Verbatim are created equal. Verbatim Life series you find in brick and mortar stores and online will be CMC Magnetics. CMC is the bottom of the barrel optical disc manufacturer. Verbatim DataLifePlus MKM is the only really consistent quality DVD DL blank. (Although I've had good results with TDK's.) You can probably only find Verbatim DataLifePlus MKM media online. Like I can only get mine from Amazon.com. Most people using CMC DL media who switch to the quality Verbatim discs generally find their problems go away. It's not a be all, cure all, but it generally fixes the problem. And if this started all of a sudden out the clear blue when you had gotten good results on CMC before, that could just be the nature of the beast. You got lucky before.