Skip to main content
Topic: [Wishlist] Suggestions/Requests for CUETools, CUERipper, etc. (Read 979 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

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

Suggestions/Requests

Making a suggestion or request does not guarantee that a feature will be added or changed. The developer will ultimately decide what direction the software will go, what the priorities are and how to allocate time while working on the project. As users we can only present an alternate viewpoint.

If you're familiar with C#, you could create a patch or pull request to contribute to the project. However if programming is not in your skill set, I created this thread to politely Suggest/Request features for CUETools, CUERipper, or one of the other programs in the CUETools suite.

I perused the most recent replies (1500 or so) in the old development thread (plus a few other posts) and compiled a list of repeated suggestions/requests to get things started. The list is not in any specific order. I only attempted to sort by program, not priority.

I excluded suggestions/requests that were already added or being worked on such as OPUS support or the latest versions of FLAC and Monkey's Audio. If I missed your Suggestion/Request, providing a link to the original post is sufficient. (Copy/paste the link from "Reply #nn" in the upper left corner of your original post). Please don't double-post. Please check the list before you post. With all Suggestions/Requests in one thread and/or compiled as a list, you shouldn't need to keep repeating them.


korth

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

Reply #1
General (Could apply to more than one program)

  • SMART (hybrid) HTOA Gap handling
    If Track One pregap is say 5 seconds or longer use Gaps Appended + HTOA. For anything less than 5 seconds, automatically switch to Gaps Appended. The user would no longer have to deal with all those 32, 33, 37, etc. silent (or inaudible) frames saved as an HTOA file just to be able to catch a real hidden track before track one.
  • Tagging the HTOA file.
    This could be an issue for the CUETools file grouping feature. [doubtful]
  • Encode lossless input files other than 16-bit, 44.1kHz, 2 channel (Redbook)
    Such as 16/24-bit, 48/96/192kHz flac with 2 or more channels. [penciled in as a possible feature of BLUTools which already handles non-redbook PCM audio extraction]
  • Split lossless input files other than 16-bit, 44.1kHz, 2 channel (Redbook)
    Such as 16/24-bit, 48/96/192kHz flac with 2 or more channels. [penciled in as a possible feature of BLUTools which already handles non-redbook PCM audio extraction]
  • Full AccurateRip v2 support
    Cross pressing verification using ARv2
  • Support for detecting UTF-8 input without BOM
    Currently wide characters in UTF-8 files without BOM are interpreted as two one-byte characters from the local code page.
  • Option to always write utf-8 CUE sheet
    Currently the CUE sheet is only saved in utf-8 if there are characters not in your local codepage.
  • Option to disable writing a CUE sheet for separate tracks
    A CUE sheet is not needed for lossy formats.
  • Option to "Force Compliant CUE" sheet for separate tracks
    Data could be preserved by REMarking out the HTOA, Index 00 and other non-compliant lines.
  • The ability to add custom metadata fields
    The name and content of the field would need to be manually entered.
  • GD3 metadata retrieval support.
    If the user wants to use a paid subscription to the GD3 service. [doubtful]
  • ReplayGain support
    Various Requests. Copying: CUE data to CUE data, CUE data to Tags, Tags to CUE data, Tags to Tags. Analysis: to CUE data, to Tags.
  • Download mirrors and file hashes
    [forum] [github] > mirror added at github for v2.1.7 [mirror]; file hashes added to [Download Page].


korth

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

Reply #2
CUETools.exe

  • 'Album art search' is not yet functioning in CUETools.
    Users suggested/requested that this be added.
  • When encoding, ISRC commands are not copied from the original CUE file to the new CUE file.
    Users suggested/requested that this be added.
  • When encoding, the source Unicode (UCS-2 le) EAC extraction log is converted to ANSI in the Output folder.
    If the user enabled the log checksum feature in EAC, the new LOG file can no longer be checked by the EAC log verifier. Some users have suggested/requested that the original log file be copied to the Output folder without the text encoding being altered.  >
    addressed in commit 9f80400
  • CLI CUETools.exe /<profile> does not return CTDB verification even with 'Use CTDB' & 'Verify Using CTDB' checked and saved in the profile.
    (/verify, /convert, /fix) Only AccurateRip verification results are returned.
  • In the 'Extra' section, it is difficult to enter negative numbers in the 'Offset' box.
    The zero wants to hang around.  >
    addressed in commit cacc461
  • After repairing a rip, the accurip log does not contain CTDB info even though 'Verify Using CTDB' is checked.
    Perhaps CUETools should rerun verify after repair.
  • iTunes "Part of a compilation" support.
    https://hydrogenaud.io/index.php/topic,66233.msg947413.html#msg947413
  • Support parsing of data from other extraction logs in addition to EAC & CUERipper.
    XLD for example.
  • Create CUE Sheet from an extraction log file
    To recover the CUE if 3rd-party tagging software removes/deletes an embedded CUE or the CUE file from an Image+CUE is damaged, corrupt or accidentally deleted.
  • In-place conversion
    Output to the source folder without concern for existing filenames.
  • CUE Sheet POSTGAP command support
    Supported by ImgBurn, Alcohol 120%


korth

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

Reply #3
CUERipper.exe

  • Add external encoders from the GUI.
    Right now you need to edit the settings.txt file.
  • More setting options available from the GUI.
    Right now you need to edit the settings.txt file.
  • Save/store Output templates separately for lossy and lossless encoding.
    So the user doesn't need to remember to manually change the template when switching between lossy and lossless.
  • Rip and save to both lossy and lossless simultaneously.
    So you don't have to rip it twice or convert with CUETools to have both.
  • Rip single pass (burst) using AccurateRip/CTDB verification then secure rip only the tracks that didn't verify.
    Other rippers are doing something similar now.
  • Re-rip Selected Tracks
    Instead of always having to re-rip the whole CD to try get a better copy of one or two tracks that had errors.
  • Extract through error messages.
    Right now extraction stops on some Errors/Exceptions such as Error Reading CD: IOCTL Failed. Users thought that they should be able to rip the remaining tracks.
  • Reject the metadata retrieved from CTDB
    Provide a blank space (or Unknown Artist - Unknown Title) in the metadata selection drop-down list for when the metadata retrieved is not correct for the inserted media (this can happen with CD Singles for example when only freedb results are returned).
  • Import local artwork
    When no artwork is available from CTDB.
  • Import local metadata into CUERipper (or local database)
    from a text file, clipboard list or xml. Editing a few fields is simple enough but filling in all the blanks within CUERipper can be exhausting (especially if a refresh happens and everything gets blanked, making the user start over > refresh addressed in commit a2b12d1).
  • Add options to Detect/Decode HDCD
    Similar to what exists in CUETools.exe


korth

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

Reply #4
Other programs in the CUETools suite

CUETools.ARCUE.exe (formerly ArCueDotNet.exe)

  • An option to specify the offset
    to be used during AccurateRip verification.

CUETools.Ripper.Console.exe (formerly CUETools.ConsoleRipper.exe)

  • Don't try to write a WAV and CUE file with illegal file characters
    [forum] [github] > addressed in commit 2bde923
  • Don't overwrite existing files without warning (including Multi-CD sets that use same %album%)
    [forum]
  • Don't write utf-8 CUE file without BOM
    CUETools.exe interprets text as all single-byte characters in local codepage [General#06].


korth

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

Reply #5

((( SPACE RESERVED )))



korth

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

Reply #6
((( SPACE RESERVED )))



korth

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

Reply #7
Suggestion:
Make the Multiselect browser more user-friendly by letting the user choose which entries get a tick-mark (e.g. based on file extension).

Problem:
Currently, if there are one or more .cue files, an m3u playlist, and the music files (flac) in a folder, then opening the Multiselect Browser on the Parent folder will automatically select (set a tick-mark for) each of these entries.
If you don't manually de-select some of them, you will end up running the verification multiple times for the same data, which is obviously not ideal, especially since the Multiselect Browser is used when you have lots of albums to verify (so that would mean LOTS of manual unticking of boxes..).

So, what I'm envisioning is
EITHER a field in the settings, where the user could specify something like "*.cue" and then only the cue sheets would get a tick mark automatically,
OR some kind of context menu in the Multiselect Browser itself, that lets users select/deselect file extensions to be checked/unchecked.

Thanks for considering.

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

Reply #8
Enable CUERipper to repair errors using CTDB.
Allow CUERipper to automatically transform metadata, such as "Capitalize First Letter Of All Words".
Enable CUERipper to calculate and write Album and Track ReplayGain values.
Allow persistent setting of which tag fields are written, for instance by placing checkboxes to left of fields on "Metadata" window.  I only want to write ALBUM, ARTIST, YEAR, TITLE, TRACK, GENRE, ALBUM GAIN and TRACK GAIN.
Allow ability to turn off creation of "non-music" extra files, e.g. logs, CUE, ACCURIP.

Thanks for asking.

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

Reply #9
The upper case first letter suggested by Apesbrain is a good idea i second.
I wanted to have a chance to not write the Comment from the CUE to tag years ago.
For my workflow maybe a pull down list for the Genre field like in mp3tag was nice.
Is troll-adiposity coming from feederism?
With 24bit music you can listen to silence much louder!

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

Reply #10
Please add a function to CUETools so that it checks the functionality of CUE (FILE "album.flac / ape / wv" WAVE) and creates a new one only in the absence, that is (FILE "album.wav" WAVE). Sorry for google translate.

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

Reply #11
Hello,

Thanks for pulling the list together!

Requests for writing mp3 files with cuetools
1. support for ISRC tag (repeat of above) - is there a way to vote?
2. support for CATALOG tag.
3. support for COMPOSER tag.
4. musicbrainz support. If a match is made with music brainz, include the music brainz release and trackids as  TXXX tags in the MP3 file (see https://picard.musicbrainz.org/docs/mappings/ for details. and mappings).
Thanks

 
SimplePortal 1.0.0 RC1 © 2008-2020