dbminter

As I said, the NS60 doesn't seem to be available anywhere. I couldn't find it on either Amazon.com or NewEgg.com when I last looked, but the NS40 was available on Amazon.com. Amazon's really good with their return policy. I recently tried out a Pioneer 213 and had to return it because Pioneer borked the firmware AGAIN! After a decade of borked DVD+RW firmware, they HAD fixed it on the 213, but BORKED BD-R, DVD+R DL, and CD-R. The latest firmware fixed all these issues but BORKED DVD+RW again! Amazon accepted my return with no issues.

Oh, that's my bad. I was going by the end of the log where it says this: I 12:04:57 Source Device: [3:0:0] PIONEER BD-RW BDR-212V 1.00 (G:) (SATA) I see later on you must have applied the 1.02 update. Another drive would isolate if it's the Pioneer's problem. That's why I recommended what I use. I know they "work" but that only means they "work" for me. They may not "work" for you. But, with a baseline, if they don't work for you, then that would probably help isolate if it's something else that is wrong.

You're currently on 1.00. You might as well try updating to 1.02. If it isn't firmware for your drive, it will most likely simply say it can't flash your drive, so nothing bad would have happened.

The BDR-212 is actually a BD burner. The 212V is not listed on Pioneer's firmware site, but the BDR-2212 has as its latest firmware 1.2.0.005. And other BDR lines have like 1.04 as opposed to your listed 1.00. You could try the firmware here: https://pioneer.jp/device_e/product-e/ibs/device_e/dev00001r_e.html#firmware1 Note if the firmware does not support your drive, the firmware update package will not alter your drive as it won't allow anything to happen to it. I recommended the LG line because it has the least amount of problems with it, and none fatal, except for the NS40 which didn't write to double layer BD media correctly.. Unlike Pioneer drives which for the past 10 years have had unaddressed firmware borks.

I would first check for a firmware update to the Pioneer drive. In Write mode, right click on the Pioneer drive and choose the last option in the context menu for checking for a firmware update. Apply that if found and see if that helps. You don't really have an apples to apples comparisons in all of these logs. You're using both good discs, the MKM's, and trash discs, CMC. However, you're getting it on good discs, which isn't normal. CMC errors are WAY too common. But, NOT on MKM's. Barring that, I can only recommend trying the LG WH16NS60, if you can find it, which is what I use. If not, try the WH16NS40, which you can probably still find, but note last time I tried it years ago, it did NOT write properly to double layer BD-R and BD-RE, even though it claims to support them. Note these two LG drives are BD burners.

Of course, LUK makes the final decisions regarding who is a beta tester, but I don't think we've had any new ones added in over 10 years. So, there probably aren't any openings for one right now. But, maybe you'll get lucky.

The current state is easier to answer. There was a beta released around November 16th of 2021. So, it's still being developed, just very slowly. As for why it doesn't appear to be updated, the answer is most likely the developer has a job. :)

Looks like you had a transient read error that ImgBurn recovered from. The image file is most likely okay. I'd only have worried if ImgBurn stopped reading all together. I can tell you what most likely caused the problem. This: I 06:28:52 Source Media Type: DVD+R (Book Type: DVD+R) (Disc ID: CMC MAG-M01-00) The disc being read is one CMC Magnetics's trash disc. CMC makes the worst discs out there. It is fairly common for read errors on those and to be completely unreadable after just a year or so.

Thanks! I'll try to remember that. Maybe add some text to the windows to mention CTRL+C can copy the message contents to the clipboard?

When an operation error occurs during an ImgBurn function, a pop up window opens with detailed error codes, etc. about the error. The way it stands now, the user must take a screenshot of these windows to gather troubleshooting information. I was thinking, if it's possible, to pipe these errors codes, etc. that appear in the pop up windows into the Log. That way, a person can copy and paste the error information from the Log, which is easier. As it stands, there is sometimes an error line in the Log, but if there is, it's nowhere near as detailed as the error windows that pop up. In lieu of piping the errors into the Log, I have another idea worth pursuing. Add some kind of button or function in the error pop up windows that display error information and let the user save a copy of the window/perform a screenshot from within the error window itself. That way, the user doesn't have to take the extra steps themselves to generate screenshots. Thanks!

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.