I got the MDynamicEq and so far it's my favorite EQ plugin and really helps me to track down problem areas fast.

However, I am seeing some problems with performance. My session is running in 32bit mode on i7 at 44.1 kHz and right now has about 5 instances (no upsampling).

When I load up the project, CPU meter in Logic is all the way down but once I open GUI for MDynamicEQ and start using the sonogram, things get very unresponsive in Logic. In addition, the CPU meters don't go down even when playback is stopped.
Turning the sonogram off afterwards does not help and I think that analyzer might have a similar (but smaller) effect.

As for the CPU meters not going down, I suspect that it's probably because of Waves' classic compressor plugins, which generate 60hz hum, which is audible even when the session is not playing.

That made me wonder if MDynamicEQ's analyzer and sonogram are still working even if the UI is closed.
I went through all instances and turned off the visualizers. It did help a lot but I am still seeing a little of lagging in general Logic responsiveness.

Anyone else experiencing this?

UPDATE: Right now it's so bad, that doing any work is very hard. It took about 40 seconds for the DAW to stop playback.

Activity Monitor shows about 127% CPU load.
The only other change I can think of is the updated Brainworx Cleansweep. Will revert to pre-plugins alliance version to check.

Well, I have heard about this problem on some Windows system with on-board integrated video card. There were about 2 cases as far as I remember, both solved by using a dedicated video-card (which should always be used). Mac systems always have this afaik, but aren't you using a shared memory for video processing?
There is a major update betaversion coming out in a few days tops, which further improves memory usage and rendering, but this looks way to extreme. On my Windows based i7 I can run literally like 50 instances of the plugin without a significant problem and when sonograms are enabled, only the secondary GUI processing thread is affected.
Please try to make a simple project with just our plugins to ensure this is really related.

I'm working on an iMac, so yes, the video card is integrated (Radeon 58xx) but I don't think it is using shared memory.

So far I have reverted Brainworx's CleanSweep to an older release, booted from DVD to repair disk and disk permissions, cleaned OSX up with Onyx (including nuking AudioUnits cache).

So far it seems to have helped but I did not have a chance to run the session for a longer time.

It might have been CleanSweep that was the culprit here after all. I will update the thread after I spend more time with the session.

Thank you!

Ok . Also please note that these issues may be caused by some background processes - antiviruses, malware cleaners etc. These apps usually try to make the user think they are needed and don't take any CPU , but the opposite is true...

The response time has been a lot better now, but I am still getting a little lag that seems to be tied to using the sonogram/analyzer.

At this time, I can't really play around to troubleshoot the source of the issue but it's to a point where I can live with it.

I'll see if new version changes anything and will try to set up a session with only the Melda DynEQ once I am done with current project.

Thank you for your help and great job making these plugins. They are exceptional.

Thank you for the info! We'll see with the new version if it will not be good enough, we'll take it from there .