Yes I know. But I don't want to copy the MIR settings for each instrument or group three times on three computers.. Every time. :) This is a triple work. I want 3 computers and 1 space for my orchestra.
I do not think it is difficult to make. Now we connecting with VE PRO like this:
Host > VE Server > VE Instance - using the plug-in "Server Interface" (for Instance) and "Audio-Input" (for Instance audio-input)
But we could connecting with MIR like this:
Host > VE Server > MIR - using the plug-in "MIR Interface" or "MIR Audio-Input" :)
Or directly:
Host > MIR on slave computer.
I don't mind to buy 3 MIRs for my 3 computer and 3*x.. roompacks :) But then I have to copy all the settings three times ..
If you mean to run the MIR in VE Instance on slave computer and connect to this MIR via a audio-plugin, it is a bad idea. First, you know how it is not convenient :), secondly, vienna guys has not yet solved the problem of conflict between host and VE PRO multiprocessing using..
Now we have VE Server working separately from the host. In other words - VE Server-Standalone. :) And connecting host with server via "server interface" plug-in. MIR also can works Standalone (I think MIR have 127.0.0.0 too :)) and connecting with host via Vienna MIR PRO plug-in. Why we can not connect with MIR on the slave computer like the server?