Thanks
Compressive Update
- KVRist
- 490 posts since 21 Jun, 2002 from Hamburg
a little bit OT, but what happened to Chordme? I lost it after a crash and couldn't find it anymore. Missing it!
aka rktic. demoscener (Farbrausch, Holon, MFX, Still), sound designer, ux-dude, sth @AudioRealism, human synthesizer—not necessarily in that order.
- KVRAF
- 25049 posts since 12 Jul, 2003 from West Caprazumia
Thnaks a lot for the update!

-
- KVRian
- Topic Starter
- 995 posts since 25 Apr, 2005
Thanks for the kind words bduffy, I'm glad you like itbduffy wrote:Freakin' excellent so far. I don't recall a lot of CPU-use in the previous version, but seems quite low now. The only comment I can think of right now is that the sidechain monitor is loud as hell; when I have a significant boost it nearly blows my head off!Caco wrote:Ah it sounds like wavelab can't deal with plugins that have more than one stereo input then. Good to see Steinberg fully supporting the VST specST54 wrote:I tricked myself
The 'lite' version is/was OK with WL5/6.Same behaviour as the previous version.(was a long time I tried that)
Only the pro version doesn't do it in the mastersection of WL.
Possibly something to do with the 'external input/aux' capabilities.
Some error about "not supporting the number of channels".
You can use them both in the WL montage.
Anyway thx for the update ....esp. the ratio knob
S.
@S-N-S - glad to hear it's working![]()
@bduffy - let me know what you think, I'd be interested to hear any feedback you have![]()
Sounds great, though: I'm getting a really slamming drum bus right now, using the sidechain to compress the kick and snare and leave let the lows and highs through; very nice. Hard to think of any compressor sounding better; this is top-notch stuff, my friend.
Thanks Jens - have you found the CPU lower for the sidechain?
- KVRAF
- 25049 posts since 12 Jul, 2003 from West Caprazumia
Yes, I have indeed - and quite significantly!
Just one minor niggle: the ratio-value is still the wrong way around.
Just one minor niggle: the ratio-value is still the wrong way around.
- KVRAF
- 25049 posts since 12 Jul, 2003 from West Caprazumia
Oh, I just noticed another problem which I didn't see before:
I don't know if this is caused by denormals, but when there's no input, the cpu-usage approximately tripples on my AthlonXP.
Putting Digitalfishphones' Normalizer before it fixes the problem.
I don't know if this is caused by denormals, but when there's no input, the cpu-usage approximately tripples on my AthlonXP.
Putting Digitalfishphones' Normalizer before it fixes the problem.
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
I haven't been able to recreate any denorm problems over here (Intel P4), but I did notice that the output level graphic jumps "outside" of its container.''
Also: have you ever considered putting an input level meter on Compressive?
Also: have you ever considered putting an input level meter on Compressive?
- KVRAF
- 25049 posts since 12 Jul, 2003 from West Caprazumia
I made some experiments now:
it's the sidechain - at least one band must have a value other than 0db and the sidechain must have been fed with a signal once. The signal of the Normalizer plugin is enough to trigger it (-608db).
The cpu consumption slightly depends on the value of the sidechain-band (it doesn't seem to matter though whether it's a boost or a cut) and with the high band the effect is significantly less drastic than with the medium and the low band (which are both about the same).
it's the sidechain - at least one band must have a value other than 0db and the sidechain must have been fed with a signal once. The signal of the Normalizer plugin is enough to trigger it (-608db).
The cpu consumption slightly depends on the value of the sidechain-band (it doesn't seem to matter though whether it's a boost or a cut) and with the high band the effect is significantly less drastic than with the medium and the low band (which are both about the same).
-
- KVRian
- Topic Starter
- 995 posts since 25 Apr, 2005
Cool, thanks Jens will look into it.jens wrote:I made some experiments now:
it's the sidechain - at least one band must have a value other than 0db and the sidechain must have been fed with a signal once. The signal of the Normalizer plugin is enough to trigger it (-608db).
The cpu consumption slightly depends on the value of the sidechain-band (it doesn't seem to matter though whether it's a boost or a cut) and with the high band the effect is significantly less drastic than with the medium and the low band (which are both about the same).
- KVRAF
- 25049 posts since 12 Jul, 2003 from West Caprazumia
Great, thanks! 
-
- KVRian
- Topic Starter
- 995 posts since 25 Apr, 2005
yep, I had noticed that as well and I have added it to my todo list to fix. I had been thinking about meters recently and whether I can fit one on there without having to redo the GUI. I an not sure if or when but it would be nice to have input/output and gain reduction meters.bduffy wrote:I haven't been able to recreate any denorm problems over here (Intel P4), but I did notice that the output level graphic jumps "outside" of its container.''
Also: have you ever considered putting an input level meter on Compressive?
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
Cool! I love Input/Output/GR meters...Caco wrote:yep, I had noticed that as well and I have added it to my todo list to fix. I had been thinking about meters recently and whether I can fit one on there without having to redo the GUI. I an not sure if or when but it would be nice to have input/output and gain reduction meters.bduffy wrote:I haven't been able to recreate any denorm problems over here (Intel P4), but I did notice that the output level graphic jumps "outside" of its container.''
Also: have you ever considered putting an input level meter on Compressive?
Looking at the GUI now, I kind of expect to see an input meter on the left, where you have almost precisely the right amount of space for them; gain reduction...yeah, that could be a problem. If you shifted all the knobs over a few pixels, you could free up some room on the right to at least get a numerical readout in, perhaps...

