LIGHTNING UK!

If you're going to ask for help, please at least be using the correct program! Try getting some other media. A quick look over at the LiteOn forum on cdfreaks.com should show you what works and what doesn't on those drives.

It will already do this as part of the 'calculate optimal' option. To see where it thinks it will go, select tools -> iso -> display ifo layer break information.

No idea what's causing the problems you're experiencing! The only time discs don't work on players is if they don't support the media. It could also be you're using DVD+R and not bitsetting to DVDROM. Make sure you use quality media, cheapo stuff often works at the start, then gets progressively worse towards the end. Show us the log of you burning a disc and maybe we'll be able to spot potential problems.

ImgBurn can't be used for burning audio cds.

Your drive's firmware doesn't support the media you're putting into it - or at least it hasn't been able to initialise the disc on that attempt. This is a hardware/firmware/media issue.

'Verify' always comes in handy here too!

When it's ready

It's in the 'File' menu too.

Unlikey, software plays no part in the burn quality - unless it's turning on/off special drive features - which ImgBurn doesn't touch. Why don't you use the 'Graph' feature in ImgBurn to see how it thinks the burn went. It may at least show you where the drive was slowing itself down.

please copy + paste the full log.

bin files come with a cue file - because they can be complex images. You should use a CUE burning program for them really. If ImgBurn can't burn the bin directly, it wont be able to burn the ISO version of it either.

The next version already has support for burning to different drives, one after the other. As for suggestion 2... something will happen eventually but I'm not sure what.

Image content is not really relevant. The program 'should' burn anything. If it's not, you may need to update your drives firmware / buy better media.

Your drive reported a tracking servo failure... so I'm guessing that's what happened. (search for that on google if you're bored). It was just a bad disc. Chuck it in the bin and put another one in the tray. Always ensure you're running the latest firmware for your drive too.

Not really, no. That would mean dynamically resizing stuff.... very pointless in my opinion! It does no harm by being there so it's really a case of leave it be or remove it and tidy up where there will now be a few blank areas within the dialog window.

No, what I'm saying is that an ISO/IMG file is a collection of files in a ready to burn format. i.e. no processing has to be done. You read a chunk of data from the ISO/IMG file and write it to the disc. If a sector holds 2048 bytes of data, you read that from the ISO/IMG burn and burn it to sector 1 on the disc. (Discs (including hard drives) are made up of a bunch of sectors). Then you read the next 2048 bytes and burn that to sector 2. etc etc. With files, you have to first calculate where each and every file will be positioned (sector number wise), and how many sectors they will take up (this depends on the size of the file of course). You then need to build a table (i.e. FAT - File Allocation Table, NTFS - NT File System, ISO, Joliet, UDF - These are all different file systems), so programs/the operating system can perform a lookup on a certain file and know which sector it's located at. That table has to be recorded onto the disc too. Like I said, doing that is not trivial and so at the moment, ImgBurn can't do it. It relies on another program for that and then just burns that image in a simple sector by sector format. When other programs give the impression of burning 'files', they're really just creating an ISO/IMG file on-the-fly as data is always burnt in sectors, starting at 1 and ending at X.

Me too... I'm not even sure 74 mins ones still exist! In this day and age, it is quite possible I could remove it - and have thought about doing so several times. The trouble is, if I remove it, I'm bound to upset someone who DOES want/use it. I just can't win!

Well I never let anything damaging slip past.... just the odd cosmetic issue

Like I said, it's mainly for CD! If you didn't do much CD burning, it'll probably make less sense to you. Sometimes it's just easier to read 73:59:00 for an image size and know it's gonna fit on a 74 min cd rather than needing an 80min one. I don't think of CDs in terms of MB capacity, it's Time capacity for me - being old skool and all that

an img file is like an iso file... and hopefully you know the concept of an ISO?! It's a complete image of the disc. For an ISO, it's just like you read sector 1, and write it to a file. Then you read sector 2 and append it to that same ISO file. The 'file' content of the disc is of NO importance. You're talking about turning files into iso/img files and then durning burning to a cd/dvd turning them back to file...that's not how it works at all, it just looks that way. Burning a collection of files means you have to create the filesystem (i.e. FAT/FAT32/NTFS/ISO/Joliet/UDF etc) on the fly and add the files in the correct places. Seeing as you even asked this question, perhaps that is a little over your head - much in the same way that ACTUAL filesystem creation (in programming terms) is a little over mine! - well, it's non trivial at least

We're not talking about video time here, it's disc time. 25 / 30 FPS for video is obviously very different! Just want to be sure I've made myself clear so as not to confuse anyone!

It's automatic.

It actually shouldn't do that. It should say you've not yet had the correct number of successful copies and ask if you wish to retry for that remaining number. Oh... it only does it if you originally wanted more than 1 copy though. I've now tweaked it so that if there are other images in the queue after the 'failed' one (and the failed one was only queued up with 1 copy in mind), it'll prompt to repeat that image. If there aren't any other queued images, it'll just call it quits and exit how it normally would if you were just burning 1 file. At the moment you can of course select the failed/burnt images and right click + 'queue again'. I don't remember ever having a failure so that part of code never really got any testing! lol

Most programs will auto erase / format media before burning anyway - hence why adding an optional button is pretty pointless. The main reason for me to say 'No' though, is that it would mess up my GUI!

FF = Frames. It comes from the old 'CD' days when 640mb was 74 mins, 7800mb was 80 mins etc. 75 frames = 1 second. 60 seconds = 1 minute.