Skip to main content

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

0 Members and 1 Guest are viewing this topic.
  • o770
  • [*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2225
Hi. Where did my tracks comment tag go after ripping? You know, that comment field inside the track itself - when you click the track in Cueripper tracklist.
I used that for the release years of tracks in my compilation albums and some additional notes but it's missing in Foobar properties window after the Cue file has been loaded. Foobar only shows the album comment tag - that one from the button Meta in Cueripper.

  • korth
  • [*][*][*][*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2226
Known problem/bug mentioned here. I've already let Gregory know that it still isn't working in 2.1.5.
korth

  • o770
  • [*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2227
Ok... I failed to notice that. What tool do you recommend me to load the .cue file from Cueripper and fix the tags in my rips - image+.cue?
One more thing if I could, where would that comment field go if working? How can I create it?
  • Last Edit: 27 April, 2013, 07:21:37 PM by o770

  • korth
  • [*][*][*][*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2228
Depending on how many you need to do, you might just edit them in. cdrcue may do it but it's not free and you might just be editing them in using that app with the REM command anyway.

Code: [Select]
REM DATE 2011
REM DISCID AAAAAAAA
PERFORMER "Various Artists"
TITLE "Title"
FILE "File.flac" WAVE
  TRACK 01 AUDIO
   PERFORMER "Artist 1"
   TITLE "Title"
   [color=#FF0000]REM COMMENT "1974"[/color]
   INDEX 01 00:00:00
  TRACK 02 AUDIO
   PERFORMER "Artist 2"
   TITLE "Title"
   [color=#FF0000]REM COMMENT "1976"[/color]
   INDEX 01 00:...
  • Last Edit: 27 April, 2013, 07:49:24 PM by korth
korth

  • o770
  • [*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2229
That works for me as long as the album comment field hasn't been used - the one in the header, just like in your example. I need something else but I guess that's for another topic. I wonder how Cueripper could manage both fields since they are presented separated in the GUI.
Thanks a lot, korth!

  • a3aan
  • [*][*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2230
Still hoping for writing of CTDB Accuracy values tags. Just like AccurateRip values tags. Any chance? Cheers, Adriaan.

CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2231
Regarding the complete integration between CueTools and CTDB, I am missing the "encode if verified" script to take into account the CTDB submissions as well since it seems to be already quite mature, and sometimes, even more useful than AR (especially for new releases). Hope it is in Gregory's plans for a future version.

CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2232
Hi. Where did my tracks comment tag go after ripping? You know, that comment field inside the track itself - when you click the track in Cueripper tracklist.
I used that for the release years of tracks in my compilation albums and some additional notes but it's missing in Foobar properties window after the Cue file has been loaded. Foobar only shows the album comment tag - that one from the button Meta in Cueripper.

It was supposed to be written as a tag. It will be fixed it in official release.

I'm not sure about per-track 'REM COMMENT' in CUESheet. CUESheets are not supposed to handle advanced tagging.
CUETools 2.1.4

CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2233
A special thanks to Gregory for the new (incoming) version  ...
One question : how can i change the 'totaltrack' & 'totaldisc' tags with the reference standard 'tracktotal' & 'disktotal' during the flac creation ?
'Albumartist' tag is supported ? In the setting file i don't see anything...
Any chance in future to see the option 'capitalize first letter' in the tags option ?
Thanks in advance .


Anyone can help me  ?
Tnx.

  • korth
  • [*][*][*][*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2234
I'm not sure about per-track 'REM COMMENT' in CUESheet.
That's just something that works in the Foobar properties window provided to satisfy
but it's missing in Foobar properties window after the Cue file has been loaded. Foobar only shows the album comment tag

If I remember correctly I got the per-track 'REM COMMENT' from the foo_cuesheet_creator component. I don't expect it to be part of CUERipper.
  • Last Edit: 28 April, 2013, 01:22:43 PM by korth
korth

CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2235
"albumartist" is supported and is used instead of "artist" whenever you set different artists for different tracks.

I think i switched to 'tracktotal' & 'disktotal' because 'totaltrack' & 'totaldisc' were not supported by foobar2000.
If i'm wrong, i can just fix it. If i'm right, i will probably need to think about adding "foobar2000-compatible tagging" option.

As for 'capitalize first letter' button, i don't like it.
CUETools 2.1.4

  • marc2003
  • [*][*][*][*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2236
foobar2000 changed sometime ago to use the more widely accepted TRACKTOTAL and DISCTOTAL by default. it still has options for writing in it's older format. i think it still reads from both.



edit: according to the changelog, this happened in 1.1.8
  • Last Edit: 28 April, 2013, 01:33:23 PM by marc2003

CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2237
Thanks. That's good news.
CUETools 2.1.4

  • o770
  • [*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2238
So the track comment may be a field exclusive to per-track rips, added to the audio files; it would be disabled otherwise...?

I suggest having any possible tag available to the tracks separately, either for tracks and image rips.

It was supposed to be written as a tag. It will be fixed it in official release.
  • Last Edit: 28 April, 2013, 03:13:21 PM by o770

CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2239
Foobar has a way of keeping per-track tags in image (if it has embedded cuesheet): it uses "cue_trackNN_" prefix. That's the way cuetools stores AR tags for example.
CUETools 2.1.4

  • Eli
  • [*][*][*][*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2240
Gregory, has/or will reading TOCs in meta data make it to 2.1.5? Can't wait to be able to scan my 8000 albums!

CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2241
Yes
CUETools 2.1.4

  • MrSinatra
  • [*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2242
first, I apologize if this is the wrong place to post this, please correct me if so.

second, I want to thank the dev, as I made bad EAC rips that the "truncate offset" feature fixed! 

third, I want to report a bug, or perhaps get instruction if that's what I need:

I had made FLACs (single per track files, tagged, no cue sheets) of the beatles remasters using EAC / Flac 1.2.1 some years ago that had the offset issue.  I have since seen cuetools make new flacs out of them that play gaplessly, and so that's great.

however, one of my tag fields, TRACKNUMBER, does not seem to exist in the new flacs at all?  is that by design?  how do I get the track number in the new files tag?  (it is in the filename as well btw)

also, all my tag fields are now capitalized and reordered, such that my RG fields, for some reason, are listed first.  again, by design?

I also have other questions about cuetools and the encoders, etc, but where would be the best place to post them, as I assume its not this thread?

thanks again!!!

  • korth
  • [*][*][*][*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2243
Did you change any of the Advanced Settings? 'Write basic tags from CUE data' needs to checked for TRACKNUMBER even if there is no Input CUE sheet (CUETools creates a 'dummy' CUE sheet if none exists).

Capitalization is likely from the metadata source. If you used a batch input mode and don't want tag data used from freedb, musicbrainz, etc., you can disable them.
  • Last Edit: 29 April, 2013, 01:34:53 PM by korth
korth

  • MrSinatra
  • [*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2244
thx for the reply, I think it helped.  hope you don't mind bearing with me...

Did you change any of the Advanced Settings? 'Write basic tags from CUE data' needs to checked for TRACKNUMBER even if there is no Input CUE sheet (CUETools creates a 'dummy' CUE sheet if none exists).


yes, I did change settings, including that one.  I have to say, I find it misleading, but I do understand.  putting it back fixed it, but doing so now adds a comment field and value I don't want: "CUETools generated dummy CUE sheet"  ...can I turn that off?  it just makes work for me having to delete it afterwards.

Capitalization is likely from the metadata source. If you used a batch input mode and don't want tag data used from freedb, musicbrainz, etc., you can disable them.


I dragged a folder to the cuetools input line.  I had freedb and musicbrainz unchecked.  I think maybe I was unclear...

in the orig flac files, some of the actual FIELD-names, (not the values for the field names, but the field names themselves), are NOT capitalized.  in the new FLACs cuetools makes, they are ALL capitalized.  (again, the field names, not the values).  in addition, they are re-ordered such that the RG fields and values come first, as well as other changes.

is that typical and desired?

some other issues:

when I converted to ALAC, i noticed it embedded the artwork, even though i had that pref unchecked.  is that not a bug?  do i have to uncheck all the art options to get it not to happen on m4a?

which library for alac is the "official" one?  libALAC or ffmpeg alac?  its great to have these choices, but where can i see a pros/cons to pick between them?

at the very top, i pick "fix" but i get the feeling convert or default would yield the same result for me, in so far as fixing my offset issue; similarly, do i really need to pick "fix offset" in the action box, as it seems default does that anyway, and whats repair for?

sorry for overloading this post!  thx for the help!

CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2245
doing so now adds a comment field and value I don't want: "CUETools generated dummy CUE sheet"  ...can I turn that off?  it just makes work for me having to delete it afterwards.
I'd like to second that. It makes sense to put this in the .cuesheet, but why put it in the files themselves?

  • korth
  • [*][*][*][*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2246
MrSinatra,
I'll defer on the 'CUETools generated dummy CUE sheet' and 'FIELD-names' questions.

Embedded artwork does seem to be a bug and not limited to ALAC. 'Copy album art tags' AND 'Embed Folder.jpg' need to be unchecked to prevent embedded art even if the input files don't have embedded art.

ffmpeg alac is an external encoder. It was used before the built-in encoder was added. Users may still use it if they wish (the user must supply the ffmpeg.exe for it to work).

Profiles are used to 'preset' your settings for different tasks. 'fix' is a preset for 'fix offset' which refers to 'drive offset correction' not the '[a href='index.php?act=findpost&pid=831858']compression offset[/a]' fix by truncating the extra 4608 samples. You should use the 'default' profile for that.

You can find out a little more about 'repair' here.
  • Last Edit: 29 April, 2013, 07:35:00 PM by korth
korth

  • dizzy274
  • [*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2247
Hi All

First post here, so please bear with me.....

I've been running Cuetools under XP for years with no problems - recently I've switched to Windows 8 and all is ok except:-

When verifying and creating an Accuraterip log ( xxx.accuraterip ), I can't automatically overwrite it. I've ticked the box "Remember my choice" in the "Overwrite" panel, but it won't remember my choice.

This occurs with both 2.1.4 & 2.1.5.

Any ideas?

Best regards.

Ian.
balr 2,0
using *,2

CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2248
The "remember my choice" only seems to work for this current run, as in, you select multiple albums and it asks you if you want to overwrite the .accurip. You tick  the checkbox and it doesn't ask you for the other selected albums. I think this is intended and is not dependent on the OS version.

  • marc2003
  • [*][*][*][*][*]
CUETools versions 1.9.5 through 2.1.5 (current)
Reply #2249
oh phooey, i just bought a new drive having not had one for over a year and cueripper doesn't like it. it fetches metadata/AR/CTDB data but fails when the progress bar of detecting gaps reaches 100%.



a few details: LITE-ON iHAS 524 internal sata drive, gigabyte motherboard with intel h61 chipset, windows 7 x64

i tried several disks and they all error at the same place. foobar2000 and EAC both rip those same disks just fine.

cueripper did manage to rip 1 disk though - it was an enhanced CD with 13 audio tracks and a data track. all the ones that failed are just standard audio. any ideas?