simple peak limiting
hello!
50 different signals hit my DAC, varying in "loudness".. (due to movement, jitter project) I've tried using [omx.peaklim~] to limit the final peak (comparable to ableton's limiter), but am having my difficulties - my sound still breaks off after a short while.
is there any other way for simple peak limiting? (merely keeping my "master" peak below 1)
cheers!
-jonas
Simplest way I know of would be to patch in a [tanh~] right before the dac. Rather than limiting, that would give you soft-clipping.
Maybe you just have the attack time too long on [omx.peaklim~] and it's letting stray peaks through?
I think you'll get better results if you use [vst~] and a good limiter like Voxengo Elephant...etc...etc........you would get much better sound quality that way, at the expense of a little more cpu hit.
Also, have you used poly~ before? That tiff is frightening! :)
thanks for all the info, tim! I'll also have a look at [poly~], always was a bit afraid of this "little" fella... :)
all the best!
-jonas
hm, very weird... I've tried all you've suggested, but sound keeps breaking off. although with [tanh~] it does take a while...
how do you know, that the signal is actually breaking off ?
meter~, for example, will flash the red "over" LED, if the signal's (smoothed) amplitude is greater or _equal_ to 1.0 !
maybe a simple [*~ 0.8] (-2dB) after limiting/soft-clipping will help...
you could also use [peakamp~] to see what's the signal's (sample) maximum.
Could you post an audio clip? I'm not sure what you mean by "breaking off".
Do you always have 50 audio signals hitting the dac~ at the same time? If so, then then you really have to scale each audio signal/the sum accordingly, rather than just trying to catch peaks.
I'm sorry, everything's ok with my peaks. the problem is caused by [groove~] - which apparently wouldn't accept my loop commands (hence stopping after my sample reached its end).. why it does this I'll have to check on now.. still glad it's not a peak brainteaser anymore
thanks for your time..!
all the best
-j
yeah, groove~ sometimes behaves weird with loop-points..
In my experience, the safest method is to use messages only and leave the loop point inlets unconnected:
"setloop 0. 500. , startloop"
easy question:
can anyone explain me the values of the right most outlet of omx please?
they go from -5 to 250.
i know that it is just a kind of scaling and -5 is max limitation and 250 is no limitiation...but why do u choose these numbers? why not (to be stupid) 400 and 30000 ?
Thanx
Peer
"hm, very weird... I've tried all you've suggested, but sound keeps breaking off. although with [tanh~] it does take a while..."
tanh wont do much unless you also do /pi
lol @ tiff