On Mon, 2002-07-01 at 04:03, Chris Holt wrote:
> Hello, Raider,
Hi Chris...
Here is my test list:
track02.orig.wav - unmodified
track02.r3mix.wav - --r3mix
track02.standard.wav - --alt-preset standard
track02.extreme.wav - --alt-preset extreme
track02.insane.wav - --alt-preset insane
track02.128k.wav - 128k cbr (--preset tape)
track02.160k.wav - 160k cbr (--preset hifi)
track02.192k.wav - 192k cbr (--preset cd)
track02.256k.wav - 256k cbr (--preset studio)
track02.320k.wav - 320k cbr (-b 320)
track02.abr128.wav - 128k abr
track02.abr160.wav - 160k abr
track02.abr192.wav - 192k abr
track02.abr256.wav - 256k abr
track02.abr320.wav - 320k abr
track02.vbr1.wav - --vbr-new -V 4 -q 2
track02.vbr2.wav - --vbr-new -V 1 -q 2
track02.vbr3.wav - --vbr-new -V 4 -q 0
track02.vbr4.wav - --vbr-new -V 4 -q 5
track02.vbr5.wav - --vbr-new -V 7 -q 2
track02.vbr6.wav - --vbr-old -V 4 -q 2
track02.vbr7.wav - --vbr-old -V 1 -q 2
track02.vbr8.wav - --vbr-old -V 4 -q 0
track02.vbr9.wav - --vbr-old -V 4 -q 5
track02.vbr10.wav - --vbr-old -V 7 -q 2
I know I should have put that in my first mail. :(
> Sorry, you never mentioned bitrate and you said "I'm not very good with this", so I
>was addressing things that I thought you may not have taken into account..
Just because I know on the surface how lame works doesn't mean I have
the slightest idea of what is going on with my sound. I'm working on an
empirical level - rip, encode, decode, burn - listen and compare the two
versions. And to be frank I was surprised to find out that all but the
not encoded (and than decoded) version had that dinamics problem.
> Okay, as for LAME, there are a bewildering number of options, and I suspect that
>unless you started your tests sometime last fall you haven't gotten through all the
>possible incarnations yet. :)
You are right with this. But as you can see there are quite a lot of
versions with only a few test options. The initial wish was to find out
what's the best way to encode (I normally use --r3mix) and also to hear
the difference between 128k cbr and 224k for example.
> Perhaps you might get some good tips out of the r3mix site. http://www.r3mix.net
I don't see anything on the r3mix site related with this problem. Even
if it's extremely helpful and well organised... still, no hint.
> Not to mention, it's a hell of a lot easier than typing: "--nspsytune --vbr-mtrh
>-V1 -mj -h -b96 --lowpass 19.5 --athtype 3 --ns-sfb21 2 -Z --scale 0.98 -X0" :)
;-) True. But you can also set an alias for the shell... or make a
short script or even better - use a GUI front-end ;-)
Given the above list - which included the switches involved in encoding
the original wav (the decoding was like this 'lame -decode tune.mp3')
are there any other filters that are triggered by default?
signature.asc
Description: This is a digitally signed message part
