@nektarios said:
Thank you. So effectively, as a VST, I need a separate MIR PRO instance per instrument. Which will eat up a ton of my CPU cycles... π Am I right?
I haven't paid attention to the CPU effects, but I doubt you're right about that, because when you run it as a VST, each MIR VST you add isn't totally separate. There's a single MIR room, which I think VSL has called the "engine", and each track where you add a VST gets a little thing added, but it's just for communicating with the single MIR room. In the end, I doubt using MIR as a VST takes any more CPU than using it in VE.
The Plug-In (VST) manual descibes it: "the plug-in version of MIR Pro relies on two different parts, namely the actual plug-in, and a common control user interface (UI) shared by all instantiated plug-ins."
Looking in my Win Task Manager, I see just one Win 8.1 process for the MIR engine, while I'm using multiple instruments in VST MIR.