dbminter

I don't know the details. I'm just going on what Ch3vr0n said. It looks like you're going to have to replace your DVD burner and the type of discs you will need. Others will have to tell you what drives properly overburn; I don't know that information. I didn't know, in fact, that only certain DVD DL discs support overburning, apparently. I've only heard of Media Range from people who post on this board who use it, but they are probably cheap discs. Especially for DVD DL burning. Basically, the only DL's that work with regular fluidity are DataLife Plus (NOT Life Series) discs from Verbatim, which you can only get online. I'm guessing these discs are okay for overburning?

Good catch, Ch3! I didn't notice those were thermal printable labels in the image. I don't have a CD label printer but I always use the inkjet printable label surface discs to burn to, unless they're intentionally for temporary backups which will be destroyed after their usefulness has ended, discs to give to others, etc. I use them in case I ever do get such a printer, I can print labels on them later. And even if I never do get such a printer, I can always write on them with CD markers to write a title or some other identifying information on the inkjet printable surface.

You could try mounting this .IMG file in a virtual optical disc drive. If it won't mount, ImgBurn will most likely not burn it. And you've already shown that ImgBurn probably can't handle RAM disk type image files. If I had to hazard a guess, those types of image files aren't compatible with optical disc burning. I believe .IMG was also the image file format for making images of floppy disks back in the days of those drives. Those definitely have FAT type tables, so they're no good in an ImgBurn situation like the one you're trying to use it for.

I'm not entirely sure as I've never seen the good Verbatim BD-R is packaging that says DataLifePlus on it. However, those are printable surface media, so that might explain it. I haven't bought any of those in years and am still working on my cake stack of them. If it says DataLifePlus on it and there's a premium on the price, well, there's a reason it probably costs more. It's the good stuff.

Even if they finish burning and verifying, CMC media generally doesn't last very long. I had some like 15 years ago. After a year, they weren't readable. And this was from a stack of like 200 where half of them failed to burn or verify.

You might want to, then, remove ImgBurn from the equation. Just copy the contents from the disc in Windows/File Explorer to a temporary location to do the "reading." Then, create a new DVD Video job in ImgBurn with that content.

What exactly are you trying to do? Do you have an already written CD-R disc with data on it that you want to copy over to a new data disc with the Joliet file system? I'm guessing this disc has data on it and is not an audio CD?

Can't tell from that. You'll have to insert one of the discs to find out. ImgBurn will tell you in Write mode in the right hand side pain something called Disc/Manufacturer ID. If it says VERBAT-IM or some variant, they're good. If they say CMC anywhere in them, they're bad. Right hand side pain?! Obviously, I meant pane.

Be sure they aren't Life Series. If they're Life Series, they're some of the worst you can get. You need DataLife Plus discs you can only find online.

Yes, Verbatim is, pretty much, the only viable option for double layer DVD. Get the DataLife Plus series you can only find online. NOT the Life Series you find in brick and mortar stores.

Yeah, the last LG model was a real mess. Just fine for single layer BD media, but absolutely terrible at writing DL BD media. 9 times out of 10, it fails Verify. If you formatted a Verbatim BD-RE DL as a giant floppy, the data written to the 2nd layer is always corrupt. I have the current Ultra HD LG model, but I only use it because I needed something that reads and write Ritek 6x DVD-RW. The LG BD model is the only BD drive that will do this. I don't really feel like putting this model through a bunch of tests on BD-RE DL media when I know, for sure, the Pioneer BDR-209M will handle them just fine. The first ASUS I had was a USB model that passed every test I threw at it. So, I had high hopes for their latest internal model. Thus, I bought it and immediately regretted it.

I only ever use Verbatim BD-R. They're blue text on a white background labeled. They're rated at 6x, but can be written much higher with some drives, like mine. Ritek media can be kind of iffy. I'd see if the better quality Verbatim still causes issues with your drive. Like LUK said, if these better discs still cause you problems, then the solution is most likely a new drive. I only use Pioneer's BDR-209M BD burner. I've been using it for like over 5 years now. I had one that was still working after 2 years and only replaced it because the early runs of that model had an issue where pressing the Eject button didn't always work the first time after a few months. Pressing it a 2nd time would always work. And using Eject commands always worked. There's a newer Pioneer Ultra HD BD burner, but I've never tried it. I believe I used Verbatim BD-R with an ASUS drive before without issue. I ended up returning that ASUS drive, though. The newest ASUS model on its initial firmware had a big deal killer: it destroyed rewritable media Ritek 8x DVD+RW and Verbatim BD-RE!

Sometimes, something as unlikely as simply powering off and restarting Windows does wonders. Sometimes it does diddly!

Actually, I had a cause to just now write a BD-R so I thought I'd check it out while I was at it. There actually are write descriptors on the disc, so ImgBurn is returning, for beyond 6x. However, it may be that write descriptors are returned by the drive itself and not necessarily the media. I don't know. I mean, why would they print 6x on the media and the packaging when it can actually write at twice that rate? It would be more of a selling point on the package to list higher rated speeds if they really are available.

If your drive is 9 years old, it's well beyond twice the life span I've gotten from my best Pioneer. So, yeah, I'd say it's given up the ghost. As for the other thing about write speeds, it does seem a drive is capable of writing a media at greater than its highest listed write descriptor. It seem the drive manufacturer has tested that media at higher rates and they weren't corrupted by the faster writes. So, they "rate" them in the write strategies at higher that available writes in the write descriptors.

My BD-R are physically labeled as 6x. Don't know what the actual write descriptors on the disc are because I don't care! I only care about what speeds I can get from the drive. So, I haven't checked the actual write descriptors on one of these BD-R in ImgBurn and it's not something that interests me to do so.

I don't know for sure, but I would guess there isn't a write descriptor on the media for anything more than its highest maximum rate. The ability of the drive to write at higher rates of speed is down to the write strategy in the burner's firmware.

Many drives are capable of writing BD-R media capped at lower maximum write speeds at higher rates. For instance, my Verbatim BD-R are rated at 6x, but the Pioneer BDR-29M writes them at about 12x max.

I'm no expert, but I would have to say that if anything is done before Writing LeadIn to prepare a disc for writing, it must be super quick.

Ah, yes, I had Unicode support disabled, too.

Were you able to burn these Ritek discs before successfully under firmware revision 3.03? Or did you just recently update the firmware and it stopped working? If the latter is the case, there's probably a bug in the firmware for that media write strategy. Wouldn't surprise me. I had 2 of these drives in 2016 and they were terrible. I sent the 2nd one back after it did the same thing as the first: destroy Ritek 8x rewritable DVD+RW and Verbatim 2x BD-RE. I'd hope these firmware updates since 2016 would have improved this drive by now. I wouldn't necessarily throw the drive away off the bat. First I'd try some better BD-R like Verbatim. If you got the same write failures on better quality media, then I'd suspect the drive or the firmware is the problem. I threw my first one of these drives away only because I couldn't return it. I'd taken off the bar code from the box for a refund so I couldn't return it. The 2nd one I got to see if I had just gotten a bad unit, but it was just as bad. So, I was able to return that one. I'd have hoped firmware revisions might improve the performance of this drive by now.

Windows caps the maximum number of displayable characters, for a reason I'll be damned if I can figure out. So, probably, most other software is just returning what Windows does. Or the other software sets its own crippling limits for reasons only the author knows. As for your original question, I created a new job in ImgBurn using UDF 2.60 and the maximum UDF label field length is 126 characters. I created a new job in ImgBurn with 2.50 and it too is 126 characters. As for why ImgBurn is capping you at 64 characters, I don't know. The ISO label is 32 maximum, it seems. Joliet is even less, half that. VolumeIdentifier may be something different, though, than what Windows returns as the disc label. Windows should normally read the UDF or ISO labels.

I was wondering if the absence of the DID entry might be indicative of a possible problem with your drive. However, on further consideration, it seems more likely that those Optical Quantum discs may simply not have a DID present on them. I'm guessing if ImgBurn doesn't find a DID label on the media, it doesn't return anything? I've never seen a media format corrupted error before, so I can't say what it means. Maybe it was the Ritek discs that were the problem. However, that doesn't address your initial concern. If ImgBurn does any kind of writing to discs at the gathering of files stage. Were you creating an image file or writing these files on the fly to the BD-R? If you were writing on the fly, I can see it writing a packet of files, gathering some more, and then writing those while gathering some more. That might explain why some content was written to the disc. If you were creating an image file first and that was when the gathering of files was done, then nothing would have been written to an inserted disc because no access to the drive was being performed.

DID is Disc ID. It tells who manufactured the disc. It's generally a line in the log that I usually see. So, I didn't see it going over the logs and I was curious as to why it wasn't there.

The thing I noticed that was odd, to me anyway, was why did neither log seem to indicate, that I could find, what the DID of the BD-R was.