HydrogenAudio

Lossy Audio Compression => Ogg Vorbis => Ogg Vorbis - General => Topic started by: ani_Jackal3 on 2020-10-21 13:34:12

Title: Libvorbis 1.3.7 vs AoTuv B6.03
Post by: ani_Jackal3 on 2020-10-21 13:34:12
Are they both the same?, or is AoTuv gains so minimal that it not worth it?. Noticed that latest 192kbps blind test didn't try libvorbis only just the latest AoTuv.
Title: Re: Libvorbis 1.3.7 vs AoTuv B6.03
Post by: punkrockdude on 2020-10-24 10:52:46
Using aotuv I really liked using the advanced options to my likings.
Title: Re: Libvorbis 1.3.7 vs AoTuv B6.03
Post by: ani_Jackal3 on 2020-10-25 07:21:41
Using aotuv I really liked using the advanced options to my likings.

Is there a list of them?, Yeah i like how the bit rate will boost on complex stuff if only they did with puffy artifact. Since some songs need Q 9.2 to sound transparent but at least i can have 99.5% at 160kbps no problem.
Title: Re: Libvorbis 1.3.7 vs AoTuv B6.03
Post by: punkrockdude on 2020-10-26 10:38:10
I tried the following that did or I imagined made a difference to transients:

-q 3 --advanced-encode-option impulse_noisetune=-15 --advanced-encode-option bit_reservoir_bias=0 --advanced-encode-option bit_reservoir_bits=4 --advanced-encode-option bitrate_average_damping=0.1

Title: Re: Libvorbis 1.3.7 vs AoTuv B6.03
Post by: john33 on 2020-10-26 14:04:29
Those options are exposed in oggdropXPd. :)
Title: Re: Libvorbis 1.3.7 vs AoTuv B6.03
Post by: m14u on 2020-10-26 14:28:22
-q 3 [...] --advanced-encode-option bit_reservoir_bits=4 [...]
"bit_reservoir_bits=N
              [...]  This option must be  used
              with  --managed  to have any effect and affects only minimum and
              maximum bitrate management.  Average bitrate  encoding  with  no
              hard bitrate boundaries does not use a bit reservoir."
Title: Re: Libvorbis 1.3.7 vs AoTuv B6.03
Post by: punkrockdude on 2020-10-30 07:27:07
m14u,
Thank you for the clarification on that parameter.