>But.... how much gain do you have to give ?
you can do -oo to +10 dB (nominal - unchanged - gain by default)
>Is there a way like OTA's -g max ??
You mean normalize?
Im afraid thats impossible to normalise a signal in
a live (streaming situation) unless someone invents crystal-ball VST,
as an audio signal normalizing algorithm must
1)first scan the audio signal entirely
2)remember the highest (peak) value it encountered
3)find a gain value x so that high val = max
4)apply gain x to whole file
none of which can be done in a live streaming app, like this.
(but are easily done in offline sound editors)
Engineers use Dynamics Compressors in realtime
(with which they can use to prevent sudden unexpected peaks),
but these, well change the source dynamics.. so you might not want that here.
The best way would be with trial and error, run a couple of source
files and find a gain setting that doesnt clip the signal.
(this plugin might help:
http://www.pspaudioware.com/plugins/vmeter.html)
Our audio file player extracts the file at nominal volume, and
audio files have a max "normalized" value they can support
(well the 32 bit float can go beyond that and represent signal
out of the normalised [-1;1] range, but i dont want to get too techy again), So im sure there is a propper gain setting, but the overall gain setting might be influenced by the settings of any of the other plugins in the chain.
>Adobe Audition = Coold Edit Pro 2.1 (They bought the program.)
Yeah, youre right, my plogue collegue just told me.
>But it does a good job !!!!
Hey thanx!
>The value on the bottom of the screen gives sometimes strange results....
>i don't know what really happens then, or if it's a bug somewhere in the "memory and cpu management".
>load a module and use it...... cpu : 2.6 %
>reload the module, do some modifications (other file names)
>: cpu 80 % and once even 105.67 % > hard reset to be able to work again....
it can be many things, pentium 4 denormalisation bug in (any) VST,
I/O disk thread code having problems (bidule bug).
Or something else weve never encountered before.
If you can find specific steps to reproduce these errors, we would glady
try to fix them.