tired of this plug-in not working properly, I've had the same issue since i bought the crappy thing. the exact same problem was happening on my old computer. it maxes out the cpu when the interface is opened. this has been raised before in a separate thread, is a known issue and various people also experience it.

tired of this plug-in not working properly, I've had the same issue since i bought the crappy thing. the exact same problem was happening on my old computer. it maxes out the cpu when the interface is opened. this has been raised before in a separate thread, is a known issue and various people also experience it.

Also have the same issues with other Arturia plugins when the GUI is open.... Don't hold your breath for a solution!

Hi everyone , i had a look into this on logic x 10.0.7 with my mac pro 6 core 2010 . and i cannot get the same results as you .logic works in a strange way with multi cores and its easy to overload due to the way logic works .there is a link below which was for logic 8 but may still apply.I loaded just semv and loaded the cpu monitor in logic and i tried everything to max it out .logic and the semv was checked in activity monitor and only used 16% of my cpu which goes unto 600%.check the link if your making projects.http://support.apple.com/kb/HT3161?viewlocale=en_US&locale=en_US

My issue with it is in Pro Tools, sorry i jumped in on your thread but thought it might be connected in some way.That said, in my instance it isn't a plug in CPU problem per sť, it's more a graphical refresh issue which other plugs (Arturia) do also suffer from.

Thanks, Stuart

P.S. My thought on this is that it affects graphics that having moving parts to them (Not keys) i.e, Spark pads lighting up, moving patterns, Sequence patterns and arpeggios.

hello all, first post.i also have the SEM's overload problems, several plug-ins had this (lex native, overloud breverb f.e.)'had this', because they have all been fixed now and the problem with lex, where i did beta-testing, was some GUI priority setting.does this also apply to the sem? in it's current state is unusable here when the GUI is open.in a total empty project it works fine, but as soon as you add other plug-ins the CPU goes through the roof ONLY if the SEM gui is open.