CUETools versions 1.9.5 through 2.1.4 (current), AccurateRip support & more Options

[bilbo]

And it sounds like CUERipper is using C2 pointers with my drive, and the log is just wrong. I don't like that there is boilerplate text that misrepresents settings.

Setting C2 to yes is not desirable in an EAC style log. Did you try setting "EAC style log" to false in the options?

This post has been edited by bilbo: May 22 2013, 14:10

[mjb2006]

Setting C2 to yes is not desirable in an EAC style log.

If C2 pointers are used, why would you want the log to say they weren't?

Did you try setting "EAC style log" to false in the options?

Well, yeah, but that produces CUERipper's native log format, which doesn't say whether C2 pointers were used at all.

[ligerpants]

As a longtime user, I'm happy to see that 2.1.5 is forthcoming. However, even in the new beta, when running Verify on .ape or .tak files, it seems like the ACCURATERIP* tags aren't being updated, as they are in .flac files.

I have tested this using embedded and track-separated .ape and .tak files, and examining/reloading tags in the latest Foobar2000. 2.1.4 behaves the same way. I only noticed this because I use embedded .tak files maintained by CUETools to store/port my CD collection.

Is this something I'm doing wrong, or a minor bug?