Back Forum Reply New

AGknot 2.26 audio conversion bug

im choose 96 VBR, AG coded to 84 VBR mp3
im choose 160 VBR, AG coded to 136 VBR mp3

It's normal for the post-processed VBR audio to be read lower than the setting.

but in 2.20 version if i choosed 160, AG coded how about 160

in 2.26 as though i choose 136 - not 160, however i choose 160(sorry my english  )

.

Hi! I've problems with audio conversion (ac3 -gt; mp3)... the voice is too low, while the ambient sound is good, what can I do?

Thanks, bye.

I am still using Autogk 2.20, not sure whether I should upgrade to 2.26 one, since it seem there are many problems arised. Anyone please help to clarify the question below?

Does the problem affect CBR audio also?
Does the quot;voice is too lowquot; problem exist?
Have the new v2.26 been improved in encoding speed?


Originally Posted by miniyoyoI am still using Autogk 2.20, not sure whether I should upgrade to 2.26 one, since it seem there are many problems arised. Anyone please help to clarify the question below?

Does the problem affect CBR audio also?
Does the quot;voice is too lowquot; problem exist?
Have the new v2.26 been improved in encoding speed?

Hi,

Does the problem affect CBR audio also? -gt; should not cause CBR means Constant Bit Rate; constant is just constant  
Does the quot;voice is too lowquot; problem exist? -gt;Dunno, you may want to try different settings in DGIndex/Audio for dynamic range control or normalisation
Have the new v2.26 been improved in encoding speed? -gt; yes for avi sources, see  2.25 release notes here: showthread.ph...221#post393221
Between the Dgindex 1.45 and avisynth 2.56 I believe the overall process speed is improved but no benchs done  

For mp3 VBR I just use 1 or 2 presets higher, exemple to get around 128 VBR I try 144 or 160 VBR
All this audio issues (improvements  ) are related to the lame 3.97B2, you can always go back to 3.96 if needed see post from henryho_hk above: showthread.ph...769#post761769

Did
¥
Back Forum Reply New