Displaying 4 results from an estimated 4 matches for "s10s".
Did you mean:
10s
2004 Sep 10
2
[Flac-users] Re: questions about 1.1.0 release
...in the stream that can
| be seeked to, they are just hints about regular locations in
| the stream. you can still seek to any sample. the number of
| seekpoints are just one factor in determining how fast the
| decoder can find any particular sample. I did a lot of testing
| before deciding on -S10s.
So you can seek anywhere, but if it isn't on a stored seekpoint, the
calculation will be interpolated between the preceding and following
seekpoints? I'll have to try it and see what happens. Come to think of it,
what bugs me about Winamp's seeking through APEs is not so much the pr...
2004 Sep 10
2
[Flac-users] questions about 1.1.0 release
...ile puzzle me, so I've not tried to use it yet.
Pardon my denseness here ...
First, as long as you don't use the --cuesheet option when you encode, are
.flac files encoded by 1.1.0 still readable by earlier versions?
Second, if the old default for seekpoints was -S100x and the new one is -S10s,
does that mean that, if you encode a 44.1-ksps WAV that was ripped from a CD,
the old default was to set 441 seekpoints per second and the new one is to set
one seekpoint every ten seconds?
One of the major reasons I preferred FLAC to APE, despite APE's usually
tighter compression, was that i...
2004 Sep 10
0
[Flac-users] questions about 1.1.0 release
...uot; <dattier@panix.com> wrote:
> First, as long as you don't use the --cuesheet option when you
> encode, are
> .flac files encoded by 1.1.0 still readable by earlier versions?
that's right.
> Second, if the old default for seekpoints was -S100x and the new one
> is -S10s,
> does that mean that, if you encode a 44.1-ksps WAV that was ripped
> from a CD,
> the old default was to set 441 seekpoints per second and the new one
> is to set
> one seekpoint every ten seconds?
no, -S100x meant 100 seekpoints per stream, regardless of the
length. a three min...
2004 Sep 10
0
[Flac-users] Re: questions about 1.1.0 release
...gt; | be seeked to, they are just hints about regular locations in
> | the stream. you can still seek to any sample. the number of
> | seekpoints are just one factor in determining how fast the
> | decoder can find any particular sample. I did a lot of testing
> | before deciding on -S10s.
>
> So you can seek anywhere, but if it isn't on a stored seekpoint, the
> calculation will be interpolated between the preceding and following
> seekpoints? I'll have to try it and see what happens.
no. the decoder uses the seekpoints to estimate where in the
stream to sta...