Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: [Wishlist] Suggestions/Requests for CUETools, CUERipper, etc. (Read 8455 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: [Wishlist] Suggestions/Requests for CUETools, CUERipper, etc.

Reply #25
CueRipper

I would like to rip the audio tracks and run the encoder in the background
today it's non sense , rip a track ,wait to encode and re-start to spin the drive to rip the second track and so on
it could rip all the tracks in a temp folder maybe chooses/selected by the user (to speed up , maybe a scratch disk) and encode the track in the background
beause rip 1 disk is ok , but if somebody do need to rip 30 cds , well it does become very slow
thanks ,take care

Re: [Wishlist] Suggestions/Requests for CUETools, CUERipper, etc.

Reply #26
Would be great if the limites were extended"
Error Limits
More than 99 tracks - Exception: [Index] out of range
Track start position ~140 minutes or above - Exception: invalid stride

Especially the last one.
Isn't 99 or 100 tracks the limit of the RedBook CD TOC specification, though?
Where have you seen a CD with more than that?

As for the 140 minute limit, I don't know, but I suspect it's a similar situation.
140 is double of 70, which is the approximate duration of first generation audio CDs. Maybe they were counting on packing double density in the future and made room in the format for that. I don't know, I'm just speculating.

It sounds like you are trying to do out-of-spec stuff. CUETools is a CD-centered software, as far as I know, so it seems reasonable that it should follow the specification.

Indeed, but if it already has a time limit way above of what a physical disc can handle, it could be raised even higher. Same with number of tracks, so that bandcamp releases that exceed those could still be processed for example. EAC already gives up after INDEX exceeding 90-99 minute mark, while CueTools could rip longer "discs" (virtual image+cue), it just so happens that I finally encountered one that is longer than said limit and it would be great if it could process ~150 minute album. Maybe there's something that can be changed (cracked) in the source code manually.

Re: [Wishlist] Suggestions/Requests for CUETools, CUERipper, etc.

Reply #27
Improve keyboard navigation when manually adding metadata in to CUERipper.

Adding in any metadata and pressing enter does not move down and activate the next field. This makes adding metadata cumbersome because a mouse needs to be used to activate the next field. If in track view pressing enter on the field correctly moves down to the next field and allows that field to be edited.


+1

- add unicode support to cueripper and allow definition of character substitution

Re: [Wishlist] Suggestions/Requests for CUETools, CUERipper, etc.

Reply #28

Specify filename pattern(s) for a number of files to be copied to the output folder. For example, "*.jpg,*.pdf"
tick box to enable.

I have multiple files with artwork including pdfs of booklets that I would like to copy into the output folder.

Re: [Wishlist] Suggestions/Requests for CUETools, CUERipper, etc.

Reply #29
Drop free/gnudb in favour of musicbrainz in cueripper (both read and write, of course).

Agree - write MBID tags to encoded flac and MP files if the release is found in MB