Vienna Symphonic Library Forum
Forum Statistics

201,276 users have contributed to 43,239 threads and 259,234 posts.

In the past 24 hours, we have 3 new thread(s), 18 new post(s) and 54 new user(s).

  • "multiples" in VEPro 5?

    hello all.

    I am running the VEPro5 demo on a single Mac (MacPro, 8-core, 10.6.8), using it as a plugin on Digital Performer 7.42. The main reason that i am considering VEPro5 is to take the "load" off of DP, and it seems to be doing that very well! But i am very confused about one issue and I hope you all can explain it. It has to do with "multiple" midi channels showing up on "multiple" instances of "multiple" VI's....whew!, too many "multiples!! Apologies in advance for being lengthy here, but I want to give as many details as possibile. Here goes.....

    Prior to trying VEPro, if i wanted to run (say) 3 VI's within DP, I could load (say) a single instance of Kontakt, a single instance of PLAY and a single instance of Aria. The result would be a total of 48 unique midi channels, 16 on each VI, and each of those 48 uniqe channels would be accessible from within DP.

    Now, running VEPro5, I *thought* that I could open a single instance of VEPro5 in DP, then load in those same 3 VI's in to VEPro5. I can do this, but I no longer have access to 48 unique midi channels from within DP....just 16 unique channels? So that, when I open a new track with it's output to "VEPro5-1", it speaks to all 3 VI's at the same time?

    Am I just not understanding how to route midi in VEPRo5? Or, if I wanted to accomplish what I did before using VEPRo5, would I need to open *3* instances of VEPro5 in DP - - each one, containing a *single* VI? I suppose this might do it, but if I'm using 12-14 VI's, that's an awful lot of VEPro5's to deal with!

    Thanks in advance for your help, VEPRo5 looks like a winner, just need to understand the midi routing...


  • last edited
    last edited

    Hello williemyers,

    Unfortunately, AU is limited to 1 MIDI Port (=16 MIDI Channels) by design.

    You have 2 options there with DP:

    1) Open more than one VE PRO instance and insert one multi-timbral plug-in (Kontakt, Play, Aria) into each. Select "Omni" as the MIDI Channel, as described in the VE PRO 5 Manual, on page 49.

    2) Use EVENT INPUT Plug-ins to add MIDI Ports. This is described on page 17 of the VE PRO 5 Manual.

    Additionally, you might want to read the Routing chapter for Digital Performer, page 59, for more flexibility when it come to routing your audio signals [:)]

    Best,

    Paul


    Paul Kopf Head of Product Marketing, Social Media and Support
  • Paul , many thanks for your reply! It was "EVENT INPUT" plugins that I needed and it worked very well. I had been able to open multiple VI's within a single VEP instance and access those VI's on unique MIDI channels thru DP. happy camper.

    or at least, a happy camper for the time that I was testing the DP session. than I closed DP and VEPro5 for a break and when I returned, I had problems...
    note here that, in the process of setting up that single VEP instance, I had created two files on my Desktop...(a.) "xxxxx.viframe64" and (b.) "xxxx.mframe64". don't know exactly waht these files were all about, but I think I do need to know...

    I am trying to re-open it all and having no luck at all.... :( :(
    first question is, I've read posts on other websites (MOTUNation)  and other places where folks recommend;(a.) load VEPro first, *then* DP, or (b.) load DP first, *then* VEPro, or (c.) load DP first and let *it* load VEPro for you.
    None of these three are working for me.

    If I try (a.), DP usually reports an error message when it trys to open and will not open at all...
    If I try (b.), when I've opened VEP and look for "Server Instances" to connect to, that window is always blank...
    I've tried (c.) but DP just sits there and doesn't load anything.

    again, any/all help will be appreciated, only one day left on my test!


  • Hi, 

    Did you actually start the VE PRO SERVER? Otherwise DP has nothing to connect to....

    mframe and viframe are explained in the manual, page 21 [:)]

    Best, 

    Paul


    Paul Kopf Head of Product Marketing, Social Media and Support
  • damn!!.....

    I hate it!!....

    when things work....

    perfectly....

    for no apparent reason!!!

    [:$]