YAYDaveGamble wrote:InevitablyDr.Gunjah wrote:... which inevitably leads to the question: Can we expect a highly versatile dmgaudio saturation processor in the future?DaveGamble wrote:2) Saturation and the like from overdriving the signalpath (valve units, solid state stuff clipping, etc)ChinmayL wrote:Does COMPassion model the harmonics or saturation added by other compressors? For example, I believe Waves Studio Classics / CLA, Softube's FET and CL1B, The Glue, etc. all model the behavior but also the sound of the compressor (harmonics, etc.). Is this what the Mods do in COMPassion or is it more like the compressor models in Logic's stock compressor? I'm having a hard time getting COMPassion to sound similar to the others...(I bring this up because I've seen people say COMPassion has replaced their other compressors).
2) No.
hmm... I will have to test if this is good or bad news.canDo("Bypass") wasn't implemented. No linkage between VST2 Bypass API call and internal bypass mech. Now it is linked.And another question about this:what was wrong here?Fix: VST2 bypass
When bypassing Compassion 1.0 latency was untouched. Has this changed now? (please... no
)edit: sorry, I was mistaken about this. The behaviour is equal to the bypass in Equality(no matter which version). When having latency (for example with large lookahead) pushing the bypass button introduces crackles in the sound which is unpleasing when doing A/B comparisons.
It would be cool if you could make a preference for this, something like "keep latency on bypass (yes/no)". If people want to get rid off the latency there is still the host bypass.
Ah ok, got it. thanks!If A-R is not coupled, there are two separate circuits for Attack and Release, the order of which can be changed with the AR Order control (Attack first or Release first). Almost all AR-decoupled circuits use a low-pass filter for the Attack circuit (which, naturally, causes an interaction with the release shape). With the Attack Type control, you can blend between the Attack circuit being a filter and being an actual attack filter (with instantaneous release).
While reading the manual there came across another question (sorry
):What is the difference between "Output Trim" in the global settings and "Drive" on the Clip Limiter?
If I understood correctly, the Clip Limiter is behind the dry/wet mixer so both "Drive" and "Output Trim" seem to be redundant (except for the Drive control only being active when Clip Limiter is engaged...?)
edit: the more I think about, the more it seems to me that placing output trim behind the clip limiter (at the very end of the chain?) makes more sense.
People will unlikely use it when configuring the clip limiter because there is "Drive" - though having the output trim behind the clipper then would provide the possibility to change the global output of the plugin.
With clip limiter off people won't even care if Output Trim is before or behind it.
Maybe I'm still missing a fact here
and another edit:
Finally had time to really test 1.02 now.
Good update so far
Mousewheel on advanced parameters works fine.
The graph on 20%/10% speed is far better, but the hard green/red contrast is still quite punishing for the eye (can anyone confirm this? maybe it's just my screen). Additionally, now that I can actually see the graph, I find it still not that useful. Especially the waveform doesn't really help at setting up the comp but eats up the most space. The attack and release graphics at top and bottom (is this for L/R?) are generally a good idea, but they are too small, especially at low GR values. It's ok for a very raw indication of compression activity, but compared to the GR display in Pro-C (sorry for another comparison to Fabfilter
) it lacks "visual precision".Last but not least.. what does the new Parallel split mode exactly? (does it compress the 2 bands independently?)
Cheers,
Doc
