Because the default behaviour of most audio rippers is to append the ‘pregap’ or ‘preamble’ audio data to the previous track, where it really does not belong. I listen to a track, and then hear the band introduce the next track even though the next track is not in my playlist. The problem, however, occurs when not listening to the entire album. If I want to just hear the song, I can skip directly to it, however if I am listening to the entire album, I hear this ‘preamble’ in sequence as intended. Index 00 points to the start of this ‘preamble’, and Index 01 points to the start of the actual song. This audio data truly belongs at the beginning of the track, not at the end of the previous track. Often, the pre-gap contains actual audio data – the band engaging the audience, e.g. The issue I struggle with, however, is live albums. If you play track 1, in our example, then a completely different track from a different album, track 1 would include the 2 seconds of silence from the pregap of track 2. if you were to skip the CD directly to track 2, playback would commence from index 01 and the silence in the ‘pregap’ would be ignored.īecause this ‘pregap’ data is often silence, when splitting the CD into separate FLAC files, the ‘pregap’ audio data is most often appended to the previous track. When playing this ‘pregap’ data, a CD player would count up from -2, -1, 0 until Index 01 is reached and the song starts playing. for instance, if you listen to track 1, then leave the audio playing, after track 1 ends track 2 might start with a 2 second ‘pregap’ of silence at index 00 before the actual track starts at index 01. One use-case for these ‘pregaps’ is to add space between the songs. When listening to a CD, you would only hear this audio data when playing two contiguous tracks without interruption. Depending on how the CD was mastered, however, there can be an additional Index 00 that contains audio data before the track begins. The way the audio data is laid out on the CD, each track will have an Index 01 that points to the point in the audio stream where playback of the track should commence if you skip directly to the track. I’m not talking about gapless playback (I understand that Roon’s playback engine is gapless) – rather I’m talking about the audio data that exists between the end of the last track and the beginning of the next track. CUE files (and old-school CDs for that matter) that Roon cannot replicate with a list of FLACs, and that has to do with handling “gaps”. We may add support for CUE files in the future, as a way to support Roon members that have data in this legacy format, but if we do, it would result in reduced functionality as the format is not as flexible as our feature set I think there is still one key advantage to. We feel that CUE files are an obsolete piece of technology, and that there are better more flexible ways to store your content with no loss in quality, assuming the software handles the playback properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |