KVR Audio

silicon/silicium · Post by **silicon/silicium** » Tue Apr 25, 2006 1:24 pm

well, I can

first having a wet/dry on a comp was a bit strange for me.
then it takes me a moment to understand how down/up works (especially combined with expand/compress.

ok, now I find some decent settings, the main problem is lisibility, finding who does what, in wich direction you have to turn the know to have the desired effect. the threshold really lack of precision and the ration could go even further.
and I still don't know what cutoff do.

I have to say I m used to compressor, to traditionnal comperssor at least

but this one could be interesting, not as an academic compressor though

Kingston · Post by **Kingston** » Tue Apr 25, 2006 1:24 pm

the new version knobs are much more ergonomic.

The compressor works just fine, no bugs or anything. By flaky, I meant the sound itself. It seems like the compressor reacts to the audio in a really weird "flaky" way. Kind of clumsy and slow. I'll take a look at what's going on in a few days.

Weird how smooth it sounds, despite the odd sound. Also, the lookahead buffer control is cool. One can hear the buffer fluttering when moving the know. The flutter sounds quite smooth.

Might have to do a vinyl scracth buffer toy based on that.

silicon/silicium · Post by **silicon/silicium** » Tue Apr 25, 2006 1:26 pm

also latency is not correctly reported in energyXT.

-edit, b version threshold is far better
-with attack=0 I still have some microattack (need to turn ahead a bit to avoid that)
-instead of a wet dry knob, a simple bypass button could be enough (as on the eq)

silicon/silicium · Post by **silicon/silicium** » Tue Apr 25, 2006 1:33 pm

"Might have to do a vinyl scracth buffer toy based on that."

héhé, just thought the same two mins ago...

stefancrs · Post by **stefancrs** » Tue Apr 25, 2006 1:34 pm

The wet/dry was requested earlier on in this thread, I myself don't use it. You think it should be removed?

Regarding up/down and compress/expand, well, it isn't anywhere near a "one knob compressor", so I guess one either must know or must learn what the difference between up and down compression and expansion is to be able to tweak this effortlessly.

For "normal" compressor usage, just stay with downward compression (I usually prefer upward, but I'm a bit odd).

Two issues with reporting latency:
1) We haven't added support for it in synthmaker yet (but it'll come)
2) The latency is dynamic and even automatable, how is the host supposed to handle that?

stefancrs · Post by **stefancrs** » Tue Apr 25, 2006 1:36 pm

silicon/silicium wrote:also latency is not correctly reported in energyXT.

-edit, b version threshold is far better
-with attack=0 I still have some microattack (need to turn ahead a bit to avoid that)
-instead of a wet dry knob, a simple bypass button could be enough (as on the eq)

Letting attack/release go down all the way to zero is a bit "dangerous", not letting them go all the way down is a trade-off but I thought it was kindof worth it. Might have to reconsider it I guess

Kingston · Post by **Kingston** » Tue Apr 25, 2006 1:39 pm

stefancrs wrote:2) The latency is dynamic and even automatable, how is the host supposed to handle that?

The only solution that works everywhere today is to report one latency to the host(the highest that the plugin will use), and handle the actual parameter compensation within the plugin itself, while hosts sees a steady latency.

Unfortunate yes, but that's how it is with non-standard host behaviours.

Or play it risky and do dynamic latency reporting. Only some hosts will be able to work with that.

stefancrs · Post by **stefancrs** » Tue Apr 25, 2006 1:43 pm

Kingston wrote:
stefancrs wrote:2) The latency is dynamic and even automatable, how is the host supposed to handle that?
The only solution that works everywhere today is to report one latency to the host(the highest that the plugin will use), and handle the actual parameter compensation within the plugin itself, while hosts sees a steady latency.

Unfortunate yes, but that's how it is with non-standard host behaviours.

Or play it risky and do dynamic latency reporting. Only some hosts will be able to work with that.

We'll probably have two flavours of it then. One with PDC support and one without.

Kingston · Post by **Kingston** » Tue Apr 25, 2006 1:46 pm

Or give the user the option in the GUI (or setup page like it's usually done).

stefancrs · Post by **stefancrs** » Tue Apr 25, 2006 1:48 pm

Or that, yes

stefancrs · Post by **stefancrs** » Tue Apr 25, 2006 1:51 pm

silicon/silicium wrote:the ration could go even further.
and I still don't know what cutoff do.

Sorry, missed these two.
The ratio goes from 1:1 to inf:1 when compressing and 1:1 and 1:inf when expanding, isn't that enough?

The cutoff sets the cutoff frequency for the frequency band splitter, it is a two-band compressor after all. Where you want it usually depends on how you want the bass to behave in the compressor.

silicon/silicium · Post by **silicon/silicium** » Tue Apr 25, 2006 2:02 pm

The wet/dry was requested earlier on in this thread, I myself don't use it. You think it should be removed?

to me it's useless on a dynamic based effect, maybe I miss some application, but I never used compressor as send effect, so I can't see the point.

Regarding up/down and compress/expand, well, it isn't anywhere near a "one knob compressor", so I guess one either must know or must learn what the difference between up and down compression and expansion is to be able to tweak this effortlessly.

well, it's ok, I have some theorical knowledge about comps, I just had to find the way controls were linked to knowledge héhé.
so let's imagine giving this comp to someone who hadn't this experience.

Two issues with reporting latency:
1) We haven't added support for it in synthmaker yet (but it'll come)
2) The latency is dynamic and even automatable, how is the host supposed to handle that?

well energyXT can deal with dynamic latency reports each time the sequencer restart, so it could be enough to have our tracks in sync, even if automation is still problematic.

about attack=0, I know it's impossible (btw setting the attack to the lowest setting make some strange noises), but the current ramp let some attack be heard even if attack is set to low, and ratio to the max, making some ploc plic ploc plic plic ploc.

silicon/silicium · Post by **silicon/silicium** » Tue Apr 25, 2006 2:13 pm

ok, so hi/lo is a balance between the two outputs (low band and high band) and cutoff the crossover frequency isn't it??

C00kie · Post by **C00kie** » Tue Apr 25, 2006 2:16 pm

maybe I miss some application, but I never used compressor as send effect, so I can't see the point.

It's called "New York style compression" when dry is mixed with the compressed signal.
The "I feel lucky" google link: http://www.pizzamaking.com/lehmann_nystyle.php

stefancrs · Post by **stefancrs** » Tue Apr 25, 2006 2:16 pm

silicon/silicium wrote:ok, so hi/lo is a balance between the two outputs (low band and high band) and cutoff the crossover frequency isn't it??

Right on.

Free SynthMaker Compressor+EQ/Multi-stage distortion unit