LIGHTNING UK!

I'd say to flip flop between it being on / off if you're having trouble burning some discs with whatever its currently set to. There's no hard and fast rule for when it should / shouldn't be used.

It's only for CDs. I'm pretty sure you can write any sort of data (type of disc) you want when using DAO96. Note: ImgBurn doesn't support it, so there's no point in talking about it on this forum really.

If you've posted at videohelp, why are you doing a copy+paste here? Pick a forum and stick with it. TAO doesn't apply to DVD/BD, it's only for CD.

If you can take an image of a disc that doesn’t play and burn it again with ImgBurn so it then plays, it could be something like booktype/ bitsetting. Are you using dvd+r format discs?

Program Director (by unknown) or Power Director (by Cyberlink) ? If it's Power Director by CyberLink, I like to think they'd know what they're doing seeing as they make one of, if not 'the', main (licensed) DVD video player software for Windows (PowerDVD).

ImgBurn can read some images in those formats and burn them to disc, that’s all. Dmg is Mac, so you’ll need to go looking in that direction for help with the file format. Pdi and gi are both proprietary formats and you’ll probably be lucky to even find the tools that created them. I think pdi was pinnacle instantcopy and gi was something related to roxio. All of this seems like a waste of time given that burning disc is very much a thing of the past for most people. Maybe you’re looking to emulate something?

It's a 'read ahead' buffer (held in memory) of the image you're burning - be it from an actual image file (iso etc) or created on the fly when burning files/folders to disc.

It's just a descriptor in the file system. There's no 'Microsoft API' involved where ImgBurn is concerned as I'm creating the descriptor from scratch at Byte level. If programs / OSs support reading from it, it'll work as intended.

Sorry, no.

If no Flac files are opening, you probably don't have madFlac installed - even though you think you do. Are you running Windows 10 or 11? Are you logged in as a user with admin rights? Do you have UAC (User Account Control) enabled within Windows or is it set to 'Never Notify' ?

Not going to happen, sorry.

I very much doubt 'Test Mode' will work if you're trying to burn an image like this (multi-session). Can you post the log from a burn where 'Test Mode' isn't used? It would probably give a different error.

The extra capacity should be available automatically if you’re using a ‘plus’ drive.

An ISO is a box. Put an MP4 in a box and it's still an MP4 when you take it out again. Do you just want the MP4 on the disc or do you want something different?

ImgBurn tells you all of that in the box on the right when you're in Write mode.

ImgBurn tells you all of that in the box on the right when you're in Write mode.

The FAQ tells you what to do in this situation.

The album artist will have been written to the disc correctly, as that's what your cue is set to do. You could check that with ImgBurn itself in Read mode -> Click on the disc information button. Your player must not like using/displaying the album artist for the individual tracks and expects them to have their own info recorded. I'd say that's a limitation of its own CDTEXT implementation.

Your drive has an issue with the discs, it's nothing to do with ImgBurn. It's reporting a power calibration error, meaning it can't figure out a nice way to burn them. Are there any firmware updates available for the drive? Do not listen to the advice people make up and put on YouTube, a 72MB buffer does absolutely nothing.

Cdda is a pain for this type of thing. Drives have different read / write offsets for audio and so although it’s vaguely the same actual data (well, audio samples), it will be some offset by so many bytes. If you’re patching stuff, you’d be better off working with just the data track and keeping the audio tracks separate. That isn’t something ImgBurn can help you with though.

Yes, it works on Windows 11.

ImgBurn doesn't make a WEBM file. ISO is the correct format for burning to disc, just use Write mode. If your ISO contains a WEBM file, that's another story - remember an ISO is like a box that you put things in, in this case, someone may have put a WEBM file in it. So take a look around the internet for something that'll convert your WEBM file into the correct DVD Video disc format (a VIDEO_TS folder) and then burn that with ImgBurn in Build mode.

It isn’t an attitude, it’s a fact of life. The internet is full of useful things but you must be careful how you navigate it. Not clicking dodgy links or running suspect files (no matter what they might be pretending to be) is fundamental to your security online. If you object to digital digest’s practices, you really should take it up with them. They actually host this website, so it isn’t possible for me to remove the link - which I will also point out is absolutely fine when I check it. Other mirrors may also rebundle the setup I gave them, they have to pay for the servers and their time somehow. Most would / should be transparent about that fact though - maybe by calling it ‘download manager enhanced’ or something.

Microsoft changed the way USB 3 gets detected after the last release of ImgBurn came out. So it only sees a device as USB 2 on newer OS's. Yes, USB 2.0 / 3.0 makes a difference, but it's purely a cosmetic issue in ImgBurn.

Everybody needs to be responsible for their own actions. I've provided each of the mirrors with a 'clean' copy of the program. What they do with it after that down to them, and it's not my place to police it - they run their own websites and I have no say in what goes on. Most AV tools pick up on these PUA (potentially unwanted application) bundles, so I'm surprised it let you run whatever you downloaded anyway. If your setup is anything like the one in the other thread, your SO must have also agreed to the elevation prompt when launching the 'reward tool' or whatever it was called. Expecting ImgBurn and installing a 'reward tool' - red flag, red flag. I'm sorry you fell victim to this but you only have yourself to blame. Hopefully you can clean your system up easily enough.