dbminter

madFLAC isn't perfect. There have been some FLAC I've come across that it would not process, so I converted them to uncompressed WAV for input.

I don't use LAV. I use madFLAC to do my FLAC processing to make Audio CD's in ImgBurn. In all the time, like 15 years or so, I've been using madFLAC, I've never had it interfere with any audio processing in ImgBurn or any other audio/video application I've used.

To copy CD Audio discs, you use the Read function as defined in the first link in the first Guide I pasted:

The PS2 laser assembly base unit would be newer than the ones in the PS1. In theory, that would mean better read compatibility. I know that certain DVD-R could be played on the PS2 for things like DVD Video. I used to do it as far back as 2002, but, even then, random skips and playback problems would occur because the PS2 was simply designed before the creation of DVD-R. However, future PS2 models improved playback compatibility with DVD-R, which means that as the lasers got newer, they got better at reading recorded discs. Which would bolster the idea that as the PS2 improved, it would have better playback for CD-R.

Yeah, that's the ASUS I have bookmarked to try out in November. Someone else on this board had tried it out and it seemed to do the trick for solving their issue. I just never have had any BD-R DL before. Just BD-RE DL. I needed rewritables for monthly system backups so I could reuse the discs and my backups were all larger than a BD-RE SL. I've since moved to USB SSD's because they're much larger and read and write much faster. I also as a matter of "trust" that I only use DL media when I have to. Like for those backups I mentioned or DVD+R DL for DL DVD Video discs. When you go beyond one layer, you double the chances of having a read issue, right at the layer change(s) most often than not, as seemed to be happening in your case. So, I could have saved space with BD-R DL discs for backups which also would have read and written faster than the rewritable DL's, but I didn't want to run the risk of, years later down the road, a backup being unreadable. So, I stuck with single layer BD-R. To put it into perspective, in the 10 years or so I've been burning BD-R's for backups, I only just a few weeks ago encountered my first that wouldn't read. And that was something I "knew" years ago when I wrote it. The drive was dying and there was a recovered read error during Verify on burn. I performed a manual Verify on that same disc and it passed that time. However, that drive that burned it was replaced shortly after that due to various Verify failures on future burns. I should have burned the data again in the replacement drive while I had live copies, but I didn't. Thankfully, it was temporary files that I managed to recover from other sources a few weeks ago, so I didn't lose anything.

The actual drive in the OWC setup is an LG. I'm not familiar with that particular brand, but I do know the WH16NS40 did not properly write to BD-R DL and BD-RE DL. 9 times out of ten, they would fail verifies. Now, that was some years ago, so a firmware update to LG drives like the NS40 might have fixed it. The issue wasn't present in the NS60, but LG discontinued that model. You could try seeing if there's a firmware update for your drive. In Write mode, right click on the drive from the drop down menu and select the last option in the context menu, the one to check for a firmware update. Install the latest one if there are any and try again. If that doesn't work, the only thing to try is a different drive. Preferably not an LG model. I use ASUS's BD internal drive in a VanTech USB 3.0 enclosure, but I've not tested any DL BD discs in it. If you're going to use your own external enclosure with a BD drive, you will need a USB 3.x enclosure; 2.x won't do. ASUS makes an external BD drive, but I've yet to test it. I intend on getting one probably in December, but I don't have any BD-R DL to test it with. I've never even burned a BD-R DL before, only BD-RE DL.

This isn't really a bug, per se. More like a request to adjust disc type determination logic. Here's the scenario: I was trying to create a DVD Video disc with a VIDEO_TS in the root directory. The root directory also had an AVI file in it. ImgBurn detected the VIDEO_TS folder and then asked me if I wanted to make a DVD Video disc, which I said yes to. ImgBurn THEN detected the AVI file and asked me if I wanted to make a Divx Disc. I said no to that. Should the ImgBurn logic in this case determine if the user makes one choice, like in the above situation, it should refrain from asking to change the disc type again? Thanks!

Now, I've never copied a DVD Audio disc as I've never bought one, only created them myself, so I don't know if they're copy protected. Same for Bu-Ray Audio, which I didn't even know existed. I don't know if those are copy protected or not or if they can be. If they are, then we can't help you copy copy protected discs.

All disc copies are made the same if you use the Read and Write modes of ImgBurn. There are a few guides that you may find worth going over to answer your questions: Concentrate primarily on the first Guide listed as that should cover almost everything.

Under the Information tab in Build mode, is the Auto box checked or unchecked? If it's unchecked, try checking it.

Had another oddity. Just burned a DVD+R DL that passed Write and Verify. Then, I went to Read the same disc I had just finished Writing and Verifying and the read rate plummeted to 0.01x at the layer change. I powered off the drive, powered it back on, and tried again. The 2nd attempt to Read the disc afterwards succeeded.

Had another oddity. Just burned a DVD+R DL that passed Write and Verify. Then, I went to Read the same disc I had just finished Writing and Verifying and the read rate plummeted to 0.01x at the layer change. I powered off the drive, powered it back on, and tried again. The 2nd attempt to Read the disc afterwards succeeded.

I do believe that first failed read was a fluke due to a behavioral "bug" either in the drive, Windows, or the OWC enclosure the drive is in. Unless you use the Eject context menu item to eject discs in File Explorer, the metadata of disc contents is NOT updated. The downside of this is if you don't do it, when you copy the contents of one disc in File Explorer without Ejecting, File Explorer is trying to copy nonexistent data from subsequent discs inserted into the drive.

I do believe that first failed read was a fluke due to a behavioral "bug" either in the drive, Windows, or the OWC enclosure the drive is in. Unless you use the Eject context menu item to eject discs in File Explorer, the metadata of disc contents is NOT updated. The downside of this is if you don't do it, when you copy the contents of one disc in File Explorer without Ejecting, File Explorer is trying to copy nonexistent data from subsequent discs inserted into the drive.

Interesting how that drive apparently supports DVD-RW DL reading and writing since DVD-RW DL was NEVER manufactured.

If the Super DVD is to be a viable format, it has to make a quantum leap in write speed. However, it is based on 3-D memory and not optical storage. 3-D memory may be super fast at writes. Without it in consumer hands, we'll never know. And it's not even in enterprise hands yet as it's only just a recently announced technology. However, I think your math is off. If it takes 20 minutes to write 25 GB, 1 petabyte is 125 TB. 125 TB is 125,000 GB. (Well, let's just conveniently ignore the 1024 factor. ) So, 125,000 divided by 25 GB is 5,000 20 minute writes. That's 100,000 minutes / 60 minutes in an hour / 24 hours in a day is 69.4 days.

One thing I noticed in your screenshots. I see the text CMC MAG, which means you're using CMC Magnetics discs, which are the worst quality out there. Over 50% of the problems we see on this board are caused by CMC Magnetics media and when people switch from them to the high quality media, their problems usually go away. Try to find Verbatim DataLife Plus DVD-RW. NOT the Life Series you find in brick and mortar stores. Those will be CMC. You can generally only find the DataLife Plus stuff in online stores.

I would say so. PS1 games were on CD where layer breaks weren't a concern. However, I can't recall seeing .MDS ever associated with a PS 1 game CD image. Of course, I'm just going by ImgBurn, which I can't remember that it used MDS in its file set, but maybe it did.

I think at one time, the bypass trick was even easier. You just entered in no account name and password and repeated it several times in a row. Each time, you'd be told to enter something, but after a handful of attempts, Windows setup would go to setting up a Local Account. Microsoft quickly removed that impediment, of course.

Thanks for that Microsoft account workaround! I knew it existed, but I couldn't recall what it was. My setup is okay as it was a Windows 10 that I created back when local accounts were possible and upgraded to Windows 11. But, on my next new PC, I wanted to create a local account, but couldn't remember how to do it.

It's hard to know which error you're specifically talking about as the log displays multiple different errors from different failed burns. However, it points out a few possible issues. You're using the MCC media, so you're using the high quality stuff. Not junk media, so we can rule that out. The thing that immediately leaps out is the combination of semaphore timeout errors and the drive's listed USB interface of USB 1.1. USB 1.1 is ancient and super slow. You could be getting semaphore timeouts because the drive is not reading/writing fast enough. If you're going to use USB BD writers, you need USB 3.0 to avoid drop outs of data. However, semaphore timeout errors can also be a conflict between the USB bridge in your burner and the USB controller on your motherboard. So, what can you do? 1.) If you want to keep using that same drive, try connecting it on a USB 3.x port. 2.) Try a different drive, however, there's no guarantee X drive will work properly with the USB controller on your motherboard. 3.) Replace the USB controller on your mobo. However, there's no guarantee the next one will be any better and it's often times just cheaper to replace the mobo. Which isn't, of course, a cheap option to begin with. If you're going to go that route, you're better off buying an entirely new PC. Again, though, there's no guarantee a different PC's mobo won't have the same issue.

Most likely, if ImgBurn said Disc Not Empty, either your DVD-R actually isn't empty or your DVD "burner" is actually only a read only model. Or could be a firmware conflict with the drive and the type of DVD-R you inserted. I'd first start off with providing some information. When ImgBurn first starts, copy and paste everything in the Log window that appears on start into a reply here. I'll proceed from there. I don't understand what you meant when you said "when I use format with imgburn it doesnt show DVD-R option." You can't format DVD-R except as a giant floppy option in File Explorer. And format would only show up as an option in ImgBurn if you used DVD-RW or DVD+RW.

I've got a somewhat concrete value of how high quality the Verbatim VERBAT-IM BD-R are. I've burned over a thousand probably over the last 10 years. Out of those, I've just encountered my first one that failed to read data back properly on it. However, this was most likely because the disc was not written properly back in 2016. On Verify of this disc, there was an unable to read sector error that was corrected. Immediately after this, I swapped out the LG WH16NS60 for a new one. A manual Verify of that disc passed, but it was most likely not written properly to begin with. All other failures were either immediate burn errors or failure on Verify which were caused by dying NS60's. Once swapped out with new ones, write and Verify problems ceased.

To be fair, that disc it failed on was a bit beyond the norm. It was a mixed mode CD created by Nero Burning ROM. The 2nd attempt to burn the disc worked but failed to read it one sector based on an illegal mode for the track.

To be fair, that disc it failed on was a bit beyond the norm. It was a mixed mode CD created by Nero Burning ROM. The 2nd attempt to burn the disc worked but failed to read it one sector based on an illegal mode for the track.