LIGHTNING UK!

Well it is and it isn't. I'm just of the frame of mind that if I'm going to start messing with it then I might aswell do it properly.

Are you sure they're not 24bit wavs? I can't imagine that one 48kHz WAV would decode properly and anothers wouldn't. There must be something different about them. When you've got them loaded in GraphEdit, bring up the properties on the 'Default DirectSound Device' filter (right click -> properties) and get a screenshot of what each one says. Can you provide a sample of one of the 48kHz ones that don't work?

As it currently stands, ImgBurn's Build mode is best used with an existing folder structure. (as that's what it was designed for) The layout you're after would really come when it's had a rewrite to let you add/rename folders etc.

Think of that 'source' box as the root of the disc. If you drag 'c:\my documents\photos\' into it, you'll end up with: '\photos\' on the disc (in the root) - unless of course you enable 'preserve full pathnames' in which case you'll have '\my documents\photos\' Until you get the hang of it, you can always just make an ISO, mount it in a virtual drive program and view it via explorer. (or burn to a rewritable)

Because that's the whole idea of new versions?! They fix stuff! Your discs must have been recorded using TAO and TAO is a pain in the arse because the TOC data isn't 100% correct (you end up with 2 unreadable sectors after every track).

Windows is saying the device isn't ready. Can't you close the program down and re-open it? Maybe that'll kick it into gear.

Of course you can avoid it but why not fix whatever's causing the problem? The info is in the FAQ if you look.

No offence, but I very much doubt this is happening as you say it is. I couldn't make that happen even if I wanted to. The drive is in complete control of the burning so the software version used makes no difference. All I do is provide it with data.

GraphEdit is just an exe, it won't mess with anything. Load it up and click 'File' -> 'Render Media File'. Select your audio file and then see what happens. It'll either build the graph required to play it back or it won't and you'll get an error. You STILL haven't told me anything about the PCM/WAV file! What's the file extension? How exactly is it coming out on the disc? Is it complete garbage or is it just not 100% clear? Please remember that 'playing' a file is not the exact same thing as decoding it to a 44kHz 16bit PCM file - and that's what needs to happen when a file gets put on a CD-DA disc because that's the format of audio they use (and it's set in stone!).

ImgBurn has a fallback in the 'Create CD CUE File' window whereby any 'unknown' file that's So either select 'all files' for the file type in the browse box or drag + drop your mpa files into the window. I've added support for 'MPA' in the next version of ImgBurn so they'll show up automatically. As for the PCM/WAV thing, you'll need to provide more info as I was unable to reproduce it earlier. A good way to test things is to load the file in GraphEdit. ImgBurn basically works in the same way it does.

If you've got a problem, post the log. I've done a few DL burns today and they've all written / verified perfectly.

Sorry, I kinda meant the 'shaking window' thing rather than making it active. I remember seeing someone else with this exact same problem aaaages ago. I honestly can't remember if he ever got to the bottom of it, he probably just reinstalled the OS or something.

If your machine is basically pausing ImgBurn when it's not the active window then there's nothing ImgBurn can do about it. The process priority is already set to 'High' by default when burning. You need to look elsewhere for the root cause of the problem.

Please provide the complete log, that one is missing important information.

I need the log showing the error and also all the disc info as taken from the panel on the right when in Read mode. Make sure you're running 2.4.1.0 too please.

Sometimes you have 2 SATA controllers on a motherboard. One that's part of the main chipset and the other via a 3rd party controller. You might need to check the manual to work out which is which.

What's the PCM/WAV that won't come out properly? Is the file extension actually PCM? A file with the PCM file extension is written 'as-is' as I kinda assumed it would be 44kHz 16bit. Without the user manually entering the file format, I'm not even sure it's possible to know what the contents of a PCM file are. I just decoded a 48kHz WAV file and that worked fine for me. MPA will probably work if you actually try it - assuming DirectShow can interpret it of course.

The program is not in control at the point where it's stopping - I know this because you're unable to abort. Basically it's sent a command to the drive and it then waiting for the OS or whatever to process it. Control is only returned to the application once it's either completed successfully or errored out. You're not getting either of those things happening and that's why the whole system kinda hangs - the I/O subsystem has hung/crashed and rebooting is the only way forwards. Do you know which controller your drive is connected to? Are the drivers up-to-date for your motherboard? What about the bios? You could try following the post in the FAQ relating to resetting DMA (it involves uninstalling your controller and rebooting) - this often fixes a lot of problems.

You might want to change the 'Write Type' back to SAO/DAO in the settings too.

The cue sheet is not the problem, it's fine.

Try any of them. I don't think the files have anything to do with the issue. Use the eject button in imgburn to get the disc out. The tray is locked, that's why the button won't work. ImgBurn issues the unlock command before the eject one so it gets around that problem.

Do you have any decent CD-R discs to try it on?

It would appear the drive is giving up as it moves over to track 3. If you were to attempt to burn that same CUE again (say 5 times), does it fail each time in the exact same place? (please don't just guess if you've not tried it!) If you then try to burn another cue (on the same disc, without rebooting etc) does it work fine first time?

Do you still have the file that didn't decode properly? I wonder if I might be able to detect this issue during the analysis phase so I can inform the user and save them wasting a disc. It must be certain files encoded in a certain way with a certain (possibly buggy) program.

A write error is just a write error. So for whatever reason, the burner was unable to write to those sectors (or ones before it - due to buffering). The more you burn, the 'older' the drive gets. It could also be dust on the lense or a decrease in the quality of the discs. For the 100 odd you've burnt, maybe they were only just ok and now that things are a tiny bit worse they're failing.