LIGHTNING UK!

Have you switched the output to 'Image File' rather than 'Device' ?

Your INDEX 00 markers do not leave a short time between tracks. That's the point I was making The TRACK commands give you the ability to skip (tracks). You can't do anything with indexes at all - as in, you can't jump between them. They're invisible to software / hardware players. The table of contents on the disc only records where track x / index 01 is and that's considered the start of a track if you skip through them. So really, INDEX 00 of a track actually looks like it belongs to the previous one. The PREGAP command instructs the program to insert digital silence between tracks (that data is not taken from the file).... so if you had a single large file with digital silence in it between tracks, that's where you might choose to use INDEX 00 (for when it starts) and then INDEX 01 for when the music starts again. INDEX's consume data from the file.

You can do without the INDEX 00 entries, there's no point in them being there. INDEX 01 is what players jump to when you skip tracks etc. Plus you'd only made the index 00 1 frame long... which is 1/75th of a second! Well done for figuring it all out though. No idea about the browser thing. Remove the password from your saved password list and try again.

That would have power cycled the drive I guess - something a restart doesn't do.

Why are you using such an old version? Even the latest version is old, so that's the one you should be using. It's not worth anyone's time trying to troubleshoot when you aren't up-to-date with the app in question. Once you've updated (and I suggest you reset back to the default settings), copy and paste everything from the Log window once you've opened the program and left it until it's found the drives - I'm assuming that's the bit yours is taking ages on - going by the screenshot.

Maybe you rebooted your machine? There's no reason for it to get stuck where it did.... it would have been due to something outside of ImgBurn, but a bit more info (in the form of a debug enabled log) would have helped me to help you figure out what it might be. Hopefully it stays working ok for you now.

Please post the log from you burning (with verify enabled) the discs. Either your drive(s) can't burn the discs very well or your playback device can't read them very well. Neither of those are anything to do with ImgBurn really. You could try some different discs.

This is not something ImgBurn can help you with.... but those other CUE tools you mentioned might work? You don't need to split the actual WAV file, if the CUE has tracks defined in it, they'll reference different parts of the file and your disc will come out with multiple tracks rather than just 1. CUE files are actually quite basic, you can edit them in notepad and insert tracks based on rough timings as you fast forward through the file in media player or whatever.

Next time you burn, press the F8 key before the point where it cycles the tray. That'll enable I/O debug mode (confirm it via the Log window) and more will be added to the log. Once it's stuck, save the log and upload it here on the forum please.

That's a Windows thing. Turn off Autoplay or whatever it's called.

It looks like you tried to burn too much to the disc. The program tells you that what you've chosen to burn won't fit, which must mean you acknowledged the message.

If you have an ISO from tsMuxer, use the 'Write image file to disc' option within ImgBurn - as per the guide you were linked to earlier.

Are you trying to burn an Audio CD? If so, follow that guide.

The program detects it's a BD Video based on the presence of the BDMV folder. So.... where's your BDMV folder? Ah, hang on... you mention opening ImgBurn to burn the ISO in your initial post. If you have an ISO, you should be using Write mode to burn it, not Build mode.

Just use UDF (and only UDF) as the file system.

I did a search on the forum.... turns out it's in the FAQ https://forum.imgburn.com/index.php?/topic/59-faq/&tab=comments#comment-8023

Your AV software probably removed it. See if you can get it to actual notify you of what it's doing and not just do it.

There's no way of doing it in ImgBurn though, no. Depending on how complex the CUE is and the changes you want to make, you might just be able to edit it in notepad.

How many discs have failed like this? Have you tried burning at 4x instead of 3x? (note: 2.4x isn't supported by your drive, so it used 3x instead) Assuming your discs are ok, that means your drive probably need cleaning or replacing. It shouldn't be having a problem burning (real Verbatim) MKM-003-00 discs. They're the best DL media available.

The other 6 mirrors host files without installcore... or at least were originally given a version without it. Opting to save or run makes no difference.

You can use something like this - http://implbits.com/products/hashtab/ That file isn't part of the ImgBurn download, but maybe it's something from installcore (a plugin used by the installer). It could be a false positive though.

Are you sure you downloaded the correct file? Does the MD5 of the file you downloaded match the one shown on the website?

Oops, I’ve muddled up some of my posts by saying video_ts when your topic title clearly states it’s an avchd image. So yeah, what you’re doing is burning Blu-ray style hd content onto a dvd. You should allow the program to make the changes it recommends.

Go into Build mode within ImgBurn and add H:\ to the source box.

The GUI will always show the speed you've selected, even if the drive will have ignored the request to use that speed. You've omitted the last couple of log entries where it would have showed the actual speeds your system/drive burnt at. It's not the program which forces one of the other speeds, the drive does. I cannot override the speeds it's designed to work at.