dbminter

What it sounds like you did was add an ISO file to a Build job and created an ISO with an ISO file in it. So, that won't play on a DVD player. I've never actually seen a DVD with any contents in AUDIO_TS before, but I've made, I think, 1 DVD Audio disc in my entire life.

You shouldn't be getting layer break settings set at all if it really does fit on a DVD-5. About the only thing I can think of that might fix this is to create a new ISO that is a DVD-9. Add some extra files to pad out the size of the ISO so it will need a DVD-9. If that doesn't fix the problem, I don't know what is causing it. You're just importing a VIDEO_TS folder into a Build job and creating an ISO and that's the ISO you're trying to burn, right? Did you create the ISO first or are you using on the fly disc creation?

So, TMpegEnc was making the ISO itself? And you were using ImgBurn to burn the ISO? Instead of using Build mode to import a BDMV or whatever it's called folder? Then, if that's the case, TMpegEnc wasn't making correct ISO settings for BD Video.

Are you manually setting layer break position settings? If it will fit on a DVD-5, there is no need for a layer break as far as I know.

Having never even heard of VidCoder until this thread started, I couldn't say. I'm not familiar with how that behaves as I've never used it.

I generally don't say things unless I'm relatively sure of them. Just having some fun with ya!

Well, what do you know! There's a new beta for ConvertXToDVD! https://www.softexia.com/windows/multimedia/blu-ray-dvd-tools/convertxtodvd And ConvertXToVideo, too! https://www.softexia.com/windows/multimedia/video-editing/convertxtovideo Although the vast majority of updates only seem to be to the update engine itself! However, there was an update to address VC-1 compatibility problems, apparently, But, according to their forum, there appears to be a 7.0.0.66 for ConvertXToDVD that is coming soon that will "integrate some fixes about subtitles."

Such issues are rarely hardware related. Generally swapping in all new hardware won't fix such a problem. The problem is most likely software based. The software that made your content probably isn't making it right.

Just as I thought. It's most likely junk media. Here's your problem: I 14:25:38 Destination Media Type: BD-R (Disc ID: CMCMAG-BA5-000) You may be using Verbatim BD-R but this is the 2nd time I've seen foreign, e.g. outside of the US, Verbatim BD-R that is so called DataLife Plus that is not DataLife Plus but CMC garbage. In the US, there is no such thing as DataLife Plus Verbatim BD-R. It's all just BD-R and none of it is CMC. It appears outside of the US, Verbatim is trying to screw over their customers. The only solution is try something else, like Panasonic BD-R, if they make it. TDK may make BD-R and if they do it may be good, but TDK does make BD-RE that is CMC junk. You could always try importing Verbatim BD-R from the US. The other person I saw with this problem on the board imported the good stuff from the US to solve their problem. Oh, IC what you're saying about the data Blu-Ray. It's not a Blu-Ray Video you're playing. You're playing the folder contents via your player's browser. This won't present you with a menu like a Blu-Ray Video disc will. It seems this TMpegEnc software is not generating compliant BD Video content. This is inferring that TMpegEnc even creates a menu for its BD Video content. It may just start playing with the first chapter. I don't create BD Video so I can't say what to do at this point. Of course, why it doesn't start playing when you have the disc inserted as a BD Video, I couldn't say.

Well, it depends on how the DVD is authored. What is generally done is each movie is its own Video Title Set. However, sometimes, both movies on a 2/etc. movie disc may be combined in one giant VTS. Either way, I'd use DVDShrink in conjunction with Handbrake. I'd use DVDShrink's Re-author mode and isolate which of the 2 movies, if they're separate VTS's, to write a copy of the movie to VIDEO_TS instead of ISO. Then, I'd use Handbrake to input that VIDEO_TS. Or Handbrake can read an entire ripped DVD's VIDEO_TS and it adds all VTS's to its Queue for processing. You can use the Preview mode to find which of the large streams is the movie you want and process only that to MKV. Or just process the entire DVD to MKV's and load the MKV's in some kind of media player to see which MKV is the movie you wanted. This will take longer to do, though. If both movies are one giant VTS, you'd need DVDShrink to load the giant VTS and use its edit/trim function to trim out all the Chapters before/after the content you want to keep and write that new Re-authored content to VIDEO_TS. I would actually do this a different way, myself, with a piece of software called DVDReMake, but it's not freeware. But, I approached your question from a freeware point of view.

Also, when you say you change to a data Blu-Ray, it works. What exactly do you mean? BD Video discs are data discs and don't generally require changes to format types from the default to be playable.

Post the log of the failed burn. Open Help and choose ImgBurn Log. Open the log, find the failed burn, and copy and paste the entire write and if it made that far verify phases of the failed burn.

This is a weird case. Normally, it would simply be a thumbnail database. This file was in the root directory of a DVD Video disc that contained 2 JPG's for some reason. Also a weird FTP.LOG file. The .DB is most likely not needed.

Was adding some files and folders to a Build job and when I exited the input mode, I noticed this in the log window: W 19:23:41 Removed Filtered File: \Thumbs.db What exactly is a filtered a file, why was it removed, and who exactly decides what files should be filtered? Thanks!

Oh, I think I see what you're saying. You think that ImgBurn is maybe spinning the disc faster than CopyToDVD when it burns to disc? That may actually be the case. You seem to think that CopyToDVD is not writing discs at the maximum possible write rate like ImgBurn is? CopyToDVD may actually be writing at a slower rate, which may be noticeable in how fast it's spinning.

I don't understand what you mean. The disc has to spin in order for it be burned.

Yeah, those are the communication layers I mentioned in one of my updates to my previous reply.

I forget where it is, but there was a setting I always changed when installing and setting up a new PC that disabled Windows complaining you're not using your Microsoft account. But, I forget what it was I disabled and where. Wait, you're not getting this are you? https://superuser.com/questions/1123583/you-need-to-fix-your-microsoft-account-notification As for your ImgBurn settings question, I currently have an operation going so I can't check right now. When it's done, I'll update this reply to reflect what those settings are. It sounds like, from memory, the Elby software setting has to do with how ImgBurn detects what optical devices are connected to your system. Generally, you don't choose the Elby I/O option unless you have problems with the default setting with ImgBurn and your drives. Exactly where you looking at these settings? Help me help you. Under what tab, etc. Okay, I'm into the ImgBurn settings. I guess you mean under the I/O tab, Page 1, Interface tab. Anyway, if that's what you mean, yeah, that's what I thought it was. That's how ImgBurn communicates with your devices. Some people need different translation layers with their hardware to get ImgBurn to recognize their devices. Or, if they're not behaving right, maybe changing the layer fixes things on some people's setups. If you're not having any problems with ImgBurn communicating with your optical drives, leave its setting alone.

Most likely, those engines are flagging the OpenCandy plugin as malware. It's a PUP, Potentially Unwanted Program, but not malware. There is a difference that most AV vendors don't differentiate. Plus, OpenCandy is no more. The server's dead. The mirrors may be a different story as there's no control over what they do with the installer once they get it. Which is why you should always download from Mirror 7, the ImgBurn Provided link, and not the other mirrors.

Yes, in my experience, power calibration errors are rarely the result of actual power supply issues. Don't know why they call them that, then. However, I would make sure the drive is connected to an external enclosure with a proper external power supply to it. That may also fix your Eject issue. My experience has been low quality discs are generally the cause of power calibration errors. Post a log from a failed burn. Under Help, choose ImgBurn Logs to find the log file, open it, find a failed burn with a power calibration error in it, and post the entire burn and, if applicable, verification log of that operation. That would tell us more.

Sorry, I failed to reply to this earlier. If you're looking for CD-R's, those are good ones to get. I purchased some of those exact same ones October 17th, 2017. I don't go through a lot of branded CD-R, preferring inkjet label discs, so I still have them. If I remember correctly, the Manufacturer ID for those CD-R is Mitsubishi. That's the M in MCC and MKM, the quality DataLife Plus DVD discs. Mitsubishi makes the best stuff out there now.

Yes, unfortunately, there are a few CMC's out there, which leads to some confusion. What leads to more confusion is CMC is crap media; MCC is quality Verbatim DVD-R/DVD+R!

That's the nature of cheaply made media. Sometimes within the same package of discs, you'll get discs that pass write and verify and some that won't. And even those that do complete the burn and verify process, there's no guarantee they'll be playable in a certain device. And even if they are, because they're cheap media, they will probably be unreadable within a year or 2. And they definitely won't last as long as quality media. I once had a cake stack of 200 CMC's. They were Optodisc which used to make their own quality media, but switched to crap CMC. Out of those 200, about 100 failed to write. Which meant about 50% of them completed writing. Once I learned of CMC after this incident, I recopied those discs to better quality Verbatim discs just to be sure. I then went over my collection of already burned discs to make sure I didn't have any CMC's. CMC is crap because they're cheaply made. They use cheap dye in their discs, which leads to all kinds of incompatibility problems. Sure, they're cheaper to buy, but they're cheaper in quality as a result. There's an old Spanish saying that translates as "The cheap comes out expensive."

I disabled my Microsoft account and just use a local account. I don't want Microsoft with access to any of my stuff. We all know what they'll do with/to it. Plus, the so called benefits won't last. For instance, cloud storage of your Windows settings. Microsoft will just change the locations of those settings at some point in the future, requiring you to re-enter those configurations again at some later date. Plus, if you store everything in the cloud, what happens when that server is down?

Yeah, the refurbished drive is fine thus far. I wouldn't be worried about it for another month, though, as the one it replaced lasted about 2 months before it needed replacing. As for new media notification, I mean storage media. On 1903's initial release, whenever you inserted a flash drive or attached a new external USB HDD, the new Notification box would stay lit up until you manually clicked on it to open the Notifications list. This was the new behavior for all Notifications. Now, after the last KB update, it doesn't do this for new media detection but STILL does it for all other Notifications! In fact, this was the default behavior YEARS ago until Microsoft wised up and changed this behavior... then the dumbasses put it back in! I left the Notifications alone and they still were highlighted in the lower right hand corner to let me know I had Notifications. You will definitely know if you're on 1903. There's a new light theme that will change your Desktop to the new lighter blue Windows logo theme. Plus, simply Run/search for something called WINVER. It will tell you your current version of Windows. If you're running 1903, it will say Version 1903 near the top.