Skip to main content

Topic: CUETools versions 1.9.5 through 2.1.5 (current) (Read 1367280 times) previous topic - next topic

0 Members and 4 Guests are viewing this topic.
  • Porcus
  • [*][*][*][*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2900
I have mentioned this before I think, but never uploaded it. A sample of probably some of the worst few seconds that CUETools ever repaired: https://hydrogenaud.io/index.php/topic,113978.new.html

  • NetRanger
  • [*][*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2901
A little 'request'...... what about making it possible to use a FLAC Binary with this great tool of yours Gregory.

  • korth
  • [*][*][*][*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2902
korth

  • NetRanger
  • [*][*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2903
Thnx for the reminder korth. Totally forgot about that.

  • madmalkav
  • [*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2904
Anything I can do for Cueripper to write unicode filenames on the CUE? The filenames are OK after I found the tip about editing settings.txt in %appdata% and changed the ANSI safe filename param to 0 but the CUE still uses ANSI.  If I load the flac files on Cuetools and generate CUE then it have proper unicode filenames inside.
  • Last Edit: 10 May, 2017, 12:12:35 PM by madmalkav

  • Lexeremo
  • [*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2905
I'm getting the error "Exception: First index must start at file beginning"

Please help me =(

Quote
REM GENRE Game
REM DATE 2009
REM DISCID A910410D
REM COMMENT "ExactAudioCopy v0.99pb5"
PERFORMER "EastNewSound"
TITLE "Sacred Factor"
FILE "Sacred Factor.tta" WAVE
  TRACK 01 AUDIO
    TITLE "song for bird"
    PERFORMER "リツカ"
    INDEX 01 00:02:00
  TRACK 02 AUDIO
    TITLE "Your Color"
    PERFORMER "Cryu"
    INDEX 01 04:55:08
  TRACK 03 AUDIO
    TITLE "Lucid Dream"
    PERFORMER "茶太"
    INDEX 01 10:45:40

  • korth
  • [*][*][*][*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2906
The file should begin at 00:00:00
Track 01 begins at 00:02:00

Add INDEX 00 00:00:00 to show where the file begins.
Quote
FILE "Sacred Factor.tta" WAVE
  TRACK 01 AUDIO
    TITLE "song for bird"
    PERFORMER "リツカ"
    INDEX 00 00:00:00
    INDEX 01 00:02:00
korth

  • hydrogenate
  • [*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2907
Sorry, posted in wrong section.  :-[ 
  • Last Edit: 30 June, 2017, 09:42:26 AM by hydrogenate

  • Coreda
  • [*][*][*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2908
So this has been an issue for a little while (perhaps six months?), metadata sourced from Discogs now adds a space and comma character after the Artist tag, despite it not displaying as such in the CUERipper UI.

So it will display as say, The Beatles in the CUERipper UI, but when ripped it will output to The Beatles , - which will include directories and filenames if that's part of the user's output template.

Using v2.1.5

  • Cellfish
  • [*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2909
Thank you for making CUETools.  I love it, and use it all the time :)


Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2910
Hi !
It seems that the sync between CTDB and musicbrainz is down again.
 ( probably because of : https://blog.musicbrainz.org/2017/05/16/schema-change-release-2017-05-15-including-upgrade-instructions/ )

Is it possible to have a look ?

Best Regard, and thanks for your work :D

  • Porcus
  • [*][*][*][*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2911
A bug-ish behaviour that may be known:

When there is already a CDTOC, CUETools may sometimes write a second one. And I will have e.g.
11+96+4D77+B2EB+10223+186D4+1F433+26051+2BBDA+30844+3461B+3737B+38B30+3C070+3DEBE+42930+48EA4+4F095+55115; 11+96+4D77+B2EB+10223+186D4+1F433+26051+2BBDA+30844+3461B+3737B+38B30+3C070+3DEBE+42930+48EA4+4F095+55115
note: both are equal
- and next time I try to verify, CUETools refuses to recognize that track as part of the CD with the others.

Suggestion: if the CDTOC-to-be-written is the same as one already present, do not write.

Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2912
As reported on this user talk page, the wiki page CUETools Download may need to be updated.

(by the way, this thread's first post needs to be updated too :)

  • Porcus
  • [*][*][*][*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2913
I did a round of AccurateRip-retroverification ... I know that ripping without cross-pressing checking is soooo last decade, but about ninety percent of my rips were done before dBpoweramp implemented that feature.
So out of about 7250 CDs, approx.:
* 3800 were Accurate upon ripping;
* 2500 more verify (confidence at least 2, since "1" would be mine - except some purged submissions); a few by PerfectTunes, but most of them by CUETools.
... out of the 2500, 51 were repaired by CUETools first.
* 700 are still the only submission (many self-released and from basement labels);
* 150 seem to have a competing entry, not sure if mine or the other is right
* 70 are bad rips
* 30 are HDCDs which I decoded upon ripping. Ignorance, argh.

So if (*guess!*) half the "competing entry" ones are indeed bad, then CUETools managed to repair 1/4 of my bad rips.
Despite an "adverse" selection: I re-ripped a few CDs which upon ripping had some Accurate and one or two Inaccurate tracks - and if they were not that rare, they should have had a better chance of being repairable.

Not counting classical music (different folder, must be counted manually, too lazy) .


And, a gentle bump, while I'm at it:
Here is a case where CUETools and fb2k on one hand, compute the AccurateRip (V1) checksum different from what dBpoweramp and PerfectTunes do:



Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2914
Thanks, very interesting statistics.

In my dream universe record labels (including the basement ones) would submit reliable data to the database for each CD they plan to print, so even if there are consistent errors in all the copies we could still all repair them ;)
CUETools 2.1.6

  • Porcus
  • [*][*][*][*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2915
In a not-so-optimal universe, I still keep my CDs ... but hell I do not want to re-rip. Ever. That was some job ...

By the way, you need to upgrade your signature :-o

  • Putsli
  • [*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2916
Greetings!
When I transcode flac into aac using CUETools.Converter, the entries in the main tags of the new file are duplicated, like: "ALBUMARTIST: Al Chem; Al Chem" How can I fix this?

Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2917
When using "CUETools.exe /convert" in a batch file, how can I make the GUI automatically exit after it's finished processing?

  • dpr
  • [*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2918
Hi, I'm unable to encode compilations with Cuetools 2.1.5.

I have a CUE file with the COMPILATION flag set, and can encode mp3 files for all of the tracks. Other meta data from the CUE file is created as tags in the mp3 files, but not the 'part of a compilation'.

I am new to using Cuetools, but not to cuefiles;  I have a number of images and cue files that i created with eac and have successfully encoded using LAME to create these files with the metadata including the compilation flag.

The input cue file has the following:

REM GENRE Christmas-Rock
REM DATE 1963
REM DISCID B4083E0D
REM COMMENT "ExactAudioCopy v0.99pb3"
REM COMPILATION 1
PERFORMER "Various Artists"
TITLE "A Christmas Gift for You from Phil Spector"
etc

All of the mp3s are created with the year, genre and the Various Artists performer from the cue file, but the "Part of the Compilation" flag is not set.  I have also tried changing the REM COMPILATION 1 line to REM COMPILATION TRUE.

I must be missing something obvious. Please can anyone clue me in? Also how to post 'code snippets'
Thanks
dpr







Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2919
For converting a huge amount of image+cue files to lossy files, is there a way to NOT have the cue file copied over to the destination directory. I tested with 2.15 and haven't been able to stop the cue file being copied. Is there a newer build with the option? Thanks

  • korth
  • [*][*][*][*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2920
https://hydrogenaud.io/index.php/topic,66233.msg819468.html#msg819468
Option to not write the CUE hasn't been added as of the current version.
korth

Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2921
https://hydrogenaud.io/index.php/topic,66233.msg819468.html#msg819468
Option to not write the CUE hasn't been added as of the current version.

I've just tried with 2.1.6 (The current version?) and it's still writing the cue file when converting to lossy m4a files.

  • hydrogenate
  • [*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2922
CUETools 2.1.6. & Windows 7 x64

Hi  :)

During the process of splitting a single FLAC into multiples, CUETools abruptly stops the process, and displays this error message:

"flac.exe has exited prematurely with code 1: The pipe has been ended."

Could someone please explain what causes this, and perhaps offer the appropriate solution?

Thank you.
  • Last Edit: 05 December, 2017, 09:37:00 AM by hydrogenate

  • korth
  • [*][*][*][*][*]
Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2923
flac will exit with code 1 if there were any errors, including when the MD5 checksum doesn't match the audio.
Can you run Action:Verify on the input without error?
You can also test your input file for errors with the flac frontend or with the flac command-line flac.exe -t yourinputfile.flac
korth

Re: CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2924
If it happens right away, it might be due to wrong command line parameters.
CUETools 2.1.6