LIGHTNING UK!

CDA files don't really exists. They're just little pointers to the CDDA sectors on the disc that Windows displays when you browse an audio cd. Rip and convert your disc with something like Exact Audio Copy (EAC)

Whilst it would depend on the SATA -> USB 3.0 adapter being used, in real world tests, you'll never get anywhere near SATA 2 speeds on USB 3.0... or at least I didn't. I did a few about a year or so ago, pairing an SSD (OCZ Vertex 3 MI 120GB) with a USB 3.0 docking station (ThermalTake BlacX 5G) and an adapter (Akasa Flexstor Disklink). Neither of them managed to even reach 200MB/s. The drive would happily do 500MB/s on an Intel Z68 chipset SATA3 controller though.

The application makes no difference. Unless something funny is going on, hardware is always the limiting factor with these things. Go back to the disc that reads at different speeds in different drives and post the disc info from each one. If you're saying the disc info sometimes changes just from reinserting the disc, try to capture that change too. If both drives list the same read speed, they should both be able to read the disc in the same amount of time. The max read speed entry in the log after the read operation should match up and the transfer rate graphs should be nice smooth curves.

Rip lock? Different disc formats read at different speeds too.

How different are they exactly? Both buses are faster than the hardware (at least where reading is concerned) so there shouldn't be anything limiting the read speed except the drives themselves. SATA is loads faster than USB 2.0. You'd be lucky to see 35MB/s on USB 2.0. That's a walk in the park for SATA.

Yes

Read and verify are the same thing. The program is just sending the same 'read' command to the drive for both operations. It will have only failed to read because you were using a different drive - one that wasn't as good at reading the disc. Some are just better / more forgiving than others. If I've misunderstood your post and you were reading it in the same drive that verified it ok, maybe it was due to the drive / disc cooling down. The disc could have been borderline unreadable during the verify and 'just' unreadable by the time you tried to read it. I won't pretend to know how the drive does what it does when it comes to error handling / correction, that's not something software has to worry about. I just issue a 'read' command and the drive either processes it correctly or it errors out.

How is that post any different to your first one? I'm only going to tell you to try some decent double layer discs again - 'MKM-003-00' ones from Verbatim. If they fail too then your drive is probably dirty or broken.

It's hardly rocket science. If the offer page you're looking at doesn't have simple 'Yes, I want it' / 'No, I don't want it' type options, it'll have 'Express' / 'Custom' ones. Click 'Custom' and the opt-out option is then straight in front of you. I don't have anything to do with the design of these pages but they're nothing out of the ordinary and now the OpenCandy team have made the 'Custom' option look 'normal' again (it looked greyed out/disabled before), I can't really complain about them.

Maybe.... Maybe not.

DVD Video shouldn't really use ISO9660 at all and I don't know why they bother putting it on the disc. I'm sure everything would use the UDF file system over that one and they play the data based on pointers / offsets within the IFO rather than looking at file system / file names (beyond the IFO) anyway. You'd have to check the specs to see what they say about ISO9660 restrictions. The folders/files have very specific names (lengths, and all uppercase) so yeah it's probably going for 1988 for maximum compatibility with really dumb, old players.

You'd have to save as one long file and not split the tracks up if you don't want any digital silence (potentially being) added. You are just talking about a maximum of 1/75 of a second though (that's what 1 sector is... or 2352 bytes if you prefer it that way). Would you really notice it? Maybe... maybe not.

If the drive won't burn to that 'TDKBLD-Wfa-000' media, all I can suggest is trying some different discs.

The original spec for ISO9660 was really restricted / limited (this is what the '1988' option in ImgBurn's Build mode corresponds to). Since then, things have become a little more relaxed (the '1999' option).

http://forum.imgburn.com/index.php?showtopic=8000

Yeah it plays DVD ones but I'm not so sure about BD ones.

You should look into converting them to MKVs or something. You'd do that straight from the disc though. Reading the disc to an ISO and then extracting the ISO is the same as just copying the files from the disc.

It supports pregaps and postgaps, yes. The typical format of the times is MM:SS:FF, so yes, it supports frames.

Why are you calling this a bug when it's something you've done? It should be in 'support'. The lead-out address is relative to the file (same as the indexes)... so your final audio track looks like it's 45 minutes long, that's the problem here.

You can uninstall it by running the installation program on the download page I linked you to.

Why would you bother reading the disc with ImgBurn at all? Just copy the files off it using Explorer.

There's nothing in the log that'll tell you if you have the problem. You have to do some tests and examine the graphs. If you want to keep SPTD installed (because you use it with DAEMON Tools or whatever), at least ensure you're running the most recent version - v1.86 as of right now I believe. http://www.duplexsecure.com/en/downloads

If your drive has a nice smooth transfer rate curve when reading back a DVD, no. If it seems to hit a limit (before 16x or whatever it should be capable of) and then be a bit 'all over the place', maybe.

When it's dumping the fields from a structure (response from a given command), it'll use the names of those fields as specified in the spec. But at the top of the disc info where it shows the MID of a disc in the same place for all discs, it uses MID

imageburn