dbminter

Video "file?" Only one file? Then there's probably something wrong somewhere with the encoder because BDMV should contain multiple files, unless it's a really small video you've created. All in all, it seems there's a problem with your encoding software on this particular project. First, it created a BD that only loads menus. And now you can't get audio to play back. There's something wrong with the encoder or the player you're using doesn't support that audio codec, so you're getting silence on playback.

Most likely in a situation like this, the problem is with the authoring software. It didn't generate properly playable contents. Do you have an actual BDMV folder on your hard disk where the BD was generated? If so, try playing that folder in a software player on your PC. If it still doesn't play properly, it wasn't authored correctly. Have you changed the type of BD-R you've been using? I've never heard of Disc ID: OTCBDR-002-000 so it may be a cheap type of media. If you've always been using it, then you wouldn't care about that.

Yeah, I was wondering the same thing. If ISOBuster might do the trick.

Most likely, I/O errors mean either the disc was burned incorrectly or burned correctly and your drive is reporting it can't read it for whatever reason. As for what you can do, first we'd need to see a log of a burn where the verify fails. Under Help, choose ImgBurn Logs to access the log of a failed burn. Post the log of that write and verify where it fails. It will tell us what we need to know, like if you're using cheap discs, the most common cause of bad burns, or whatever else may be the cause.

While this isn't related to your questions, there is something you should be aware of, if you're not already. Your Saturn most likely must be modded in some way, either internally or externally, in order to play copies of games, I'm guessing. You probably can't just backup Saturn game CD's, pop them in, and expect them to play. At least, I'd think there must surely be some kind of copy protection that prevents this normally. The Playstation 1 and 2 did, and every console released since then has some kind of copy protection scheme embedded in it.

Yes, but I believe the 1.03 firmware update is only to appease Hollywood. It seemed that drive may be able to decrypt UltraHD Blu-Rays. So, a firmware update was rushed out to patch that hole. It's the only update in it. But, there were also 1.01 and 1.02 released in the 6 years since 1.00 came out. You'd be surprised at what can happen. The contents could be corrupted but only just corrupted enough as to still be "readable" just incorrect. Does Daemon Tools have its own tool for creating disc images? If it does, try creating a disc image in Daemon Tools and see if it can mount its own image. If it can't, then the disc is definitely the problem. You said it was a data CD, right? What exactly are the contents of this CD? Do you remember what you burned to it?

There may be a firmware update for that drive. It seems you have 1.00 firmware and there is a 1.03 for that drive. Check to see if that helps improve read/detection, if there is one. The drive string indicates it's an LG drive and I think I've had that model before. LG's aren't really very good readers. But, as you say, the disc is decades old and may have just reached the end of its life cycle.

Well, if it is a BD-ROM, you can't set the book type on a read only (ROM) drive. It has to be a writer.

Yeah, I don't think Verbatim makes any of its own media. They farm out, and, unfortunately, they farm out to the great (Mitsubishi) and the worst (CMC). Any Life series (Not DataLife Plus) CD or DVD media will be CMC, as will Verbatim's BD-RE SL. Mitsubishi and TDK make their BD-RE DL and Mitsubishi makes the DataLife Plus CD and DVD media. All I've ever seen are just plain called Verbatim BD-R, but they have the VERBAT-Im DID. So, I guess Mitsubishi makes those because I rarely have issues with Verbatim's BD-R.

When you just copy the MP4 to a BD, if your Blu-Ray player supports playing MP4 files, it will play it. ImgBurn will make an auto playing Blu-Ray from a BDMV and CERTIFICATE combination IF they're both compliant. IF they're authored correctly to auto start, ImgBurn will create a BD that will automatically play in a Blu-Ray player. Which is why it's best to have authoring software that doesn't create the ISO itself. To let ImgBurn create its own ISO. Most likely, this muxing software isn't creating compliant content. Either it doesn't play or it doesn't create proper ISO's for auto play. Having never used it, I can't say. If I were going to get such software, I'd get VSO's ConvertXToHD, since I've used ConvertXToDVD for years to create DVD's from video containers. I think it has a 7 day free unlimited trial. Although the output may be watermarked. Couldn't say.

Could be the fault of the ISO created by the muxer. You'd have to mount the ISO in a virtual drive and see if you can get it to play on a PC.

My only experience with DL BD media are Verbatim BD-RE DL. Some were made by Verbatim and some by TDK. When it comes to DL DVD media, Verbatim is the only one that can be trusted across the board. I know the 5 Ritek DVD+R DL I tried, only 2 were still readable after a few years. The other 3 weren't even recognized as discs. I only use Verbatim media where possible, except for DVD Video, where I use Ritek's 8x DVD+RW because Ritek was the only company still making them. I wouldn't use Verbatim's BD-RE, though, as they're CMC now.

Plus, a larger image file size that approaches the maximum space of the media means you're writing more data closer to the edge of the disc. Another common place for errors to occur is when you're writing near the edge. The smaller ISO could explain why it worked.

You should generally avoid CMC as a rule. However, if you've used them fine for a long enough period of time that they haven't given you reason to question them, the drive may have reached the end of its life. Failures to Verify generally mean the burn wasn't done correctly. And that generally, but not always, means it's the fault of the drive or the media. Without using quality media, I can't say what the situation is in this case. What you could try to see if it's just a problem with the ISO is try to find a CMC disc that did burn and verify, read it to an image, and then try burning that new read to another CMC disc. If it fails again, then you know it's most likely not the ISO that's the problem in either case. It's the CMC discs or your drive has reached the end of its life.

You shouldn't be using Ritek media for dual layer discs, but since you've used them fine for months, that won't alter the situation. Generally, when drives start failing to write correctly at the layer change, it's time to replace the drive. It's reached the end of its viable life. When you get consistent failures of Verify at the layer change, the drive isn't burning the 2nd layer correctly. Generally.

On that page, people probably want to click the link underlined in blue that says here. It says that downloads the file without the download manager. The download manager is probably the wrap around software that is offering bloatware. It says Download Manager Enabled under the green and white arrow link you mentioned.

Do you have existing ISO's or discs you need to make ISO's of? If you have existing ISO's, ImgBurn won't help you in this case. Just copy them to the HDD. If you have discs you need to make ISO's of, use Read mode to create the ISO's of the discs and tell ImgBurn to store the ISO's on the portable hard drive, whatever drive letter it uses and whatever folder you want to store it in. You must have some Blu-Ray discs if the ISO's exceed 10 GB. Or you downloaded installation ISO's exceeding 10 GB for various Microsoft ISO's.

BTW, does Pioneer make an internal slim SATA BD burner? Or are they all either USB or half height internal SATA's?

I do have UAC disabled and I still can't write to that folder/get a prompt when copying and pasting files to Program Folders (x86)\ImgBurn. No, nothing gets written to the log window when attempting to save ImgBurn.ibb to C:\Program Files (x86)\ImgBurn. There's just the prompt asking me if I want to replace the existing file. Then, nothing happens after selecting to replace the file. No other prompts and nothing written to the log window.

I'm the Administrator and even I get a prompt when copying and pasting the ImgBurn.ibb file into the ImgBurn folder. Why doesn't ImgBurn return an error that it couldn't save the file if writing files isn't allowed in the Program Files (x86) directory? Shouldn't it being denied being able to write the file have returned an error prompt from ImgBurn? Or at least from Windows?

Can ImgBurn not save a new ImgBurn.ibb file in the program's installed directory because the file is loaded by ImgBurn on start up of the application? Therefore, the file is "in use?" I tried saving a new default options ImgBurn.ibb to be loaded on start of application, but ImgBurn never actually saved the file in the program's installation directory. It never displayed the dialog saying the file was successfully saved. And I checked the date/time stamp on the file and it wasn't reflecting the current date. ImgBurn would save the file to a different location, but never saved it in the installed directory. But, I'm guessing this is by design?

As long as I can find the 2209, I'll keep getting that. Only when I have to move to the Ultra HD one will I get that. I've no use for Ultra HD, either. I do, though, still plenty of DVD writing. In fact, since they no longer make and I can't find 8x DVD+RW media on the Internet, I got the last 3 cake stacks of 25 Amazon.com was offering last year. It will take some time before I deplete those. Once they're gone, I'll use the LG UHD if 6x DVD-RW can still be found. Which it can still be found laying around Amazon.com, even though they no longer make it. Otherwise, I'll have to just go to the 4x media they still make. Which they may not even make those anymore by the time I get around to exhausting my 8x and 6x options.

I figured the Ultra HD Pioneer drive would eventually become all you could get. Why should Pioneer make a drive that costs less and does less when it can charge more for something you may not use? The LG line seems poised to do likewise. The WH series now has an Ultra HD one. That's the one I got because the last WH generation had lots of problems writing BD DL media and formatted BD-RE DL that would write corrupt data to Layer 1. I needed something that still supports 6x DVD-RW for reading. The 2209 claims it does, but inserting one returns a positioning error where the drive won't even recognize it's been inserted. I told Pioneer this so maybe they'll investigate. They did fix the 8x DVD+RW Verify failure that crept in from firmware 1.33 to 1.34 in 1.50.

The BDR-209M does support DVD-RAM according to DVD Info. Never actually tried using that media in it as I only ever used DVD-RAM on my old Panasonic DVD Video recorders starting from 2002.

Now, that I did not know. Being in North America, I only ever knew of the strings 209 and 2209, and their various internal ID strings that ImgBurn displays. So, I always used 209 and 2209 to differentiate between the Pioneer BD drive that supported M-Disc and the one that didn't. I've only ever had 1 209 and I didn't like it. It didn't work with my external enclosure like the 2209 did. And it would fail to Verify DVD+RW that I'd put the exact same disc that had just failed on the 209 in the 2209, burned the same image file to the same disc in the 2209, and it would pass Verify. So, I don't recommend the 209 over the 2209. I've had like 6 2209's and only one of them was a dud that had to go back to Amazon.com. So, I've had better luck with the 2209 over the 209, so I recommend it over the other. Now, I could have gotten a bad 209, but it doesn't make me want to try another one to see when I know the 2209 has worked well for me.