it happens for particular sources only, in general it happens because differently from other compressors nebula control signal is NOT filtered at all (many compressors are using an highpass filters). We leave that freedom to you releasing the sidechained version of nebula.
In nebula2 and nebula3 you have wrong timings. Only nebula3 pro supports right envelope follower timings. So compression sounds differently.
It doesn't mean that nebula3 pro can handle compresson on low frequencies content better than nebula3 and nebula2.
For that you need to engage sidechaining with a proper filter, because it's physics: we don't sample which kind of spectrum the compressor is sensible of, all our compressors are sensible on the whole spectrum. So they "ring" if you have for example a bottom drum: original compressor unit maybe is reacting only to particular frequencies, not all of them.
I should say it doesn't happen frequently though, it happens if you are trying to compress a bottom drum or a bassline alone.
I'm explaining it because an user upgraded to nebula3 pro from nebula2 and asked for a refund. I hope it doesn't happen any more. We provide nebula3 free with a couple of compressors, and nebula3 free is based on CoreII. All of them are obviously ringing on a bottom drum alone if you are trying to process it.
Ok well that rings a weird sort of a bell. I just upgraded to pro3 & thought I was doing something wrong. Ive done a couple of clean installs before I read this. How do we download the sidechain version please? Steve
thanks for all the info giancarlo. i am excited to try the side chain version.
i did first discover this issue on a mix buss compressor. so it isn't isolated to solo sounds. at the time i didn't know it was the lowend causing it, so i don't know if i could have backed off the lowend before the compressor and applied more afterward. thanks, Darrell