LIGHTNING UK!

Well you will keep trying to go at a tangent to the program!

Yeah that's actually the one I was referring to (without naming names).

Yes we know what the layerbreak is in physical terms, however for DVD Video there are lots of other things to consider. You can only really say either way if you've actually read the DVD Video specs - and unless you work for an authoring company that's paid for them, I doubt you have!

Bitsetting is performed automatically by almost all burners now. It's not something you have to 'do/change' for every burn. It's a set once and forget about it type setting (on all but LG drives I believe - more fool them!). ImgBurn supports changing the booktype setting on most of the major manufacturers, just click the little 'Book' picture down the bottom right when in one of the write mode. (on the 'Device' tab in Build mode).

Ah maybe that's it then. I figured it would be 2 years everwhere.

Doesn't that just run it into UltraISO / PowerISO? That's not a direction I see ImgBurn heading. If you want to add files, mount the existing ISO in DAEMON Tools and point Build mode at the virtual drive. Then add your new stuff and make a new image. When complete, delete old image.

Does anyone really know for sure that the mux rate is important?! It strikes me that programs have been setting layer breaks without any regard for mux rate for ages and it's never really been an issue!

I could have sworn Plextor drives came with 2 years warranty

If you're burning non DVD Video data too, there is an option for where you want the DVD Video data to be positioned. Either at the start, mixed in or at the end. It defaults to mixed in. So although your VIDEO_TS folder might be quite small (and fit on 1 layer), some of the other stuff is probably pushing it over the edge. When it does / can fit on 1 layer, ImgBurn IS clever enough to know that it doesn't need splitting across the layer break. So perhaps you just need to play around with the 'Folder Content Location' option on the 'Build' tab in the settings.

Pretty much the first thing I do in code is put up the splash screen. If it's not even getting that far, it's out of my hands, sorry. Try loading it in safemode and see if it still gets stuck.

You're lucky it plays at all really - VCD's are multitrack and ImgBurn doesn't do multitrack burning. If it stops earlier than it should do, maybe the drive just can't read that bit on the disc and so gives up. Your guess is as good as ours.

No offence but that really is the users problem if they buy media the drive doesn't support. I'm not even sure it's possible to know if the media is high speed and the drive doesn't support it.

I just meant that for all the writer cares, you could have burnt 4 million 'zero filled' sectors. What's being burn is neither here nor there. The drive just can't read the sector back. It's not that the data on the disc doesn't match that of the image file, it's that the data on the disc is 110% useless because the drive cannot read it, full stop. Just RMA the drive and save yourself from wasting more time and money trying to fix things and diagnose problems.

Really Blu?! I've got quite a few that come up as PTP in the disc info. *Finding* the layerbreak is not really the issue here. I assume Bloodyroar would be loading from an MDS so the original LB would be preserved. The reason it's not being, and hence why ImgBurn is searching full stop, is that the LB in the MDS is not usable on OTP media. What comes after that is almost to be expected - i.e. where no cells just happen to be aligned on an ECC boundary and still let L0 >= L1.

You're getting proper read errors back from the drive. This is not an issue with WHAT has been burnt, just that something has been burnt at all! If the burner burns ok (no errors) and then can't read back what it just wrote, it's clear the burn was no good. I would almost expect that on cheapo ritek / cmc DL media but not on Verbatim ones. So if it really is still giving you read errors when you've burn to decent Verbatim discs, I would say your drive is on its way out. When mine died it would cycle the tray after the burn (and before the verify) but get stuck and just return the 'Unable to recover TOC' error. So it has just that second finished burning and then it couldn't even initialise the disc to gather info about it etc - and that process is TOTALLY internal to the drive. I filled out an RMA on the plextor site and 4 days later I had a new drive.

That doesn't really mean anything bloodyroar. Every disc is different, this one just happens to have L0 That is not permitted on OTP discs so therefore this one must have come from PTP.

In build mode, yes. You just add it as you would do any other folder. Or better still, add the parent folder - the one that contains the AUDIO_TS / JACKET_P / VIDEO_TS folders.

As Blu said, you want to burn them at 2.4x, not 4x. When you burn the verbatims, set it to 2.4x too. If you really do get write errors on both sets of media, the media has got to be duff or the drive is. My Plextor 716 lasted a year before it died, just RMA it, it's easy/quick/free!

The image probably came from a PTP disc. You won't be able to burn it with a proper layerbreak unless you extract the contents and make a new image.

Ah yes, I see the problem. Once it has done the erase it reinitialises the disc. It doesn't reset one of the flags until after that has finished. That flag is the one that stops it saying erase is still in progress. I've guess I've never just loaded ImgBurn to erase something and then closed it straight afterwards... if I had, I would have found this too. Thanks for reporting it.

They can but normally DVD Video files live in a VIDEO_TS folder, that's just the way it works. When you burn them to DVD they'll go into a VIDEO_TS folder - it makes sense to arrange them in the same way on your hdd - get into good habits and all that

Yes drives do monitor the burn, it's generally known as WOPC (A.K.A. SolidBurn, amongst other things). If you find the drive is slowing down as it perhaps attempts to speed up, it's probably because it's done the little burn quality test and thought "OMG, this burn is awful, I'd better slow myself down!".

You don't need to close the program to get the log, just copy + paste the info from the log window itself. If you close the log window normally, just enable it again via the 'View' menu.

Yeah but why would you want to use the old free version when the new version is so much better? (and fixes lots of problems etc) Although VSO are in the business to make money, the didn't actually mind doing DivXtoDVD for free. I think they were kinda made to charge for it because of the code it uses internally (patented stuff).

Other than RITEKF1 discs being useless, the issue you're having does not sound like it's at all related to the actual burning stage. Split pictures etc sounds like it can't decode the video properly and of course that can only be attributed to the program that created it in the first place. PC software players are MUCH more forgiving of that kinda thing - they can just release fixes / workarounds for encoder problems. Standalones can't do that - unless you manage to find a firmware update for your player of course.