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?

[NetRanger]

Hope to see the new FLAC v1.3.0 being added to CUETools v2.1.5 before it gets officially released.

[arbingordon]

Is there an archive of older versions of cuetools (and cueripper)?
2.1.4 and 2.1.5 fail to rip a number of CDs that rip flawlessly for me on EAC.
I'd just like to roll back to a version that works.

[db1989]

It would be better for everyone involved if you could provide details about the problem and the affected CDs so that Gregory could attempt to fix the issue, thus saving you from having to miss out on newer features simply to avoid a problem that almost certainly is fixable.

I would recommend a source of older versions that can fill the gap until such time as Gregory can address the issue, but I am not aware whether or not such a thing exists.

[korth]

The make and model of the drive can also be helpful to Grigory.

http://www.cuetools.net/install/CUETools_2.1.1.rar
http://www.cuetools.net/install/CUETools_2.1.2a.rar

These older versions are not fully compatible with the current CUETools DataBase.

This post has been edited by korth: May 31 2013, 04:41

[korth]

Samsung TSSTcorp CDDVDW SH-S203B drive
Tested with CUERipper 2.1.4 & 2.1.5 only
On extremely scuffed/scratched/dirty discs and some discs longer than 74 minutes, I get



some time after the Error Correction bar lights up. The rip aborts at this point and there are no log files written.
Cleaning/polishing the disc does prevent the exception on some.

[mistermac]

Sorry for offtop, but I need the source code for CUETools 1.9.5a very much!
Please, help me.

[Gregory S. Chudo...]

It's probably this, but why would you need a version so old?
https://sourceforge.net/p/cuetoolsnet/code/...04289fb/tarball

[mistermac]

Looks like it, thank you.

Previously, source code of the older versions could be easily downloaded from the first page. It was very convenient.
Let version is the old, but I'm satisfied with everything, especially with interface. There is just a pair of functions that I would like to add.

[Dario]

Are there plans to make CUETools work with single-track albums? Currently, if I drag the track (of which the album consists), it gives me an error saying that I didn't input an album. In order to get around this, I have to create a dummy CUE sheet, which can be a bit of a hassle.

[Rollin]

Currently, if I drag the track (of which the album consists), it gives me an error saying that I didn't input an album. In order to get around this, I have to create a dummy CUE sheet, which can be a bit of a hassle.

You can drag m3u playlist

This post has been edited by Rollin: Jun 7 2013, 17:15

[ChronoSphere]

Is it not possible to browse through network shares with CUETools? I have my music library located in one and even though it's added into my music library, CUETools doesn't seem to see it.

[ChronoSphere]

Some other things I noticed:

- When transcoding to the same path as source files, it asks you if you want to overwrite, yet says source = dest is not possible if you confirm. Can't it transcode to a temp file, then rename it to overwrite the source as the prompt suggests is possible?

- When transcoding an album that has multiple track artists, CUETools insists on picking the first track artist as album artist in batch mode, messing up the tags. Suggestion: allow to customize that, for example set to predefined string/leave album artist empty/prompt on multiple track artists

- Is it possible to process ONLY the .cue files? As it is now, you have to go to each directory and explicitly tick only the .cue, else which is rather cumbersome if you want to transcode your whole library. I tried looking into scripting, but there seems to be no documentation on the syntax/object properties

- Would be nice to have an option to ALWAYS save .cue as utf-8, looks like it didn't made into 2.1.5

[Corwin]

Is it not possible to browse through network shares with CUETools?

I'm running CueTools in an XP Virtual Machine on Linux, with a Samba file server on another Linux box. I can browse/verify/repair over the network using an SMB share.

[Corwin]

- Would be nice to have an option to ALWAYS save .cue as utf-8, looks like it didn't made into 2.1.5

I agree completely, but from what I've deduced, if there are no Unicode chars in a file, then utf-8 == ASCII. There would have to be some kind of header/footer added using utf-8 only chars to actually make the file utf-8.

This post has been edited by Corwin: Jun 14 2013, 22:21