dbminter

This happens only rarely, but it does occasionally happen. Because it is so rare, it seems impossible to debug such an issue. What happens is sometimes in Build mode, dragging and dropping a folder into the Project does not add the folder. Instead what gets added are all of the files and subfolders in the ImgBurn installation directory. So, files like ImgBurn.exe and other executables get added. This just happened to me for the first time in a long time, but it does occur from time to time. What generally happens is deleting those ImgBurn folder files and dragging and dropping the same folder again works. Thanks!

To the first question: no. USB 3.x devices reporting as USB 2.x is a cosmetic error in the software. Back when the last gold release of the software came out, there was no USB 3.0. So, ImgBurn identified USB 3.0 as USB 2.0. This has been fixed in later betas and when the next version of the software comes out (And, no, don't ask when that will be.) it will be addressed. In the meantime, ImgBurn will (In general.) use USB 3.x speeds on USB 3.x devices. To the second question: depends on what you mean by "properties." If you mean what Device Manager will return, as far as I know, no. However, in Write mode, if you right click on a drive, there is a Capabilities list that displays some meaningful hardware properties of the drive.

It was actually quite a surprise that Pioneer released the new 2213 model about 2 years ago. No one else was releasing anything new and many were discontinuing optical drives because they're a dying breed. There's little profit in them. While there's still use and demand, it's not really enough to bother with. So, companies simply don't care. Another reason why firmwares are so borked, despite repeated e-mails to tech support stating the problems.

I stopped testing the 3.10 firmware after the DVD+R DL failure, so I can't say what else may not have worked. And I can't recall what I tested before. Probably 8x DVD+RW and MCC DVD-R. Yes, the reason the 3.11 firmware was never released to the general public to update their drives was two fold: 1.) if they released an update package, it could be extracted and modified 2.) why let users update old drives when they can buy an all new one to fix the issues ASUS started? There is no way to upgrade to 3.11 firmware other than by buying an all new drive with it installed from the factory. ASUS has told me, though, that 3.11 is the end of life firmware and that that drive won't receive anymore firmware updates. Pioneers are great drives if you never plan on burning 8x DVD+RW on any Pioneer drive or 8x DVD+R DL at anything other than 2.4x on the 2213. Can't say what the performance of DVD-R DL is on the 2213. I've not used any in like 10 years and I only used those as temporary storage as they weren't good for DVD Video. After going through that batch I bought to try out, I never tested again. So, depending on the manufacturer, 8x DVD-R DL might burn at 8x in the 2213. However, I would be willing to wager that the quality DVD-R DL, if Verbatim still makes them, would behave the same way.

That firmware is ancient. There is a 3.10 firmware. Try updating to that and see if it makes a difference. There actually is a firmware 3.11, but you can ONLY get that on factory shipped units. The 3.10 firmware was the last package you could download. The 3.10 firmware had an issue of its own, though. It borked writing MKM 8x DVD+R DL, failing to Verify at the layer change. The 3.11 firmware fixed that. I never tested BD-R DL writing in the BW-16DHT as I've never burned a BD-R DL before. I've only burned BD-RE DL in the LG WH16NS40 and NS60. So, BD-RE DL testing was not something I did on the 16DHT when I tested it.

Pioneer was a non-starter for over 10 years if you wanted to write 8x DVD+RW media. Always failed Verifies. Didn't always do that. Only after a firmware update they never fixed for over 10 years. The 2213 fixed that, BROKE it again, and then fixed it, but now the firmware for the 2213 only writes at 2x to 8x MKM DVD+R DL. IF Pioneer can fix that with the next firmware AND NOT break the 8x DVD+RW AGAIN, the Pioneer will be a great drive again, like it was 10 plus years ago. However, Pioneer has not updated the 2213 firmware since September 30th, 2023. The only problems with ASUS's BD drive is it only writes at 12x to 16x BD-R from Verbatim, it tends to be a bit of a slow reader for BD-RE discs, and does have a higher "random" failure rate than the LG. LG's WH16NS60 has problems of its own. It's a slower reader across the board and will not read some discs that other drives will. Ever since Pioneer borked their firmwares for 8x DVD+RW, the LG WH16NS60 was the only viable drive, despite its problems. They no longer make the NS60, so all you can get is the NS40. The problem with the NS40 was 90% of the time, it failed to properly write DL BD media, despite supporting it. I haven't used the NS40 in a long time so maybe a firmware update finally addressed that issue.

BTW, the drive is an ASUS BW-16D1HT 3.11 firmware in a Vantec USB 3.0 Gen 1 enclosure.

I've never encountered this Error Reason before: I 20:58:28 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 5863199) W 21:00:40 Failed to Read Sectors 1467200 - 1467231 - Reason: Timeout on Logical Unit W 21:00:49 Failed to Read Sector 1467200 - Reason: Logical Unit has not Self-Configured Yet E 21:12:02 Failed to Verify Sectors! What exactly does Logical Unit has not Self-Configured Yet mean? I simply burned the image to a 2nd BD-R and it worked that time. Thanks!

ASUS's current internal BD model, BW-16D1HT, is the one I use in a VanTech 3.0 Gen 1 enclosure. The WH16NS40 from LG is another possibility although last time I used one over 5 years ago, it failed to write BD DL media 9 times out of 10, backed up by other users who experienced the same thing on this board. Pioneer's current 213 model is ALMOST there. It's a year and a half old and needs to conquer a few firmware slow writes. For instance, it, too, only writes 4x to 8x DVD+R DL. I put in for a return on the external ASUS BD drive.

Another reason not to get that drive: it writes at only 4x to 8x DVD+R DL discs. If you're going to go with the ASUS, get the internal model and put it in a VanTec or Other World Computer USB 3.0 enclosure.

Be aware that I've just begun testing one of these external ASUS drives and right out of the bat, I notice it's a slower reader. Took 5 minutes to read 300 MB off of a pressed data CD.

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.