dbminter

In your case, probably the only good test is to get some Verbatim DataLifePlus MKM DVD+R DL's and try those. You can only find them online. The Verbatims you get in brick and mortar stores will usually be CMC or some other bottom of the barrel manufacturer. My experience has been when a drive fails, it generally fails on burning DVD+R DL's first. Sometimes only on those. For whatever reason. Probably the layer break change. I've only ever had 1 drive fail on me that failed for something else. It stopped burning BD-RE.

If it's a DVD Video disc, you could try using DVD Shrink to the contents by a few percentage points and see if that new shrunk VIDEO_TS offers a layer break. You may need to do more than 1 shrink to find the size that is acceptable. Rarely, but a few times, I've had to shrink the VIDEO_TS contents to get a layer break that was accepted.

A problem like this coming up out of the clear blue sounds to me indicative of a failing drive. It works one day and doesn't the next I would generally pin on needing to replace the drive. The other option I'd look into is if the same manufacturer made the discs that worked before and didn't now. You'd need to check to see if the Disc ID listed in the log is still the same. If it is, then there could be a change in the manufacturing process by Ritek. Highly unlikely, but it could be the case.

Found an old graphics image file from like 10 years ago. It was a banner that said "Friends don't let friends burn CMC-Mags!" How true!

Ah, now it makes sense. It seems that Imation is a Memorex company or vice versa. And since both companies produce generally lower quality, cheaper junk media, it all starts to connect. Memorex used to make a quality product back when I used their CD-RW in the early 2000's. And their 24x CD-RW's were farmed out to Mitsubishi, a quality maker. And Memorex now uses Ritek for their BD media. However, that cannot undo years and millions of product of CMC Magnetics trash. And Imation always released junk product. Their floppy disks were unreadable in a year. And they farmed out to CMC for their rewritable DVD discs.

Appears my worries were apparently misguided. It seems that you can still buy them directly from Verbatim's online store. For now, anyway. So, maybe they aren't being phased out just yet.

Tried to order some Verbatim DataLife Plus BD-R from Amazon.com today only to discover that only resellers are offering them. So, I checked online and none of the major retailers have them, either! So, does this mean Verbatim is phasing out DataLife Plus BD-R? Their regular branded BD-R has the same MID/DID as the DataLife Plus, so maybe they're consolidating the line into just those. But, they'll probably just switch over the regular branded HTL BD-R to CMC! Or only offer the inferior LTH ones.

I was creating a double layer DVD image and noticed in the Log there are entries for Single Layer Profile and Double Layer Profile. Why is there an entry for Single Layer Profile when the contents won't fit on a single layer DVD?

Looks like I had a fluke BD-R. I burned again to a 2nd BD-R and it Verified fine. I was only worried because I'd never encountered a Miscompare before and I had some weird behavior with this drive. I burned some Macrium Reflect images that were split across multiple DVD's to a single BD-R. When I went to manually verify the contents in Reflect, it failed to recognize that the 2nd file was on the disc. Then I had weird behavior in the same drive when copying files from discs to the HDD. It would copy the contents but sometimes only by copying the contents into a folder named with the Label of the DVD. Windows did this on its own. Then I had the Miscompare on a BD-R in the same drive. With all this occurring over the last 2 or 3 days, I was wondering. I only installed this Pioneer BD burner a month or 2 ago, but that's no reason why it couldn't have gone bad.

Burned the image to a BD-RE. Verified fine. Maybe it was just the BD-R I used. I'll try burning another BD-R.

I mounted the image ImgBurn created and performed a manual Verify of the image contents against the mounted image. The contents verified okay, so the problem is with the burn to the disc.

Got my very first file Miscompare on Verify in my entire history of using ImgBurn. It occurs on one large file. I 16:21:49 Operation Started! I 16:21:49 Source File Sectors: 12,040,256 (MODE1/2048) I 16:21:49 Source File Size: 24,658,444,288 bytes I 16:21:49 Source File Volume Set Identifier: 4889818C00B7B7A6 I 16:21:49 Source File Application Identifier: ImgBurn v2.5.8.0 I 16:21:49 Source File Implementation Identifier: ImgBurn I 16:21:49 Source File File System(s): UDF (2.60) I 16:21:49 Destination Device: [0:0:0] PIONEER BD-RW BDR-209M 1.33 (S:) (SATA) I 16:21:49 Destination Media Type: BD-R (Disc ID: VERBAT-IMe-000) I 16:21:49 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x, 10x, 12x, 16x I 16:21:49 Destination Media Sectors: 12,219,392 I 16:21:49 Write Mode: BD I 16:21:49 Write Type: DAO I 16:21:49 Write Speed: MAX I 16:21:49 Hardware Defect Management Active: No I 16:21:49 BD-R Verify Not Required: Yes I 16:21:49 Link Size: Auto I 16:21:49 Lock Volume: Yes I 16:21:49 Test Mode: No I 16:21:49 OPC: No I 16:21:49 BURN-Proof: Enabled I 16:21:49 Write Speed Successfully Set! - Effective: 71,920 KB/s (16x) I 16:21:49 Advanced Settings - Optimal Writing Speed: No I 16:21:49 Filling Buffer... (40 MiB) I 16:21:50 Writing LeadIn... I 16:22:01 Writing Session 1 of 1... (1 Track, LBA: 0 - 12040255) I 16:22:01 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12040255) I 16:30:27 Synchronising Cache... I 16:30:28 Closing Track... I 16:30:29 Finalising Disc... I 16:30:39 Exporting Graph Data... I 16:30:39 Export Successfully Completed! I 16:30:39 Operation Successfully Completed! - Duration: 00:08:50 I 16:30:39 Average Write Rate: 47,684 KiB/s (10.9x) - Maximum Write Rate: 69,769 KiB/s (15.9x) I 16:30:39 Cycling Tray before Verify... I 16:30:54 Device Ready! I 16:30:55 Operation Started! I 16:30:55 Source Device: [0:0:0] PIONEER BD-RW BDR-209M 1.33 (S:) (SATA) I 16:30:55 Source Media Type: BD-R (Disc ID: VERBAT-IMe-000) I 16:30:55 Source Media Supported Read Speeds: 12x I 16:30:55 Source Media Supported Write Speeds: 2x, 4x, 6x, 8x, 10x, 12x I 16:30:55 Source Media Sectors: 12,040,256 I 16:30:55 Source Media Size: 24,658,444,288 bytes I 16:30:55 Image File Sectors: 12,040,256 (MODE1/2048) I 16:30:55 Image File Size: 24,658,444,288 bytes I 16:30:55 Image File Volume Set Identifier: 4889818C00B7B7A6 I 16:30:55 Image File Application Identifier: ImgBurn v2.5.8.0 I 16:30:55 Image File Implementation Identifier: ImgBurn I 16:30:55 Image File File System(s): UDF (2.60) I 16:30:55 Read Speed (Data/Audio): MAX / MAX I 16:30:56 Read Speed - Effective: 5x - 12x I 16:30:56 Verifying Session 1 of 1... (1 Track, LBA: 0 - 12040255) I 16:30:56 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 12040255) W 16:40:15 Miscompare at LBA: 8850880, Offset: 0 W 16:40:15 Device: 0x00 (Empty Sector!) W 16:40:15 Image File: 0x46 W 16:40:15 Total Errors in Sector: 2,040 I 16:40:15 Verifying Sectors... W 16:40:17 Miscompare at LBA: 8850881, Offset: 0 W 16:40:17 Device: 0x00 (Empty Sector!) W 16:40:17 Image File: 0xB6 W 16:40:17 Total Errors in Sector: 2,041 I 16:40:17 Verifying Sectors... W 16:40:34 Miscompare at LBA: 8850882, Offset: 0 W 16:40:34 Device: 0x00 (Empty Sector!) W 16:40:34 Image File: 0x2C W 16:40:34 Total Errors in Sector: 2,036 I 16:40:34 Verifying Sectors... W 16:40:35 Miscompare at LBA: 8850883, Offset: 0 W 16:40:35 Device: 0x00 (Empty Sector!) W 16:40:35 Image File: 0x1B W 16:40:35 Total Errors in Sector: 2,033 I 16:40:35 Verifying Sectors... W 16:40:36 Miscompare at LBA: 8850884, Offset: 0 W 16:40:36 Device: 0x00 (Empty Sector!) W 16:40:36 Image File: 0xAE W 16:40:36 Total Errors in Sector: 2,042 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850885, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x92 W 16:40:38 Total Errors in Sector: 2,034 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850886, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0xA9 W 16:40:38 Total Errors in Sector: 2,037 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850887, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x81 W 16:40:38 Total Errors in Sector: 2,040 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850888, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x63 W 16:40:38 Total Errors in Sector: 2,039 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850889, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x7B W 16:40:38 Total Errors in Sector: 2,046 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850890, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x39 W 16:40:38 Total Errors in Sector: 2,040 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850891, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x4A W 16:40:38 Total Errors in Sector: 2,041 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850892, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x18 W 16:40:38 Total Errors in Sector: 2,038 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850893, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x7E W 16:40:38 Total Errors in Sector: 2,042 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850894, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0xAF W 16:40:38 Total Errors in Sector: 2,041 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850895, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x83 W 16:40:38 Total Errors in Sector: 2,039 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850896, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x66 W 16:40:38 Total Errors in Sector: 2,037 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850897, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x1A W 16:40:38 Total Errors in Sector: 2,039 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850898, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x93 W 16:40:38 Total Errors in Sector: 2,037 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850899, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x1D W 16:40:38 Total Errors in Sector: 2,042 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850900, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x65 W 16:40:38 Total Errors in Sector: 2,042 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850901, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x43 W 16:40:38 Total Errors in Sector: 2,035 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850902, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x95 W 16:40:38 Total Errors in Sector: 2,031 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850903, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x6C W 16:40:38 Total Errors in Sector: 2,034 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850904, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0xED W 16:40:38 Total Errors in Sector: 2,041 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850905, Offset: 0 W 16:40:38 Device: 0x00 (Empty Sector!) W 16:40:38 Image File: 0x09 W 16:40:38 Total Errors in Sector: 2,044 I 16:40:38 Verifying Sectors... W 16:40:38 Miscompare at LBA: 8850906, Offset: 0 W 16:40:39 Device: 0x00 (Empty Sector!) W 16:40:39 Image File: 0x2D W 16:40:39 Total Errors in Sector: 2,043 I 16:40:39 Verifying Sectors... W 16:40:39 Miscompare at LBA: 8850907, Offset: 0 W 16:40:39 Device: 0x00 (Empty Sector!) W 16:40:39 Image File: 0x36 W 16:40:39 Total Errors in Sector: 2,025 I 16:40:39 Verifying Sectors... W 16:40:39 Miscompare at LBA: 8850908, Offset: 0 W 16:40:39 Device: 0x00 (Empty Sector!) W 16:40:39 Image File: 0x9E W 16:40:39 Total Errors in Sector: 2,041 I 16:40:39 Verifying Sectors... W 16:40:39 Miscompare at LBA: 8850909, Offset: 0 W 16:40:39 Device: 0x00 (Empty Sector!) W 16:40:39 Image File: 0x57 W 16:40:39 Total Errors in Sector: 2,040 I 16:40:39 Verifying Sectors... W 16:40:39 Miscompare at LBA: 8850910, Offset: 0 W 16:40:39 Device: 0x00 (Empty Sector!) W 16:40:39 Image File: 0x71 W 16:40:39 Total Errors in Sector: 2,043 I 16:40:39 Verifying Sectors... W 16:40:39 Miscompare at LBA: 8850911, Offset: 0 W 16:40:39 Device: 0x00 (Empty Sector!) W 16:40:39 Image File: 0xB6 W 16:40:39 Total Errors in Sector: 2,042 I 16:40:39 Verifying Sectors... I 16:43:12 Exporting Graph Data... I 16:43:12 Export Successfully Completed! I 16:43:12 Operation Successfully Completed! - Duration: 00:12:11 I 16:43:12 Average Verify Rate: 33,032 KiB/s (7.5x) - Maximum Verify Rate: 57,643 KiB/s (13.1x) What exactly does it mean by Empty Sector? That it attempted to write a sector but no sector was written?

Be sure you don't buy the Verbatim DVD+R DL's you find in a brick and mortar store. They will be CMC Magnetics. CMC is the worst manufacturer of optical discs out there. Probably half of the problems people report here with burns are caused by CMC media. You'll want the DataLife Plus brand. Unfortunately, you can only find them online. I get them from Amazon.com in the US.

Yeah, as LUK said, I'd first target replacing the Ritek DVD+R DL media with Verbatim DataLife Plus MKM DVD+R DL. I had 5 Ritek DVD+R DL's as a test and though they completed write and verify, 3 of them were unreadable a few years later.

I built a DVD Video image and tried to burn it to a DVD+RW but it said it would require overburning. I checked the Image Information and it said Minimum Required Media was DVD-R/RW with Free Space of 1,507,328 bytes. So, I'm guessing DVD+RW is slightly smaller in terms of writable size than a DVD-RW?

UDF 2.6 is probably what you want for 256 character file names ala Windows. I'm only guessing, but except for DVD Video, which I let ImgBurn choose the best settings for, I use UDF 2.6 for all data jobs. As for CRC, I think that only occurs when there's an error. Cyclic Redundancy Check.

Aye, 'tis not there, Cap'n.

Well, without getting too technical, you're mostly right. Because of the various factors of file systems and how files are stored, you won't get exactly 25 GB of files on a disc. However, the difference between what you'll get and what is available is under 25 but above 24, by only a fraction of a difference. Anyway, the practical answer is yes. In Build mode, you will be told at the bottom of the window how much space you've used and is left for adding more files.

On multiple layer video images, i believe the layer break is set so that no file spans across different layers per the standard. Correct me if I'm wrong. But what about with data images that aren't video? If you have a file that is too large to fit on the first layer, will part of it be on the first layer and part on the second layer? Or will the file be written only to the 2nd layer where there's full space for it?

Then, here's my apology to Asus. I'm sorry for the wrong accusation.

I've got several BD-RE's, nearly full, sitting around I can use to Read in. I'll try that. Actually, found an M-Disc BD-R more handy to read in. I 18:35:43 Operation Started! I 18:35:43 Source Device: [0:0:0] ASUS BW-12D1S-U E401 (D:) (USB) I 18:35:43 Source Media Type: BD-R (Disc ID: MILLEN-MR1-000) I 18:35:43 Source Media Supported Read Speeds: 12x I 18:35:43 Source Media Sectors: 9,781,600 I 18:35:43 Source Media Size: 20,032,716,800 bytes I 18:35:43 Read Speed (Data/Audio): 56x / 56x I 18:35:44 Read Speed - Effective: 5x - 12x I 18:45:23 Operation Successfully Completed! - Duration: 00:09:34 I 18:45:23 Average Read Rate: 34,082 KiB/s (7.8x) - Maximum Read Rate: 48,089 KiB/s (11.0x) So, that Average Read Rate is more than 25 MB/s? If so, that shows this drive is USB 3.0, doesn't it? If it does, I owe Asus an apology.

Is the "transfer rate" the same as the Read Rate during a Read of a DVD-R to an image file? I 17:55:43 Average Read Rate: 14,555 KiB/s (10.8x) - Maximum Read Rate: 20,760 KiB/s (15.3x) I can't do the math easily in my head, but does 20,760 KiB/s translate to roughly 20 MB/s? Or 25? If it does and if the transfer rate is the same as the Read Rate, then it says it's USB 3.0, I'm guessing? If the transfer rate is not the same as the Read Rate, how do I determine the transfer rate from such a Read?

Asus are liars! I put in a USB 3.0 cable on the drive and connected it to a USB 3.0 port. Guess what ImgBurn returns? I 17:17:03 -> Drive 4 - Info: ASUS BW-12D1S-U E401 (D:) (USB 2.0) This drive IS a USB 2.0 drive, despite it being advertised as a USB 3.0! Why else include only a USB 2.0 cable? So, the blue colored port on the Asus drive is a lie.

If I uncheck Images Still Queued in the Display Warnings under General Page 1, will that stop the prompt to save the queue when ImgBurn is closed and a disc has been read to an image file, but the image file itself hasn't been burned yet? Sometimes, for testing purposes, I read discs to image files in ImgBurn that I have no intention of burning. Just read tests for already burnt discs. When I close ImgBurn, I get a prompt asking me if I want to save the queue. Thanks!

Had a chance to test writing an image to a CD-R in the Asus. Destination Media Type: CD-R (Disc ID: 97m24s01f, Taiyo Yuden Co.) It was a small DVD Video job that I don't have time watch right now and it's not very important as it's only a temporary archive of a project I was working on. So, I thought it would be a good test. Image burn and verify successful. CD-R read to an image file by ImgBurn in one of my Pioneer's. Image file mounted to virtual drive successfully. DVD Video processing successful, so it's a pretty good indication it's good for CD-R, especially a good TY media like I used.