LIGHTNING UK!

Crossflash to a GGW-H20L and then put the latest YL07 firmware on. http://club.myce.com/f142/lg-blu-ray-crossflash-ggw-h20l-gbw-h20l-be06lu10-be06lu11-260811/ http://www.firmwarehq.com/LG/GGW-H20L/files.html

I was talking about something physically stopping the tray. Like where some cases have a flap over the front that hides the drives and therefore blocks the tray from ejecting fully.

I've seen this happen when the tray is prevented from opening fully as it's cycled between write and verify. It must be some sort of firmware bug.

It's all retrieved from the optical unit... TOC info and Track info. ImgBurn just attempts to put it in plain english. I can't claim to have created the 'lead-out' cue entry myself, no. It's just an unofficial extension I saw another app (IsoBuster I think) using once upon a time.

The data on the disc is exactly what's on your hdd. So if the player has an issue with what's on the disc, either it just can't read it very well or the source files are to blame. I assume you have the latest firmware on your player? Try and play the disc in a proper 'BD capable' software player (not VLC etc). Use a trial/demo of PowerDVD 11 Ultra if you don't have one.

What disc is it? Do you have another drive you can try it in? The TOC info is pretty much just a dump of what the drive has returned.

ImgBurn is out of date. Put the new one on. Your OS's service pack is out of date - put SP3 on. Your firmware is out of date - http://www.firmwarehq.com/Pioneer/DVR-118L/files.html You're using cheapo 'CMC MAG. AM3' media. You're burning at MAX speed. Try one of the slower supported speeds... like 8x.

High errors rates on the disc are what's causing it to fail, not the programs you've got open.

You really don't need to go overboard with that stuff. If the drive is getting the data then the burn quality will not suffer - and even if it doesn't get the data the burn quality doesn't really suffer! If I shut everything down each time I did a burn, I'd spend half my life closing everything down and reopening it again!

AWS means nothing if you haven't configured the Automatic Write Speed feature. It would just burn at MAX speed - which in this case would be 8x. So yes, you have tried burning at 8x. The drive shouldn't really be failing on genuine TY discs, it could have a dirty laser.

Just Google 'merge video_ts'.

Have you tried burning at 8x?

If you're running it under Wine, make sure you've got the 'I/O Interface' option (in the Settings, I/O tab) set to ASPI. If the drive still isn't visible, it's probably the fault of Wine/OsX.

What's on the disc in question? Is it a DVD Video disc? If so, DVDShrink can be used to join them both together I believe. I'm sure you can google for info on how to do it.

You use MCSE - http://ala42.cdfreaks.com/MCSE/

The drive does it... or rather its firmware. It only supports 4x, 6x and 8x on those discs. The only way round it is to hack at the firmware binary using MCSE ( http://ala42.cdfreaks.com/MCSE/ ) and make it swap the write strategy for the Aone MID to another one that supports 2.4x. Then flash the updated binary to the drive. Of course then the 2.4x strategy you've 'borrowed' won't be tailor made for the media you're actually burning to so you might not get optimal results (compared to if LiteOn supported 2.4x officially).

You can't combine double sided discs into a single double layer sized image using ImgBurn. You'd have to copy the files from each side into 2 different folders, merge them into a 3rd folder (using whatever tools you need to depending on the type of content) and then burn the contents of that 3rd folder.

Verbatim's BD-RE DL discs are new out aren't they? You might just have to wait for a firmware update to come out that adds support for them.

Have a read of this - http://forum.imgburn.com/index.php?showtopic=18912&view=findpost&p=136270

That's probably down to the HyperTuning / SmartBurn options. There's no artificial limit imposed by the program itself.

Yes, ImgBurn only writes what you tell it. Upon issuing the 'sync cache' command to the drive, the drive is then doing whatever else it wants to do internally. Yes, if I wanted to I could make it mention the 1GB thing in the log. I prefer to go with what's being done command wise though rather than making special exceptions for certain amounts of data on certain media formats for what may or may not be certain drives. You know what's happening and why it's happening, so hopefully you'll be ok now.

It's not the program doing extra stuff, it's the drive. Ideally, the drive would return a % complete for the sync cache process - and that info is already displayed in the status bar when it's available.

You were burning at 2x, that's slow as hell. You can't write less than 1GB to a DVD-RW disc, the drive will make up whatever you don't use. Yes, the drive (not the program) just needed a little more time to finish burning that 1GB (which included your 146MB). If you'd left it a little while longer it would have done everything it was supposed to. 'Cycle Tray Before Verify' is on by default.

Nope, (and to put it bluntly) that's complete rubbish. Once the data hits the drive's buffer (which it is doing just fine), your entire system is out of the equation. (With the exception of something like a faulty psu that can't provide enough power to the drive) The drive and its firmware control every aspect of the burn and the quality of burn you'll eventually end up with. When have you EVER seen burning software say anything in the changelog about improving the write quality on such and such a disc? Exactly, never. That's something you see in firmware release notes. Doing things like enabling 'Perform OPC Before Write' will change how your drive behaves (internally) and could have a positive/negative effect on burn quality but things like buffer sizes, I/O interfaces, IDE/AHCI etc never will. *The comment about buffer size not being an issue assumes there are no problems supplying the drive with a steady stream of data - if you're abusing the hdd during the burn, the drive may have to pause now and then until there's enough data for it to start up again. That might introduce a PIE/PIF at the point of relinking but you'd never notice it. You're only burning at about 5.5MB/s at 4x so it's hardly taxing for a modern hdd. The default 40MB buffer will last about 7 seconds without ANYTHING being read from the hdd - and 7 seconds is quite a long time (to a computer) for nothing to happen.

You can already specify multiple files via CLI but 'Send To' doesn't appear to let you format the output. It just adds them in one long 'space delimited' string and puts quotes round long file names. Of course I'm not going to change the background to white. You are but 1 person! (plus I'd hate it) It uses your Windows colours. If you want white windows, make it so on your own system.