Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Embedding CUESheet into FLAC images using EAC/REACT2 (Read 5297 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Embedding CUESheet into FLAC images using EAC/REACT2

Hello everyone.

I have just finished ripping my CD collection into FLAC images using REACT2 and EAC. Thanks once again to the developers for the excellent programs.

After doing so, I noticed that REACT2 embeds CUESheets into the FLAC images as a vorbis comment rather than a native FLAC metadata block. While I am not cribbing about this, I am curious to know why this is done this way. Are there any disadvantages to embedding CUESheets as a FLAC metadata block?

The reason I ask is that while most apps recognize the vorbis "cuesheet" comment and process the data properly, isn't it better to make use of FLAC's native tagging features? Won't this improve compatibility with DAPS and music playback software that don't know about the vorbis 'cuesheet' comment?

Please shed some light on this.

Thanks.

Embedding CUESheet into FLAC images using EAC/REACT2

Reply #1
I think this post is still relevant:

http://www.hydrogenaudio.org/forums/index....st&p=371680

I don't use FLAC but it seems that most people use a Vorbis comment, because the CUESHEET metadata block will strip out meta data.

Of course, you can easily edit your REACT-image.cfg file to use whichever method you see fit - even using both methods.
I'm on a horse.

Embedding CUESheet into FLAC images using EAC/REACT2

Reply #2
Thanks Synthetic Soul!!

I won't worry too much about this any more, and will stick with the vorbis comments.

Embedding CUESheet into FLAC images using EAC/REACT2

Reply #3
I think that foobar2000 does the same, but I'd problems when trying to play the resulting flac file in amarok, I had to import the cuesheet manually to the metadata block with metaflac to being able to play the file with amarok, also I think that not embedding the cuesheet directly to the metadata block doesn't produces the SEEKTABLE

 

Embedding CUESheet into FLAC images using EAC/REACT2

Reply #4
No, I don't suppose that you would get the seekpoints.  The Cuesheet Vorbis comment is just another tag as far as FLAC is concerned.

If I used FLAC I would be tempted to use both methods, as it's only an extra 3KB or so.  However I seem to remember one member having problems with that.  If you ensure that the cuesheet is correct before embedding, so you don't end up having to edit it later down the line, then I'm not sure how it could cause a problem, but I've never tested.
I'm on a horse.

Embedding CUESheet into FLAC images using EAC/REACT2

Reply #5
I think that foobar2000 does the same, but I'd problems when trying to play the resulting flac file in amarok, I had to import the cuesheet manually to the metadata block with metaflac to being able to play the file with amarok, also I think that not embedding the cuesheet directly to the metadata block doesn't produces the SEEKTABLE


I am quite surprised... The default EAC/REACT2 configuration creates FLAC images with SEEKPOINTS. Embedding a CUESheet as a FLAC tag adds a metadata block that looks something like this:

Code: [Select]
METADATA block #4
  type: 5 (CUESHEET)
  is last: false
  length: 816
  media catalog number:
  lead-in: 88200
  is CD: true
  number of tracks: 9
    track[0]
      offset: 0
      number: 1
      ISRC:
      type: AUDIO
      pre-emphasis: false
      number of index points: 1
        index[0]
          offset: 0
          number: 1
    track[1]
      offset: 13438740
      number: 2
      ISRC:
      type: AUDIO
      pre-emphasis: false
      number of index points: 1
        index[0]
          offset: 0
          number: 1
    track[2]
      offset: 26750472
      number: 3
      ISRC:
      type: AUDIO
      pre-emphasis: false
      number of index points: 1
        index[0]
          offset: 0
          number: 1
    track[3]
      offset: 41426952
      number: 4
      ISRC:
      type: AUDIO
      pre-emphasis: false
      number of index points: 1
        index[0]
          offset: 0
          number: 1
    track[4]
      offset: 51241848
      number: 5
      ISRC:
      type: AUDIO
      pre-emphasis: false
      number of index points: 1
        index[0]
          offset: 0
          number: 1
    track[5]
      offset: 61691784
      number: 6
      ISRC:
      type: AUDIO
      pre-emphasis: false
      number of index points: 1
        index[0]
          offset: 0
          number: 1
    track[6]
      offset: 78473304
      number: 7
      ISRC:
      type: AUDIO
      pre-emphasis: false
      number of index points: 1
        index[0]
          offset: 0
          number: 1
    track[7]
      offset: 92682912
      number: 8
      ISRC:
      type: AUDIO
      pre-emphasis: false
      number of index points: 1
        index[0]
          offset: 0
          number: 1
    track[8]
      offset: 108076752
      number: 170 (LEAD-OUT)

The artist's name, album name, etc. don't get written into these track, but this is a CUESheet, albeit in a different form. The SEEKTABLE looks something like this:
Code: [Select]
METADATA block #1
  type: 3 (SEEKTABLE)
  is last: false
  length: 4428
  seek points: 246
    point 0: sample_number=0, stream_offset=0, frame_samples=4096
    point 1: sample_number=438272, stream_offset=546863, frame_samples=4096
    point 2: sample_number=880640, stream_offset=1244667, frame_samples=4096
    point 3: sample_number=1318912, stream_offset=2395019, frame_samples=4096
    point 4: sample_number=1761280, stream_offset=3677475, frame_samples=4096
    point 5: sample_number=2203648, stream_offset=4979840, frame_samples=4096
    point 6: sample_number=2641920, stream_offset=6166030, frame_samples=4096
    point 7: sample_number=3084288, stream_offset=7441919, frame_samples=4096
    point 8: sample_number=3526656, stream_offset=8708518, frame_samples=4096
    point 9: sample_number=3964928, stream_offset=9953722, frame_samples=4096
    point 10: sample_number=4407296, stream_offset=11247823, frame_samples=4096
    point 11: sample_number=4849664, stream_offset=12511055, frame_samples=4096
.
.
.

Are you sure that you didn't get the SEEKPOINTS in the image?


Embedding CUESheet into FLAC images using EAC/REACT2

Reply #7
I'm getting more than a little confused.

My understanding (which could easily be wrong) is this:
  • The default REACT config sets a Vorbis comment called "cuesheet", using the --tag-from-file switch.  It does not set the native FLAC CUESHEET block.
  • The above behaviour will result in seekpoints in the file, but not specific to tracks, just the default 10 second intervals.
  • You need to use the --cuesheet switch to a. populate the FLAC CUESHEET block and b. create seek points at track index points.
For the record, this is the code in my config:

Code: [Select]
    @tools@\flac.exe @Opt_Flac@ %RG_Flac% %Cover_tag% %Disc_Flac% -T "%ArtistField%=@cdartist@" -T album="@album@" -T totaltracks="@numtracks@" -T date="@year@" -T genre="@genre@" -T comment="@comment@" -T encoded-by="%USERNAME%" -T encoding="Flac @Ver_Flac@ @Opt_Flac@" --tag-from-file="cuesheet=@cuesheet@" --tag-from-file="eaclog=@eaclog@" "@source@" -o "@image@"
I'm on a horse.

Embedding CUESheet into FLAC images using EAC/REACT2

Reply #8
Hi Synthetic Soul. I understand now. My default EAC/REACT2 setup produces FLACs with SEEKPOINTS alright, but the --cuesheet option adds additional SEEKPOINTS according to the specified CUESheet, which is stated quite clearly in the FLAC help message.

Sorry about the confusion caused.

Embedding CUESheet into FLAC images using EAC/REACT2

Reply #9
Hi everybody,

I just started to rip with React 2.0ssb16p and Accuraterip.
I keep the cuesheets generated by EAC.

Concerning those embedded ones, I coverted one of those flacimages
into a single wav/cuesheet with foobar and the cuesheet generated by foobar
was completely different from the EAC cuesheet.

Why are they different?
Is it possible to get the original index points out of the flacimage?
Should I keep the original cueheets then?

Thanks in advance,
Philipp

BTW: Thanks for the great work! I really appreciate it..