cue_track01_ALBUM=track 1 album titlecue_track01_ALBUM ARTIST=track one album artistcue_track01_artist=Artist track 1cue_track01_COMMENT=comments for track twocue_track01_COMPOSER=track one composercue_track01_DATE=track one datecue_track01_DISCNUMBER=track one disc numbercue_track01_GENRE=track one genrecue_track01_PERFORMER=track one performercue_track02_ALBUM=track two albumcue_track02_ALBUM ARTIST=track two album artistcue_track02_artist=track two artistcue_track02_COMMENT=comments for track twocue_track02_COMPOSER=track two composercue_track02_DATE=track two datecue_track02_DISCNUMBER=999cue_track02_GENRE=track two genrecue_track02_PERFORMER=track two performercue_track02_TOTALDISCS=track two disccue_track03_ALBUM=track three albumcue_track03_ALBUM ARTIST=track three album artistcue_track03_ARTIST=track three artistcue_track03_COMMENT=track three commentscue_track03_COMPOSER=track three composercue_track03_DATE=track three datecue_track03_DISCNUMBER=track three disc numbercue_track03_GENRE=track three genrecue_track03_PERFORMER=track three performercue_track03_TOTALDISCS=track three total discscuesheet=FILE "CDImage.wav" WAVE

"vorbis comments" is the tagging format used in FLAC files, I wasn't talking about Ogg files (vorbis comments are used there as well though).

oh... right.

Quote

Why do you think it's better to read the cuesheet tag? The FLAC specification seems to be encouraging the use of the CUESHEET block along with tags like the cue_trackNN* tags foobar is adding.

I think it's better to read the cuesheet tag solely because that's what foobar does. But in the name of compliance, it's probably better to read the cuesheet block.

Just thinking about it again, I think that reading the cuesheet tag is easier because it uses the min:sec:frames that all cuesheets use and thus can use the same cuesheet parser that the cuesheet file reader uses.

But I just looked at another cuesheet from the "--export-cuesheet-to=" option, and it says this:

Curiously, this one is in min:sec:frames, while the other one was in samples. I don't know why. Perhaps because the other one was 48khz sampling, and this one is 44.1khz (cd source). Wow, cuesheets are kind of crazy...

Quote

Also, do you know of any applications apart from foobar with support for FLACs with embedded cues?

"vorbis comments" is the tagging format used in FLAC files, I wasn't talking about Ogg files (vorbis comments are used there as well though).

oh... right.

Quote

Why do you think it's better to read the cuesheet tag? The FLAC specification seems to be encouraging the use of the CUESHEET block along with tags like the cue_trackNN* tags foobar is adding.

I think it's better to read the cuesheet tag solely because that's what foobar does. But in the name of compliance, it's probably better to read the cuesheet block.

Just thinking about it again, I think that reading the cuesheet tag is easier because it uses the min:sec:frames that all cuesheets use and thus can use the same cuesheet parser that the cuesheet file reader uses.

But I just looked at another cuesheet from the "--export-cuesheet-to=" option, and it says this:

Curiously, this one is in min:sec:frames, while the other one was in samples. I don't know why. Perhaps because the other one was 48khz sampling, and this one is 44.1khz (cd source). Wow, cuesheets are kind of crazy...

Quote

Also, do you know of any applications apart from foobar with support for FLACs with embedded cues?

Well, Cuesheets were initially created only for CD burning layout. I never seen them Cuesheet tags in a FLAC file but I know the standard is that metadata block that specifies samples & no artist/title/composer.