Yog Sothoth schrieb am Fre, 29 Sep 2000:
>
> hi -- This is my first post to the list. I've been
> helping myself to the cvs source code for a few months now and this is a
> subject I have done some experimentation with.
>
> the only drawback I've found when using --nspsytune in vbr mode is that
> the average bitrate may increase somewhat dramatically. In one of my test
> cases (10 second clip) the avegare bitrate is 290 with --nspsytune vs 210
> without it.
>
> lame version is 3.87 beta 1, options used were
> -b 128 -h -m j -q 1 -V 1 [--nspsytune]
>
> anyone interested in the clip can mail me. I have a small collection of
> 10 second clips that produce similar results. I also have samples which
> produce smaller average bitrates with --nspsytune.
>
> from now on I usually take some 30 seconds of source material and encode
> it both with and without --nspsytune to determine which will produce the
> smallest average bitrate before encoding the whole project.
This is a not so good idea. Take for example vbrtest.wav from
LAME's homepage. Encode it with and without --nspsytune. Following
your logic you would not using --nspsytune, but it was specially
tuned to make this one good sounding, needing more bits.
If you want some example where --nspsytune hurts, you can get
spahm.wav there too.
> in cbr mode I prefer to use --nspsytune at all times. for the same
> reason naoki shibata and others have mentioned.
>
> On Fri, Sep 29, 2000 at 01:09:16PM +0900, Naoki Shibata wrote:
> > I've asked some people to evaluate --nspsytune, and most of their
> > response were positive ones.
> >
> > In VBR mode, --nspsytune usually improves sound quality with high
> > tonality like piano and tambourin but sometimes degrades sound with low
> > tonality like snare drums.
> >
> > In CBR mode, --nspsytune lowers artifacts in high frequency.
>
> --
> Michael Horan III
Ciao Robert
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
