LIGHTNING UK!

The name passed via CLI is used once and then thrown away. So... the only way I can see this happening is if the drive isn't ready or gets refreshed, thereby making the program generate a new name. What's controlling your Nimbie (loading discs etc) ?

The size of the spare area gets set when you issue the format command... and the available sizes come from what's reported in the 'Format Capacities' section of the disc info. So basically, you query the drive to get a list of sizes and then pick from the list. Looking at the info posted above, you've got 3 options. So your disc is left with 46781440, 47305728 or 48854016 usable sectors. The size of the spare area of course decreases as usable sectors increases. Your disc is currently formatted with the middle one and would be considered the 'normal' one to go for if you want spare areas. You can expand the spare area region(s), but that's not something ImgBurn allows for. The ISA / OSA values in the 'Disc Definition Structure' are to do with spare areas. They correspond to the number of clusters that have been allocated for spare areas in those regions. 8192 clusters = 8192 * 32 sectors = 8192 * 32 * 2048 = 536,870,912 bytes = 512 MiB Spare areas are per layer. There's an inner area and an outer area, per layer. (Hence ISA and OSA. The user data sectors are in the middle) I expect there would also be a value available for ISA2, ISA3 etc on your TL/QL discs, but again, that's not covered by the specs I have. I cannot tell you how much of each has been used, there's only a flag set when it's full. This is already displayed. Yes, ODD software works at quite a high level really. Larger disc sizes etc shouldn't cause much of an issue, if any issue at all. It's only a problem when the format of a certain structure changes that you'll come unstuck. Luckily, that would mainly cause cosmetic issues. You issue a 'READ CAPACITY' command to the drive and it returns the size. It's as simple as that.

I assume you're talking about the PAA numbers? They're a straight dump of what's recorded in those bytes within the DI Unit. The 'Layer Information' is calculated from those values, but because they don't remotely match up with what's recorded for SL/DL media (and I only have the specs for those), it's garbage. There will be no fix for that until I can find out the specs of the DI Unit used on the TL/QL BD-XL media. I've been unable to get anything back from a Google search. Don't worry though, they aren't something the software has to use. Yes, clustor(s) should of course be cluster(s). I've corrected the 2 instances where it was spelt incorrectly.

1. Quick certification. You disabled (made it skip) full certification, so as per a previous reply, it’s requesting quick cert before falling back to no cert. 2. That looks like a bug to me. TL media barely existed back in 2013, and I’m pretty sure I’ve never looked at BDRE TL media at all. 3. Burst Cutting Area Physical ADIP Address

Minimised to the bottom left corner of the screen? Failing that, open regedit, navigate to HKEY_CURRENT_USER\Software\ImgBurn and delete the 4 entries starting with 'LogWindow'.

It looks like that drive is in an Asus laptop rather than a Sony one. Note the 'ASxx' firmware rather than 'SNxx'.

That's down to the authoring program rather than the burning program.

That wasn't quite what I meant. I believe ImgBurn will read a multisession CCD just fine... but all of the data is in a single IMG file. To build a complex CCD based on a single IMG file, you would have to figure out the exact offset of individual tracks / session etc in the IMG file and somehow input that in a GUI. That would just never happen. For building a complex CUE, you simply drag the file for each track over and add new sessions when you want to.

They aren't flexible like CUE files, so there's no point. All you can do is have it point at a single img file. CUE can specify multiple files of different types and build up a disc of multiple sessions / tracks.

If the drive supports formatting with certification, I'd expect this bit to read differently once a full format (with certification) has been completed... ^ Is as it reads after a full erase (format) in a Pioneer 209. The 'Prefer Format With Full Certification' option within ImgBurn only causes it to ask the drive to do a full format with full certification. If that fails, it asks it to do a full format with quick certification. If that fails, it asks it to do a full format with no certification. So if that option isn't checked, it skips the full cert request and goes straight for the quick cert one. Hardware defect management is activated when a disc has been formatted with spare areas. Nothing else should influence that (in terms of formatting options) and it's handled entirely by the drive. It's possible to bypass defect management and the automatic write-verification that goes with it by setting the appropriate flag in every 'Write' command sent to the drive. For BD-R, that's the 'BD-R Verify Not Required' option and for BD-RE it's the 'BD-RE FastWrite' option. Generally speaking, it would be pointless to format with spare areas enabled and have either of those option enabled. So assuming you've formatted with spare areas enabled and aren't trying to bypass the auto write-verification, the drive should remap bad blocks as it attempts to write to them. I doubt anything happens when you're just reading the disc and come across something unreadable. The whole reason for ImgBurn performing the 'zeroing sectors' stage as part of a full format is that the format process itself doesn't appear to do it. So you can issue a 'full format with full cert' command to the drive and it'll finish after x hours with disc still containing data. Now... don't quote me on that as it could be that when I noticed that happening (it not zeroing the sectors), I was full formatting in a Pioneer and so the full cert part wasn't happening anyway. Maybe I'll test it out again and compare the results of LG drives against Pioneer ones.

Sorry, no. The drive formats as a whole. As you’ve got pioneer drives, I should mention those 2 errors you get are basically because it doesn’t support certification as part of the format process. The only verification you’ll get will be from where the program takes over and zero fills each sector. If you’ve formatted with spare areas, the drive will be performing automatic write verification (and mapping out defective blocks) as it does that. If you haven’t, it won’t be. The best you can hope for there (in terms of detecting problem areas) is the drive returning a Write error. You don’t need to erase a bdre disc you’ve written to, just write straight over the top of it. Quick erase just attempts to zero fill a chuck at the start of the disc. You can instead save yourself a write cycle and just write meaningful data to it.

No, ImgBurn only supports the normal SAO/DAO and TAO modes for CD.

Hmm actually, mine just worked fine without needing to configure anything. I only have Ubuntu 12.10 running inside vmware on a Windows PC though. I was using Wine 1.6.1

Wine will need to be advertising the drive properly so the program can pick it up. Have you configured wine?

1. The guide is probably just talking about for DVD media. For BD Media, you'd want to be looking at the bit of info looking like this... This disc hasn't been fully formatted / certified. 2. Yes, the disc info always shows 1 session / track taking up the entire disc. There's no way of finding out how much of the disc has been used up by real data, beyond relying on what the file system says. 3. As you've said, spare areas are disabled by default. This is so the full size of the disc is available for user data and it burns at the speed it's meant to. If you've got a disc that's failed to format/zero correctly on its first use, that's not a great sign. You could try it again and see if the drive fixes things. If you need to work around some problem sectors (and this is all done by the drive itself rather than software), you'll have to format with spare areas enabled and hope there aren't more bad bits than the drive's internal format and certification process can cope with. If you favour defect management capability over usable disc space, make sure you format with spare areas enabled.

BDRE aren’t supposed to look empty, that’s not how that format/type of disc works. They should have a single session/ track spanning the entire disc. Db was right, ImgBurn does it properly and leaves the disc in the correct ‘formatted’ state. You can turn off the option to have properly formatted discs in the settings on the Write tab, but you’re better off just doing it properly that one time and then not using software that’s going to mess it up.

As it's only supposed to support BD-RE TL at 2x and yours is still claiming 6x for the supported write speeds, I'd have to say it has no firmware support for the 'SONY-ET2-002' MID.

If your laptop can’t burn the discs you’re trying to use, stick to burning them in your desktop pc or buy some different discs.

ImgBurn is for optical discs, not usb sticks.

Select Advanced input when in Build mode. (menu at the top)

My advice? I didn't say anything about discs Your source CD looks to have been an audio disc and that'll only work on a CD.

They look fine. Now just load the .CUE one in Write mode.

Yes, in Read mode.

Your drive isn't going to know or care about about any encryption that hasn't been removed. Data is data. If your initial issue is what's always been happening (stuck reserving the track), not even data (content) comes into it... just the size of it all (in sectors).

Your drive reported a 'Write Error', so it had some issue writing to the disc. Perhaps try at one of the other write speed it claims to support those discs at?