Vienna Symphonic Library Forum
Forum Statistics

194,510 users have contributed to 42,922 threads and 257,973 posts.

In the past 24 hours, we have 2 new thread(s), 8 new post(s) and 88 new user(s).

  • MirPro across instances?

    Preface this question by saying that i am brand new to the world of VSL.

    Tools:  Logic Pro, VEP6, MirPro, Cube Full, Appassionata Full

    basic question, if I split up my orchestra into multiple instances in order to deal with limitations of LogicPro, then I end up with an instance of MirPro on each VEP instance.  So let's say, for example, I have one instance for wood winds, another instance for brasses, another for perc and one for strings.  Each instance has its own MirPro instance and basically on that instance I will only see the instruments from that section on the mirPro stage.  

    Is there any sonic difference between doing it this way versus having one massive instance with all channels in one instance, only one instance of MirPro and all instruments on one mirpro stage?

    I guess doing it this way must use a little bit more CPU too of course, but just asking for any other pros or cons.

    Tonight I decided to try to get the ET Adventures on Earth mock up from Jay Bacal, working in Logic Pro.  Jay's version was in Cubase only and he provided the midi file also.  I am able to get it working and I can share that Logic project if anyone wants to check it out.. but anyway, it uses 4 VEP instances and mirpro split up with each section in its own mirpro virtual soundstage.  It seems to work and sound pretty good, but I don't know if                        this is the only way to handle it, since LogicPro has a really hard time with super large VEP instances.


  • As far as I know, Jay uses several VE Pro instanes for organisational reasons only. There will be no sonic difference as long as one uses the same MIR Engine settings in all of them. And there should be no significant difference in CPU consumption either when staying inside one huge frame. (... maybe Logic reacts somewhat peculiar in this respect, but to be absolutely sure we would have to ask people who are into the detailed Dos-and-Don'ts of this DAW ... I'm not. ;-) ...).


    /Dietz - Vienna Symphonic Library
  • Thanks a lot for responding. Jay actually did not use multiple vepro instances in this case he provided a single instance with around 100 channels all feeding thorough mirpro, with all instruments on a single mirpro soundstage. Unfortunately LPX does not handle 100 channels into a single instance, even when using the multi port template, there are midi bottlenecks that simply cannot handle it. It’s possible it could work if keyswitches would be changed to CC and perhaps also checking for redundant switches to remove them from the midi traffic, but that would be too much work. I got it to work by splitting up jay’s frame file into four instances. I did this by starting with his full frame for each one and deleting the channels not needed in each one. So in theory, all the mirpro settings are exactly the same as if they were all together on the original single soundstage. This seems to work, midi bottleneck gone and I can hear beautiful score playing. So you feel that these four mirpro cases don’t use more cpu then one giant frame? That is good to know. And good to know there should be no sonic difference either. The only thing I am wondering beyond that is when I do my own mockups it would be supremely easier I guess maybe to have all instruments on a single mirpro stage. Aside from just visualizing all the instruments on one stage is there any other coordinated data between each instrument that will be more difficult to manually make sure they are the same on the separate mirpro stages? In general I prefer having vepro mixers that aren’t 100 channels wide, for me it’s easier to have instances with separate mixers for each one representing a section, which is needed for LPX anyway but i actually like the mixers as being four smaller ones, but I guess I’m only a little concerned about how it will be to make sure four separate mirpro’s will have a cohesive and coordinated sound

  • last edited
    last edited

    @Another User said:

    Aside from just visualizing all the instruments on one stage is there any other coordinated data between each instrument that will be more difficult to manually make sure they are the same on the separate mirpro stages? [...] I guess I’m only a little concerned about how it will be to make sure four separate mirpro’s will have a cohesive and coordinated sound. [...]

    Just make sure that those settings of MIR Pro which aren't purely instrument-specific are identical. This can be achieved easily by means of saving/recalling the so-called "MIR Engine Settings". You can find the respective commands in VE Pro's "File > Vienna MIR Pro" pull-down.


    /Dietz - Vienna Symphonic Library
  • last edited
    last edited

    @Dietz said:

    Just make sure that those settings of MIR Pro which aren't purely instrument-specific are identical. This can be achieved easily by means of saving/recalling the so-called "MIR Engine Settings". You can find the respective commands in VE Pro's "File > Vienna MIR Pro" pull-down.

    hmm, I can't seem to find that vienna MIR Pro pull down.  Its definitely not on VEPro's file menu.  ???


  • So you don't see this ...? (see attachment)

    Image


    /Dietz - Vienna Symphonic Library
  • nope.

    Image


  • I see. I was talking about the stand-alone version. In your case, the solution is one centimeter to the right:

    Image


    /Dietz - Vienna Symphonic Library
  • alright thanks for that...but what exactly does this open/save option allow me to save or open?  I am looking all through the manuals for both MirPro and VEP6 and can't find any mention of what this is.


  • alright please forgive me as I'm catching up as a new user with no VEP or VSL experience from earlier "frame" days.

    Please correct anything I say wrong here so that I can understand...

    1. The output section in the MirPro editor is "global", in that it relates to the main mics, etc.. and would constitute the settings of the Venue.  So I can load a venue, but I can also tweak it with those output settings, and even dig into very specific mic setups if I'm so inclined.
    2. Using the mir pro engine projects can open/save files containing just that information.  So if I am going to use multiple instances of mir pro across VEP instances, then I should make sure they all have the same settings in that OUTPUT section and the same venue for a cohesive sound.  QUESTION:  Are there any factory preset engine project files?
    3. as I was searching around trying to figure this out I found information about so called "venue presets" and found the 1.5 version to download.  They are all viframe files, whatever that is.  I think that's a VEP5 thing.  But anyway, I see that I can open these in VEP6 and when I do, it contains a MIRPRO setup, including venue selection and the output section tweaked, and some of them contain other stuff like miracle reverb on the master bus and some contain channels also, including the instruments arranged on the mir pro stage.  I take it that then if I wanted to, I could save the engine project file from that, to save just that part of the venue preset...just the global stuff related to the whole MIRPRO stage and presumably no VEP channel stuff, no miracle reverb addon, etc..  just the venue section and output section.  Do I have that right?

    another question, these viframe files, are they for just one instance or for the whole VEP server?  

    Is there anyplace I can find a description of all the various files and filename extensions that are currently used by VEP6, MIRPRO, VIPro, etc.?  I'd like to get a better understanding of how they all relate to each other.


  • https://forum.vsl.co.at/topic/48168/Are MIR Templates Available/268541

    /Dietz - Vienna Symphonic Library