Hi Dbudde,
Originally Posted by: dbudde 
So I have some questions about MIRx. I am looking for ways to add instruments beyond the limits of MIR PRO 24. One alternative is to upgrade to MIR PRO. This has the disadvantage of only working on one system unless I purchase a second and/or third license depending on how many slaves I have. Another option is to add a venue or two of MIRx and live with its limitations for the instuments on which it is enabled. So my questions are:
1. I assume these products are compatible right? No problem running some instances of VI Pro in MIR Pro and others with MIRx enabled? All within the same VE Pro instance and/or in separate VE Pro instances?
Well - "compatible" is maybe not the word for it ;-) ... MIR Pro and MIRx are different products and can't share settings, but they will run happily side-by-side. - I posted a comparison between MIR Pro and MIRx some time ago in this thread (just scroll down a bit).
Quote:2. Does enabling MIRx in a VI Pro instance reduce the number of instances I can have in MIR PRO 24? I assume not, but just checking.
Your assumption is right: As the different products they are, they rely on individual licences, so the one won't influence the other at all (apart from technical aspects like the strain put on the CPU and so on).
Quote:3. When using MIRx on one or more slave(s) and MIR Pro 24 on the master, is there any issue about conflicts or numbers of instances that can be used?
Unless I misunderstood your question, the answer is the same as above.
Quote:4. All of this begs the question of why MIR Pro has this limitation in the first place. It is after all a Pro product and so should look superior in every way to MIRx. But it is not in this regard. Unless I just don't understand how the system works. And that is quite possible. So that's why I'm asking...
I understand what you're asking for.
Like I wrote in another recent thread in this forum: MIR is a somewhat peculiar product which offers a unique approach to spatialisation and reverb. The underlying concept implies that it should be used as unified mixing front end for (virtual) orchestration, as one single, final instance for all involved signal sources.
With the advent of MIR Pro, this concept got diluted a bit, as we can now have several instances opened side-by-side in VE Pro. Still it is meant to be seen mostly as "final summing mixer", and not as "reverb engine", spread accross several slaves.
HTH,