LIGHTNING UK!

I just downloaded + tried v3.60 and it all seemed ok to me. I'm running it on XP SP2. When I switch to a different desktop the program + taskbar button vanishes (as one would expect). When I switch back the button re-appears and the window (windows actually if you include the log one) are back on the screen.

The data you're burning is of no consequence here. The drive just sees it as generic data, it doesn't know (or care) what it is. Try cleaning your drive with one of those cleaning discs and maybe some compressed air (in a can). Other than that, if it happens all the time I'd have to say your drive is faulty. Try getting it replaced.

Damn it, a simple '!=' that should have been '=='. Fixed now.

ah shit, forget that, I can reproduce it already. One of my changes must have killed something. I'm fixing it now....

You're going to have to explain in detail the exact settings you're using and the folder you're adding (or files) in the 'source' box. I then need to know the actual structure of the folder on your hdd and what files are in it. Only then can I reproduce it and fix whatever weird issue it is that you're finding. Thanks

No problem, I'll get right on it.

At least you have it now and that's all that matters.

You're always better off using the original program for that kind of thing. Without having the file format specs, it's always a guessing game as to how these things work. Only PowerISO would really know if the image COULD be converted to a simple ISO file. Is there no other way of doing what you do without having to resort to using DAA files in the first place?!

Yeah just get away from thinking of disc in terms of MB. It's all about sectors and so the actual MB capacity depends on the sector size you use. 2048 being the smallest, only gives you (for example) 650mb or 700mb. If you up it to 2352 you get much more data on the same disc. That's how CDDA is burnt and so that's why audio images can be larger than the 650mb / 700mb limits you're expecting. DVDs don't really have a leadin in the same way CD's do. For a CD burn you actually start burning (all be it mainly a bunch of zeros) at LBA -150. For DVD you always start at LBA 0. That's not to say the drive doesn't automatically do the leadin part.... but then to me (as the software programmer), I don't really need to know exactly what the drive does for a leadin, I just need to know I start burning at LBA 0.

I assume you've checked you're on the latest firmware for your LiteOn burner? Verbatims are the best DL disc by far. If you're already using those, you (or I) can do nothing more. You might have a duff bunch of discs or your drive might be duff (such that it just can't burn any DL media).

Sorry, there will never be a linux version. You can get it running using WINE though I believe. Someone was talking about it in the 'Chat' forum a few weeks back.

Whilst I 'could' just terminate the AnyDVD process, I don't really like the idea of ANY app doing that kind of thing, least of all my own. As it only really matters anyway if you Verify something that AnyDVD decides it wants to adjust, it's not a huge deal. So long as you kinda expect 'miscompare errors' on certain DVD Video burns / verifies, that's probably enough.

This has already been suggested. As I said in previous threads, due to the number of options that can apply to a 'build', it's unlikely to ever happen. If you must perform multiple builds, write a batch file or something.

All CDDA is 2352 bytes per sector. Maybe I just don't get where you're going with all this! The 1 CD = 700mb (of data) = 80mins (of audio) is based on 2048 bytes per sector for the 'data' side. If you're talking image sizes for 80 mins of audio data, it would be something like a 750mb file.

Unless you have a rogue filter driver in your system somewhere, your drive just isn't seeing the discs (any more) in the way you need it to in order to burn them. It's not seeing that there's any free space on them and it thinks the track/session is 'complete' rather than 'empty'. afaik, ripit4me is just an exe. It would take a proper driver to mess anything like this up.

Going by this... PLEXTOR DVDR PX-760A 1.04 (ATA) Current Profile: CD-R Disc Information: Status: Empty Erasable: No Free Sectors: 359,847 Free Space: 736,966,656 bytes Free Time: 79:59:72 (MM:SS:FF) 359,847 Sectors = 359,847 Frames (FF). + 150 FF for 2 second leadin = 359,997 Frames 359,997 % 75 = 72 (FF) (359,997 - 72) / 75 = 4799 Seconds 4,799 % 60 = 59 (SS) (4,799 - 59) / 60 = 79 (MM) Giving us 79:59:72 and 359,847 sectors * 2048 bytes per sector = 736,966,656 bytes = 719,694 KB = 702.826171875 MB The size is calculated using 2048 byte sectors, not 2352.

These look the same to me. Going by what's being returned by the drive, the discs aren't empty. Do you have anything other than those Verbatim DVD-R discs?

If it's some type of compressed image, the answer is 'no' i'm afraid.

Yeah 75 sounds about right. You have to add 2 seconds to the total MSF time though because 1 frame = 1 sectors and the cd leadin is 150 seconds. So LBA 0 = 00:02:00.

It's no bother for me, just for other people who get confused with multiple versions of the same version of a program! (Quite understandable I guess). I'll see if I can't sneak something out though. I assume you're ok to just turn off the auto save for now yeah?

Well I kinda wanted to get away from having 3 versions of the same version (which is what happened with 2.0.0.0 !) If I was going to do it, I'd at least wait a day or two to see what other little bits I'd missed. /LOG CLI switch is not core functionality and is only used by a small percentage of users. It is a GUI app after all!

C++ Builder, BDS2006.

only 1 but it's a 24" widescreen.

ImgBurn just burns image / files so if any conversion is involved, the answer is 'no'. I have no idea what a canon compact video is, so maybe Google would be your best bet for finding out more info.

Ok thanks, I've changed the priority when saving the log so the CLI stuff takes preference (as it should do). It would have always worked like this (I think!) if people already auto saved the log. This version made saving the log a default option - which is different to previous versions. Not sure when this change will make it into another 'released' version though...sorry!