Skip to main content
Topic: CUESHEET tag not recognized by Foobar2000 (Read 351 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

CUESHEET tag not recognized by Foobar2000

After creating a flac with this (on W2K, with flac version 1.3.2, wav from EAC 1.3)
  flac -f -4 -V "2016 - Uncharted.wav" -o "2016 - Uncharted.flac"

and adding the tag CUESHEET from a cue file created by EAC (W2K, EAC 1.3, metaflac 1.3.2 ) like so
  metaflac --no-utf8-convert --set-tag-from-file="CUESHEET=2016 - Uncharted.cue" "2016 - Uncharted.flac"

this tag does not show in the properties of the flac by FB2K (W2K, FB2K 1.4.3) and the tracks are also not shown in the playlist. Leaving out the '--no-utf8-convert' option makes no difference.

Looking at the tags with Mp3tag (W2K, Mp3tag 2.93), under 'extended tags' the CUESHEET tag is definitely there.

Adding CUESHEET manually in FB2K via properties and pasting the entire contents of the cue file works , so the problem is not with the contents of the cue file. The tracks are not shown until the file is loaded again into FB2K however, and the data is not stored as a single tag but added as separate album, artist and track list under a CUESHEET tag. One tag or several is fine by me as long as FB2K recognizes it.

My question is therefore: what is the correct way of adding the cue data from the command line? In old threads there is talk of removing all other tags first but a freshly created flac file has none, and in any case running
  metaflac --remove-all-tags "2016 - Uncharted.flac"
before adding CUESHEET with metaflac makes no difference to FB2K


Thanks for any insights,
M.


 

Re: CUESHEET tag not recognized by Foobar2000

Reply #1
Does this CUE file have Unicode BOM?

Re: CUESHEET tag not recognized by Foobar2000

Reply #2
According to https://stackoverflow.com/questions/2223882/whats-the-difference-between-utf-8-and-utf-8-without-bom
the UTF-8 BOM places EF BB BF at the beginning of a text stream, and a text editor that displays hex such as 'HxD Hex Editor' does in fact reveal this is there in the cue file (also attached).

This is not shown by normal text editors so I may have to eat my words that it is not a problem with the file.
Removing the three characters, applying the modified cue file to a fresh flac and opening that in FB2K shows a nice track list.
BOM therefore seems to be the culprit.

I looked through the EAC options and found no switch to toggle BOM on or off for the cue file, so it has to be dealt with.
(https://wiki.hydrogenaud.io/index.php?title=EAC_and_Cue_Sheets has no mention of BOM)

Can FB2K be told to understand BOMified CUESHEET tags or is a pre-processing step needed?

Re: CUESHEET tag not recognized by Foobar2000

Reply #3
Can FB2K be told to understand BOMified CUESHEET tags or is a pre-processing step needed?
I suspect that such tag is not spec-compliant. Actually, flac/metaflac should handle it. But it's not implemented, and I doubt that it will be implemented soon.

Re: CUESHEET tag not recognized by Foobar2000

Reply #4
Hmm, this is odd... Recently I ran into a situation where I was forced to save the cuesheet with a BOM in order to force FB2K to display album and track titles properly... so it does read BOMified cuesheets... truth be told, this was an external cuesheet...

PS.
a text editor that displays hex such as 'HxD Hex Editor' does in fact reveal this is there in the cue file (also attached).

This is not shown by normal text editors
Just as an FYI. Notepad++ has an Encoding menu indicating and allowing which encoding is used/to use, without having to resort to a HEX editor (in fact, using a plugin it's also capable to switch to HEX edit mode if desired )

 
SimplePortal 1.0.0 RC1 © 2008-2019