-V n (in 3.95.1), Presets, bitrates and lowpass of V value Options

[Vietwoojagig]

Hi,

CODE

Switch            equals               target  Y  b  lowpass resample
-V 0            = --preset extreme       240     128  19500
-V 0 --vbr-new  = --preset fast extreme  240     128  19500
-V 1                                     210     128  19000
-V 1 --vbr-new                           210     128  19000
-V 2            = --preset standard      190     128  19000
-V 2 --vbr-new  = --preset fast standard    190     128  19000
-V 3                                     175   1      18000
-V 3 --vbr-new                           175   1      18000
-V 4            = --preset medium        165   1      18000
-V 4 --vbr-new  = --preset fast medium   165   1      18000
-V 5                                     130   1      17000
-V 5 --vbr-new                           130   1      17000
-V 6                                     115   1      16000
-V 6 --vbr-new                           115   1      16000
-V 7                                     100   1      14900   32000
-V 7 --vbr-new                           100   1      14900   32000
-V 8                                      85   1      12500   32000
-V 8 - vbr-new                            85   1      12500   32000
-V 9                                      65   1      10000   24000
-V 9 - vbr-new                            65   1      10000   24000

Questions:
1. Is it save to use the -V switches, with no corresponding preset (especially V 1 / V3)?
2. When is it more usefull, to use abr rather than -V n (e.g. --preset 120 better than -V 5)?
3. Are the displayed target average bitrates ok (+/- 10 kbps)?

Thanks

Edit: changed with Gabriel's suggestions. Added:-Y, -b, --lowpass, --resample
Edit: modified -b to fit with 3.96

[ThyBzi]

Thanx for your support, people

But, as far as I understood, ABX test is based on "blind" listening to audio, but my acoustic system (and perhaps my ears ))) is not ideal, so in future (when I purchase a better one) I could regret my choise made now. Are there any less subjective, MORE objective test? Which can reveal the real (no only heared) differences between two soundtracks?

My father offered my to "subtract" original signal from the encoded->decoded one, and then to estimate the "difference signal" remained. Is this method good, how do you think? Are there any software to do that? AFAIK, Sound Forge and CoolEdit can't...

Or may be some graphic tests?

And one more question. You say spectral analysis couldn't be objective in this way. But if it shows some evident distortions, collapses etc - could they NOT be real distortions of sound and its quality? Especially if they aren't above 20 KHz, but within 16-20 KHz interval?

(Of course, I agree that even identical graphs do not obligatory mean identical sound, or sound of identical quality.)

P.S. By the way, I did't understand from the FAQ, what does -vbr-new key?

P.P.S. Joint Stereo "pushes together" channels, when they spead stronger than in "regular song"... Am I wrong? Does Stereo mode produce better quality? Does it increase filesize considerably?

This post has been edited by ThyBzi: Nov 30 2006, 19:36