i don’t recall if mg2 has a multithreading option, but in mg3 i recall a user whose cpu meter was maxed out using one setting or the other.
if your audio subsystem has an asio driver you should select that. if not you should consider adding an external audio interface. (this would apply regardless of the cpu meter issue)
On the screenshot you made it looks like that you have input signals on all possible notes going into MG2? Usually the bars of the velocity meter are light grey and white for the incoming note. It could be reflections but just double check if they are “light grey” or “white”.
My guitar was in the stand. I had just set it down, so it was simply still ringing out.
Those Cpu readings are even when not playing.
Please note (pun not intended!) the Cpu meter is not constantly pegged. Once in a random while, it hits the ceiling and hovers up there for a few seconds. Meanwhile, the task manager is sedentary.
I have a Focusrite Scarlett Solo, Gen 3.
I also have a Gen 1, and the same strange meter visuals, no matter which interface I use.
As you can see, the Task Manager is showing very little load.
My more direct question should have been, “what is the MG2 Cpu meter actually monitoring?”
I use Imageline Fruity Loops, Producer Version, v 24.2.1
VST MG2, routed through the various Instrument (synthesizer) VSTs.
This rig plays FANTASTICLY! Totally acceptable latency. Fairytale versatility.
There is a project loaded, and there are 5 channels in the Channel Rack with different VSTs on each channel in this particular Project. I additionally have many other Projects, some with up to 20 channels. Same behavior.
