Is it expected that Nebula continues to use CPU even after audio stops playing? I've noticed this from the beginning but assumed it was "normal" behaviour (even though other plugins don't do it..)
Am using the AU version of nebula pro server (though without the server standalone app, ie just instances of nebula loaded in the DAW) in Logic 9.1.8. I don't know if it's anything to do with the input level being read at -192db after audio stops playing (ie maybe it thinks theres still an incredibly low level signal, which it's trying to process?)
However I today tried accessing the VST version of nebula in logic via a VST bridge (DDMF). To my surprise the CPU meter returned to 0 when audio stopped playing. Obviously this is much better. Is it possible the AU version is not optimised as well as the VST version?