LIGHTNING UK!

Audio CDs can be played in any CD player.... MP3 discs can't. Before now, I've never heard or anyone wanting to do what you want to do and as mmalves said, you can't just insert silence between mp3 tracks. You either have to completely fudge it adding loads of appropriately named files that play digital silence (and that would be hit and miss depending on how your player plays its files - either by file name or ID3 tags etc) or you edit each mp3 file in a sound editing program and add x seconds worth of silence to the end of them. None of that is something you'd ever catch me doing in ImgBurn. Sorry.

When you're in Build mode (which you'd need to be for burning a VIDEO_TS folder), you either want to create an image file or you want to burn a disc in the drive (device). Configure the 'Output' menu option accordingly. If your burner isn't showing up in the Destination box when you've set the 'Output' to 'Device', you have a problem somewhere on your system. Perhaps you could copy + paste everything from the Log window for me please?

Sorry, could you explain why the disc needs to be multisession? The more I understand about what you're doing, the easier it is for me to help you. The file system in the last session will contain a list of all the files on the disc that you've wanted it to contain - even from the previous sessions. So you won't lose anything from any of them. The only time I could see that being a problem is if you're manually referencing specific things in the file systems of previous sessions within a program on the disc.... I don't know, as some sort of weird copy protection or something. Padus.com is basically dead, so yeah, I'd say Padus / DiscJuggler are long gone and they won't be replying to your emails any time soon (ever). In Windows Vista / 7 you can drag+drop files to a dvd/bd writer drive in Explorer and then when you browse to it and click 'Burn to disc', it'll prompt you to create a normal disc (which is left open so you can add to it later - i.e. multisession), or you can create a live disc - which the OS treats more like a giant floppy disc. You'd want the 'normal' option for normal multisession burning. XP does basically the same thing but it only supports doing it for CDs.

No, the 'Create CUE File' feature is for Audio CDs really, not MP3 data discs.

http://forum.imgburn.com/index.php?showtopic=8000

I don't know why your first machine would be getting stuck on the LeadIn like that. Although it's shown as the LeadIn in ImgBurn, the program is really just sending the drive some data to write to sectors 0 - 31, 32-63 etc. This is all perfectly normal stuff and there's no other way you can burn a disc! Do you even hear the drive making an attempt to do anything? As for the 2nd one... load the program without a disc in the drive, switch to Write mode, right click the destination drive drop down box and pick 'Family Tree'. Click ok to close the prompt and then copy + paste everything from the log window. Again, can you hear the drive trying to do anything when it gets stuck? Commands should succeed or fail. There's nothing in the program to make it get stuck like that, it sends the command and sits there waiting for a response.

Which program made your multiple session image in the first place? Obviously it wasn't ImgBurn as Read mode doesn't support doing that from anything other than CDs. Also, only 3 image formats would return that error - CCD, CDI and CUE. CCD and CUE are just for CDs, I'm not sure about CDI but it's pretty much a dead format now that Padus has vanished. I personally feel that if you're going to make a copy of a disc and that disc has multiple sessions on it (with the exception of an Enhanced CD/CD Extra disc) that it's better to do what ImgBurn suggests and make a nice clean single session image based on what's currently visible to the OS based on the file system of the last session. For that reason (and because I'm lazy), I can't see things changing. You're only using an old OS there (XP), but normally I'd just say to use the drag+drop explorer style burning built into Windows Vista/7 if you want to do multisession burning.

Load the program and copy + paste everything from the log window please. You'd best do that for both machines actually.

Maxell is just the name stamped on the disc - that doesn't mean anything. The discs you're using there are based on the 'RITEKF1' dye. Maxell have used several others over the years. Unlike discs and drives, ImgBurn doesn't get any better or worse at burning.... it's a piece of software, it can't wear out or have bad days. Discs are built to different tolerances and drives wear out/get dirty.

Just so we're clear, ImgBurn isn't the problem here. What you've got there is a disc that your drive - which is ancient btw - can't read. As for why it can't read it... well your guess is as good as mine. Is the disc dirty / scratched? Maybe it wasn't a good burn in the first place (low quality due to a bad writer or less than optimal write speed). Your old NEC burner will have seen better days - cleaning it with a cleaning disc may help though. As mmalves said, try reading the disc in your other drive or another computer - if you have access to one.

Update ImgBurn too.

This is a drive/media combo issue and nothing to do with ImgBurn. Buy some better discs, try cleaning the drive with a cleaning disc etc.

That wouldn't work, it's run during the setup initialisation - i.e. before anything GUI related happens. Not only that, that's just not how it's supposed to work / flow. I'm sure if it's blocked nicely it shouldn't take a long time to start. It certainly doesn't when there really isn't an internet connection.

Uninstall ImgBurn and then install the latest version. That won't fix your problem but you need to do it anyway. Try cleaning the drive with a cleaning disc. If it still won't burn those discs, get another spindle of them and try those instead (maybe even some 8x Verbatims - MKM-003-00). If it still won't burn, get yourself another (external - non slimline drive) drive.

The program saves the contents of the log window (and all the program settings) when it's closed. It limits the length of the single log to something like 5000 lines. If you burn loads of discs, I guess you'd soon work your way through those 5000 and it would be overwriting new stuff with even newer stuff. I don't know why it failed, your drive just errored out during the burn. It doesn't look like you've got the current version of ImgBurn installed - 2.5.7.0 so please install that. You should also update the firmware on your drive to the current version. http://www.firmwarehq.com/LG/BH10LS38/files.html

If 'File Splitting: Auto' is the last line in the log window when it's freezing, what does it say in the status bar? That'll tell us what the program actually thinks it's doing - not everything gets logged. I don't know what's happening in post #3. The program is only asking the drive to read a range of sectors and it seems to be having trouble doing that. Can you please right click the drive selection box and pick 'Family Tree'. Close the prompt and then copy + paste everything from the log window.

Here's how things work... ImgBurn submits a command to the drive. The drive reports success/failure at processing said command. -> If it reports 'success', ImgBurn submits the next command...and so on. -> If it reports 'failure', it also returns something called 'SENSE DATA' and within that sense data is the error code. ImgBurn translates the error code into something resembling plain English and displays it to the user. If there was no need to verify, ImgBurn wouldn't enable it by default. Drives don't always error out during a burn. The drive could burn really badly and produce an unreadable disc... that's what verify picks up on. By default, ImgBurn appends (well, prepends) to a single log file. So open the one you see and just find the bit you need.

I need to see the log please.

Thanks, I was aware they are/were working on a 64 bit compiler for C++ Builder, it just isn't available yet. There won't be any benefit in having a 64 bit version so although it might be 'nice', it doesn't bother me too much.

ImgBurn just burns what you give it. It doesn't / can't perform any sort of conversion on your video files.

Where's the log from that burn? If the drive doesn't error out, ImgBurn has nothing to report. Didn't you verify the disc as part of the burn? That would have picked up errors - assuming the drive had a problem with reading the disc.

I'm not so sure we do a whole lot of BD burning here.... you'd be better off asking that same question over in the Blu-ray section at the MyCE (CD Freaks) forums.

ok well you can bet it's the Viscomsoft mpeg2 decoder that's causing the problem.

ImgBurn is a burning tool, it burns what you give it. If you want a tool that'll reauthor / compress what you provide so it fits on the discs you're using, you'll need something else. e.g. DVD Shrink, CloneDVD, Nero Recode

That'll give it more room to move things around, I can't say for sure it'll always work around the problem though. Try it and see!