MIR Pro doesn't save position data

[JBuck]

Hey,

It has come to my attention that when saving MIR Pro via the VE Pro File tab, it does not save any instrument data. It only seems to save the mic data. Is this normal behaviour or a bug?. And if it is normal, I am requesting that in the future there be a way to save the instrument data. This would allow the user to place the instruments on stage, configure the angle and wet dry ratios, save and then do a comparison with different settings. Or load this data intro different VE Pro projects.

Cheers.

JBuck

[Dietz]

MIR Pro's so-called "Engine Project" data is indeed meant to save all Venue-relevant settings like Venue selection, microphone selection and setup, RoomEQ banks and so on - in other words: the "empty room".

All instrument-specific parameters are handled by the single instances of the MIR track plug-in, i.e. the "Icon" on a MIR Pro's stage. In VE Pro you can save and manage these settings by means of the so-called "Channel Sets". The respective commands are available from the context-sensitive right-click menu.

MIR Pro's plug-in version (VST/AU/AAX) simply relies on the preset management of the host. - Sidenote: The most important thing to remember in this context is the fact that the _very first_ instance of MIR Pro defines its output format (Stereo, 5.1, etc.).

... that said, we are _very_ aware of the fact that it needs a much more refined and powerful preset management to make use of a complex application like MIR Pro to its full extent. We work an update that will take care for these demands.

HTH,

[William]

I never had this happen.  All positions, EQ, Dry/Wet and any other settings for individual instruments as well as the overall hall are always saved in the VE Pro file so something must be seriously wrong with this setup.  

[Seventh Sam]

@Dietz said:

MIR Pro's so-called "Engine Project" data is indeed meant to save all Venue-relevant settings like Venue selection, microphone selection and setup, RoomEQ banks and so on - in other words: the "empty room".

When you roll out the update, please keep this functionality in.  It's extraordinarily helpful when working with many instances that need diff. instrument placements and parameters but require the same room/space across all the instances.  I can't imagine why this would be taken out, but I just wanted to drop my 2c in just in case...

[William]

A VE instance can be saved with every MIR setting, and all the instruments can be removed or replaced but the MIR hall settings will be the same.  

[Seventh Sam]

@William said:

A VE instance can be saved with every MIR setting, and all the instruments can be removed or replaced but the MIR hall settings will be the same.  

I know.  However, it's helpful in certain cases to be able to save the MIR "room" settings independently.  In my case, I have a Strings Instance, Woodwinds Instance, etc. but I want them all to be in the same room with the same settings.  If I want to change any of the room settings and have them applied to all instances, all I have to do is save the new MIR Engine settings and load them in each of the instances.  If I saved it as a VE instance project, I'd have to reload each instance's instruments to their respective section (Strings, Winds, whatever) each time I wanted to change a parameter.

[William]

Yeah that makes sense.  I've just been using one big instance but it would be helpful for lots of them.

[Seventh Sam]

@William said:

Yeah that makes sense.  I've just been using one big instance but it would be helpful for lots of them.

I would prefer that, honestly, but I need to have the option to render stems (either on a section by section or instrument by instrument basis).  There's a workaround in the DAW I use, but it's annoying to set up and hogs CPU waaay more than having multiple instances...

[Seventh Sam]

Wow, I just realized that I'm making this way harder than it has to be.  Rather than having separate instances for all the different sections, I can just assign each section to a group in one instance.  Then, when I want to render stems of the sections (or even instruments), I just mute the other sections in VEP7, render in the DAW, rinse and repeat for the other sections.  😳

Thank you, William, for inadvertently triggering this epiphany.

[Dietz]

@Seventh Sam said:

Wow, I just realized that I'm making this way harder than it has to be.  Rather than having separate instances for all the different sections, I can just assign each section to a group in one instance.  Then, when I want to render stems of the sections (or even instruments), I just mute the other sections in VEP7, render in the DAW, rinse and repeat for the other sections.  😳

Thank you, William, for inadvertently triggering this epiphany.

Many DAWs offer simultaneous channel bouncing. If you use several outputs from VEP and route your stems through them, you can actually drop the "rinse and repeat"-part, too. 😉

[Seventh Sam]

@Seventh Sam said:

Wow, I just realized that I'm making this way harder than it has to be.  Rather than having separate instances for all the different sections, I can just assign each section to a group in one instance.  Then, when I want to render stems of the sections (or even instruments), I just mute the other sections in VEP7, render in the DAW, rinse and repeat for the other sections.  😳

Thank you, William, for inadvertently triggering this epiphany.

Many DAWs offer simultaneous channel bouncing. If you use several outputs from VEP and route your stems through them, you can actually drop the "rinse and repeat"-part, too. 😉

Time to break out the manual!

[William]

I didn't do anything inadvertently. I didn't think separate instances made any sense because in my setup using VE as a standalone it is unlimited in instruments, channels, ports, plugins, etc. except by the hardware. But I have an unusual system so it probably is not relevant

[Seventh Sam]

All I meant is that this thread got me thinking about how to do things more efficiently.  I'm glad it it did!

[William]

Right, I was actually thinking of some other setups I've heard of, rather than exactly what we were discussing. 

[JBuck]

@Dietz said:

All instrument-specific parameters are handled by the single instances of the MIR track plug-in, i.e. the "Icon" on a MIR Pro's stage. In VE Pro you can save and manage these settings by means of the so-called "Channel Sets". The respective commands are available from the context-sensitive right-click menu.

So at this point it is not possible to convert my 80 instrument orchestra from my e.g. Konzerthaus preset to my  Sage Gateshead preset without closing Cubase, closing VE Pro and loading up my Sage Gateshead template in both programs or, as you say, go through and load the Channel Set or the individual MIRCHAN file for all 80 instruments?.

Thanks.

[Dietz]

The answer is not as simple as a "yes" or "no". :-)

As long as you really want to switch between Vienna Konzerthaus - Großer Saal (or Mozartsaal) and The Sage Gateshead - Hall One, there would be the option of using the MIRx Mode presets provided for these Venues. In that scenario, all players would "magically" find their proper places all by themselves.

If you just want to bring over your 80 players to another Venue (one that doesn't offer MIRx Mode presets), but without expecting them to find themselves a "ready to roll" setting, then changing Venue is as simple as selecting one from MIR Pro' Venue Selection. Depending on the shape and size of the Venue, you will have to re-adjust position(s), maybe Main and Secondary Microphone setup, and most of all: The RoomEQ settings. The good news is that MIR can manage the latter by itself: All Output-related parameters are saved and recalled as "MIR Engine Projects" from the File ...-dialog in MIR Pro's main window.

... and as long as you have all your players instantiated within VE Pro rather than your DAW, you can rely on VE Pro's so-called Channel Sets to manage Venue-specific player settings - individual ones or groups.

HTH,

[JBuck]

Right, so all we really need now is to be able to batch save/load Channel Sets and we are away. This would be ideal if it were done by VE Pro Instance. We would still need to be able to batch save/load MIRCHAN files in our DAW though, as I'm sure people are using MIR Pro in their DAW without VE Pro.

Thanks.

[Dietz]

Like I wrote above: A new preset creation- and management system will be introduced with the upcoming MIR 3D.