dbminter

Wouldn't be ImgBurn's issue, most likely. ImgBurn just sends default eject commands that work on all optical drives. If a tray is not ejecting all the way out, it wouldn't be ImgBurn's fault as it has no control over that.

I wouldn't worry. The MKM-003's apparently only have Write Descriptors for 4x minimum. If you want to burn at 2.4x, MKM-002, which I am guessing would be the 4x maximum write speed discs, might write at 2.4x, but definitely MKM-001, which I am guessing would be the 2.4x discs, would. I only ever worry if the Verify fails or returns read errors. And I always write at 8x and have only ever had 1 disc die on me later after it burned and played correctly that wasn't down to not using MKM discs.

I would recommend either the IFO or BUP. I use BUP when available. The reason neither can be previewed is those two types of files are not video content. The .IFO controls the DVD player how to navigate the .VOB files, which are the previewable ones. .BUP is a backup for the .IFO files.

I don't know. I don't think I'd ever heard of that model before. I just guessed based on the drive ID string that it was an LG model and, because of that, equated that could be an issue since there was one with the NS40 and double layer BD.

The issue is probably using double layer BD-R with what appears to be the LG BD drive you're using. I know at least 1 past LG BD burner, the WH16NS40, did not properly write to double layer BD media, even though it claimed to support it. 9 times out of 10, it would fail. The NS60 does not, which is why I use that drive even though I don't need the quad layer capabilities of the NS60. So, I would try 2 different things. One: don't use the Ritek BD DL media. Verbatim media, and by "Verbatim" I don't mean the CMC stuff that they also release, is the only quality double layer media. However, depending on where you live, Ritek media may be the only kind available. Two: try a different BD burner model like the NS60.

Try this. In Build mode, there's a tab on the main landing called Options. Under Options, see if Recurse subdirectories is checked. If it is checked, uncheck it, and try again. See if that does what you want. This is a universal setting, so, every time you add a folder, no subfolders in that folder should be added.

At what point in the burn does this happen? Analysing Tracks is more of a read operation thing. Also, with certain combinations of hardware, PSX games can't be read in by ImgBurn.

I recommended the OP check the firmware because I wasn't aware what the current firmware version was. An update might have been released and the OP might have had a drive that was never flashed with any updates since leaving the factory.

There is precedent for running changes in media manufacturing that require firmware updates to make them work with a drive again. For years, Verbatim MCC DVD-R were fine with the LG WH16NS60. Then, they started constantly failing on any NS60 I tried. I told LG this and after the next firmware update, MCC DVD-R resumed working properly with the NS60.

I abandoned LiteOn years ago as they made my first BD burner and it was junk. So, I don't know anything about their quality anymore. It is not a slim model unit, so that wouldn't be the problem. No, there is no software that will determine a drive is bad. You could check for a firmware update to the drive, apply it if it exists, and try again. In Write mode, right click on the drive in question and choose the last item in the context menu which should be to check for a firmware update. If Verify completed and DiscSpeed returned no errors, that's good enough for me. I don't even bother with DiscSpeed results at all.

I would doubt it's the discs as you're using MCC in the Disc ID from the screenshot shows. So, you're using Mitsubishi media, which is the best out there. Thus, I would put it down to your drive. Either it's reached the end of its life or it has a firmware conflict with that particular media. Is your burner a slim line model? That could also be the problem.

It depends on what you want these MP4's to do. If your Blu-Ray player supports playing container files like MP4 from a Blu-Ray disc, then it's fairly straightforward. However, if it's like DVD, you must convert the MP4's to Blu-Ray Video format in order to put them on a BD-R, pop it in, and have your Blu-Ray player play the disc.

The maximum size a file can be for the ISO 9660 format is 4.2 GB. That's why 8 GB is too large. You will need to select UDF. Don't use the Write files and folders to disc option. Use Create image file from files/folders first. This will allow you to make such necessary file format changes and ImgBurn should, though I don't know for sure in this case, prompt you as to what options you should be using for files that don't meet your current file format standard. Then, once you create an image file with this option first, you need to load that file you created in Write image file to disc. You may want to go over the various Guides: https://forum.imgburn.com/forum/4-guides/ Particularly, you should look at this one:

It's analogous to a file on an HDD. It may be 1 MB, but it actually takes up slightly larger than 1 MB of space because of various metadata overhead.

The more data you burn to a disc, the larger the extended area of the burn ring. So, 250 MB will have a smaller area than 1 GB. However, if you're burning a double layer DVD Video, those employ what is known as padding. So, their ring areas may not necessarily be indicative of the actual size on the disc. For instance, I once burned a DVD VIdeo that was just a few MB larger than the size of a DVD-5. Yet, nearly the entire DVD+R DL burn area was used.

Well, the image file size should not be the same size as the 3 input files. The image file format is a container and therefore will be larger than its contents because of overhead, file system metadata, etc. So, when you burn an image size to a disc, there will be "more" burnt to it because it contains this various metadata overhead. I can't comment on the Write files/folders to disc option as I've only ever used it to test things other have reported problems with. But I would guess that it dispenses with the overhead metadata associated with a container file as no image file is written first. Plus, it depends on the data being written. For instance, a DVD Video should have theoretically different burn sizes because it uses a specific file system format type and associated metadata for DVD player playback compatibility.

DVD-RW doesn't just go read only and there's no way as far as I'm aware of to make a DVD-RW read only like you could with a floppy disk switch or the switch in a DVD-RAM cartridge. It's either read only DVD-R to start with or your drive is read only only. Or something is wrong somewhere. When you first open ImgBurn, copy and paste everything from the Log window. Next, in Write mode with the "DVD-RW" inserted into the drive, copy and paste everything from the right hand side pane of information.

This is most likely the reason: I 20:34:39 Destination Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.) CMC makes the worst discs out there. I would try better quality discs first. Like TDK or Verbatim. If you're going to use Verbatim, however, make sure you have the RIGHT Verbatim. NOT the Life Series you find in stores; those will be CMC. Get the DataLife Plus (NOT Life Series.) or discs labeled as AZO, which you will only find in online stores, usually, like Amazon. Another possible culprit is the log indicates you're using a slim model drive. Slim models tend to be junk.

Are you talking about image files or files being written to an image file? If you're talking the former, that's already a feature in ImgBurn. ImgBurn will lock in image files it's currently burning to disc. The only exceptions are the .MDS, etc. metadata files. And, I think if you have file splitting on an image set, ImgBurn only locks the portion it's currently burning from, but I could be wrong about that.

There's a way to tell a USB device's USB version. Download USBTreeView.

If you burned many similar sized discs before and it worked, then the problem could be the drive itself. It may need replacing. You may also want to try a BD-R 50 other than Ritek. Like Verbatim's VERBAT-IM media.

I have some older MP3's back from 1997 when I first started ripping CD's with a piece of software called MusicMatch Jukebox that were like 160 KBPS back before I knew of the different quality settings. 160 was the default. Once I learned the "difference," I changed the default to 320.

For 2 decades, I stuck with 320 KBPS MP3 because that was good enough. But, with the abundance of free space available now on things like USB HDD's, I switched to FLAC. And iTunes, which I primarily use now for CD extraction, uses M4A, but I choose Lossless for the quality of the rips.

If you want ImgBurn to burn FLAC to Audio CD, you'll need to download and run something called madFLAC.

Yeah, it sounded like on your previous attempt you were trying to burn another data CD with the container files rather than the CUE file, which does the conversion of the container files to Audio CD format.