azid auto find maximum gain fails?

[Mentar]

I've found out that the auto find maximum gain function, which works fairly reliable in the azidgui package, fails dramatically in GK. I have constant overflows by more than 3db .. and this is definitely noticeable.

I mean, of course I can do the whole sound part by hand, but .. could someone please look into this? Other than that GK is _so_ amazing - if this part could somehow be fixed, it would look like the perfect "fire and forget" tool for me ...

Thanks in advance :)

[MaTTeR]

I'd suggest you get familiar with Azid's command line functions. Gknot provides an expert command line in the audio tab for your own command such as gain.

[Snike42]

It would be a nice feature if Gknot would allow to enter a normalisation level or percentage instead of normalizing at 100%

This would allow to prevent problems with clipping (which can also happen during the mp3 encoding). You could just normalize at 95% and have a safety margin of 5%

Snike

[The FX Files]

If you normalize at 100% there's no clipping, since 100% is 0dB!!!

[Snike42]

If AZID would do this correctly then there would'nt be a problem in the first place. But this is not the case and sometimes overflows occur when AZID is fed with the gain (negative overflow value) found in the first pass.

Anyway something like a 'max-gain-offset' in Gknot would be very welcome. For menu's and directors commentary tracks I never normalize at 100% since this is much to loud.

Snike

[Snike42]

If AZID would do this correctly then there would'nt be a problem in the first place. But this is not the case and sometimes overflows occur when AZID is fed with the gain (negative overflow value) found in the first pass.

Anyway something like a 'max-gain-offset' in Gknot would be very welcome. For menu's and directors commentary tracks I never normalize at 100% since this is much to loud.

Snike