LIGHTNING UK!

As you would have been told back in February (if you'd ever actually made it back to the forum) when you made THIS post, please post a copy of your log file.

No it's not possible and I very much doubt it will ever be.

'Too fast' doesn't come into it. DS tells me when it's done, that's how I know I have to insert digital silence to pad the track if there isn't as much decoded data as originally estimated. The only way you're going to get anywhere with this now is to go to the madflac bloke or whoever and ask why the DS filter comes up short (or doesn't work at all). As mentioned previously, if you want a seamless disc you need to use a single large file. Even ImgBurn could be semi useful for that, it'll read an Audio CD to a WAV file, then just compress it using a Flac GUI type thing. Change the .cue file so it points to the .flac file (and not .wav) and then burn away!

Playback time is shown in the 'Time' column within the 'Create CD CUE File' window. If the CUE file comes from elsewhere, press the 'Image Information' button once you've loaded it in to Write mode. (That's the button with the picture of a disc and a question mark on it)

It may happen one day. Never say never! (although I often do ) Personally though, I'm really not fussed about it - and I tend to implement things that I want to add.

Sorry, that's beyond the scope of a burning program.

Try 8x and 12x too.

From my point of view, it's 1 command that gets/doesn't get (depending on the value of the 'Perform OPC Before Write' option in the settings) sent to the drive, that's it. The drive deals with it in the way it see's fit. As Google would probably tell you, OPC is where the drive uses a special area on the disc to try and figure out the optimum power level/setting for the laser when burning onto the media. When it's off, the burn sequence is identical to 2.3.2.0 and all the other versions before it. If you'd like to see what the command is, read the MMC6 manual available (free) from www.t10.org and look at the 'SEND OPC INFORMATION' command.

Have you tried slowing it down a bit? It just looks like the drive can't handle 16x on those discs very well. They're not my first choice for media either... or my 2nd, 3rd, 4th, 5th... you get the idea

Just look in the 'Source' box. Only stuff in there (and folders below other folders if 'Resurse Subdirectories' is enabled) will be added to your disc.

Yes it's the DirectShow filter (or at least I think it is!) The playback time of the file is found via: IMediaSeeking->GetDuration(&Duration) That's then converted into 'frames' (which are equal to 1/75th of a second). 1 Frame = 1 Sector. So once I've got that info I know how many sectors to reserve for the track in the cue sheet. If the DirectShow filter doing the decoding say's it's finished processing the file and I've not reached the number of sectors I'd reserved, I have to pad it with zeroes until I have. A zeroed sector or two at the end of the track wouldn't be noticable on normal discs but of course would be on a mixed cd. For that reason, those kinds of discs must use a single large file.

Oh and btw, SAO is Session At Once. SAO and DAO are basically the same thing. It's called SAO on CD and DAO on DVD/HD DVD/Blu-ray. Basically the write types available (as per the MMC specs) are Incremental, TAO, SAO, RAW, Layer Jump. In 2.4.0.0 I only really support Incremental and SAO (which doubles up as DAO). TAO is also then supported (properly - i.e. as a real option) in 2.4.1.0. It's in 2.4.0.0 but only as a fallback if SAO isn't available and it's implementation is pretty poor (hence the proper update in 2.4.1.0). I guess I could actually write SAO/DAO in the 'Write Type' dropdown box to avoid the confusion. On DVD/HD DVD/Blu-ray the only supported write types are Incremental, SAO/DAO (and 'Layer Jump' but that only applies to DVD-R DL and isn't supported by ImgBurn because it's a waste of time). If you select anything that's not supported it'll just default to SAO/DAO. I've never got Incremental working on CD so that just defaults to SAO/DAO regardless.

It could be drive specific donta, can't rule it out until I come across someone with the extact same drive where it works fine. Better to be safe than sorry

Yes you'll have to manually click start. There is no 'disc to disc' option in ImgBurn. If you want, write a simple batch file to make the program read the disc to an image and then write it. i.e. ImgBurn.exe /MODE READ /SRC D: /DEST "C:\Image.iso" /START /CLOSE ImgBurn.exe /MODE WRITE /SRC "C:\Image.iso" /DEST E: /START /CLOSE Job done

The only way to get it 100% gapless (unless working with a file that doesn't need decoding - i.e. wav/pcm) is to save as 1 big file. The others are subject to gaps if the decoded data doesn't match what the codec returns for a 'size' (playback time) of the file.

It's been totally removed from both. The only way to mess with the option now is to do it via the 'Advanced Settings' window.

I run 1920x1200 and I wouldn't call it 'tiny' at all. ImgBurn has loads of CLI options, just look in the readme.txt file.

It doesn't hurt the burners or mine would be dead long ago!

AFAIK, the BD format did away with the whole idea of 'layers'. You just use it as one huge disc. As such, there are no commands available to get the layer sizes etc.

It uses whatever directshow is setup to use. It's all automatic. You can change the 'merit' of your directshow filters if you prefer a certain one over others... of course it's all file type dependant too, not a 'one for all'. http://www.google.co.uk/search?hl=en&q...nager&meta= It doesn't write any temp files during decoding, it's all done on the fly. My own. Which box? The 'Source' box in build mode? Double click it or click the green arrow.

Have you really tried burning with other programs since you started getting this error? It's not the software that makes them up, the drive itself errors out and ImgBurn simply relays the error message to you. I cannot force your drive to NOT error out, it's impossible. Seriously, if the other programs will still burn that exact same media then I'm at a loss. All it could be is the Incremental / DAO 'Write Type' option in the settings - but that shouldn't be a make or break choice, they should both work.

ebay... that's where mine came from

Ah finally we get a decent log where the OPC command isn't sent and you don't get a 'command sequence error' error from the drive. It doesn't matter which way you look at it, your drive has issues. I tested a few TYG03's in my 716 yesterday and they all burnt fine (with 'Perform OPC' enabled and disabled) - might I add that this is my 2nd 716, the first broke and wouldn't burn anything. It looks like yours might have gone south too.

They're totally different versions so it's impossible to come to any conclusion just yet.

No, don't do that. Just update to the latest versions of both tools.