PDA

View Full Version : Ripping Yarn



2004-08-04, 19:49
>
> I have a question about ripping.... I have ripped it using EAC, but
that
> gives distinct tracks with an intertrack gap when played.
>
> Is there a way to do it so that it is played contiguously on the
> slimp3/squeeze?

This is not a problem with EAC so much, although you might need to dig
into its calibration system.

EAC can write a wav file per track and these wav files can be
concatenated to form a seamless audio stream. There is no added gap,
however you might need an option to be set, but I always run it that
way.

The problem is mainly with the mp3 encoding (and possibly other encoding
schemes). The Lame faq discusses this.

Newer versions of Lame implement "gapless" encoding, but it requires you
to encode manually. This is because EAC passes individual files to the
encoder, but gapless encoding requires Lame to peek at adjacent wav
files. So you have to pass all the files in sequence to Lame. It is
supposedly not quite perfect, but seems OK to me. SB and Winamp play
them seamlessly.

If you rarely select individual tracks just encode as a single file. I
tried this with cuesheets, but because I use vbr they don't work very
well either.

Cameron.

Jason Holtzapple
2004-08-05, 07:01
Cameron.Davidson (AT) csiro (DOT) au wrote:
>>I have a question about ripping.... I have ripped it using EAC, but
>
> that
>
>>gives distinct tracks with an intertrack gap when played.
>>
>>Is there a way to do it so that it is played contiguously on the
>>slimp3/squeeze?
> ...
> The problem is mainly with the mp3 encoding (and possibly other encoding
> schemes). The Lame faq discusses this.
>
> Newer versions of Lame implement "gapless" encoding, but it requires you
> to encode manually. This is because EAC passes individual files to the
> encoder, but gapless encoding requires Lame to peek at adjacent wav
> files. So you have to pass all the files in sequence to Lame. It is
> supposedly not quite perfect, but seems OK to me. SB and Winamp play
> them seamlessly.

I don't think this is the case any more. There used to be an old
--nogap option that behaved the way you described. lame 3.90.3 and
later write the actual size in bytes of the lame header+music portion
of the mp3 into the lame header (MusicLength). A decoder can read this
value and use it to achieve gapless playback. However not many
decoders support this (foobar2000 is one that I know off-hand).

Most formats designed after mp3 have better gapless support.

--Jason

Larry Truesdale
2004-08-05, 09:08
FYI: the decoder in the Rio Karma also does this.

Larry

On Thu, 05 Aug 2004 07:01:46 -0700, Jason Holtzapple
<jasonholtzapple (AT) yahoo (DOT) com> wrote:
> Cameron.Davidson (AT) csiro (DOT) au wrote:
> >>I have a question about ripping.... I have ripped it using EAC, but
> >
> > that
> >
> >>gives distinct tracks with an intertrack gap when played.
> >>
> >>Is there a way to do it so that it is played contiguously on the
> >>slimp3/squeeze?
> > ...
> > The problem is mainly with the mp3 encoding (and possibly other encoding
> > schemes). The Lame faq discusses this.
> >
> > Newer versions of Lame implement "gapless" encoding, but it requires you
> > to encode manually. This is because EAC passes individual files to the
> > encoder, but gapless encoding requires Lame to peek at adjacent wav
> > files. So you have to pass all the files in sequence to Lame. It is
> > supposedly not quite perfect, but seems OK to me. SB and Winamp play
> > them seamlessly.
>
> I don't think this is the case any more. There used to be an old
> --nogap option that behaved the way you described. lame 3.90.3 and
> later write the actual size in bytes of the lame header+music portion
> of the mp3 into the lame header (MusicLength). A decoder can read this
> value and use it to achieve gapless playback. However not many
> decoders support this (foobar2000 is one that I know off-hand).
>
> Most formats designed after mp3 have better gapless support.
>
> --Jason
>
>
>