Vienna Symphonic Library Forum
Forum Statistics

201,681 users have contributed to 43,255 threads and 259,320 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. Using constant metaframe along with song-specific instances of VEPro

  • Using constant metaframe along with song-specific instances of VEPro

    M
    M
    Hi, I've read the manual watched the videos, and trolled the boards. Still a little confused so thanks in advance. I have a large VEPro metaframe loaded with about 18 vframes of orchestral samples, that I use as a constant part of my Logic template. This metaframe loads on the same MAc Pro as Logic, but outside Logic obviously. This metaframe always stays exactly the same, so it is preserved and decoupled, and I can switch from Logic session to session, and it will always be there the same way. However, I would also like to create a separate VEPro setup that I can change from song to song, and have it running alongside the constant metaframe. So that the big metaframe is always there the same way for each different session, but ALSO there is a song specific VEPro (running outside Logic) that I can load up different Kontakt VIs, specific to each individual song. So the constant samples, plus a customizable pallet running simultaneously, all in VEPro outside Logic. What's the best way to set this up? Thanks!
  • D
    D

    Just load a new instance of VE Pro in Logic and set it to be preserved and coupled.

    DG
  • M
    M
    Thanks DG. Could you explain a bit more? I assume by "coupled" you mean not clicking "decoupled" for that instance of VEPro? So that while all the instances in my big metaframe are independent from Logic sessions (preserved and DEcoupled), this new "coupled" instance would load different, song-specific patches each time I load a new Logic session? In that case shouldn't "preserve" and "decouple" both be UNchecked for that instance? So that not only is the instance being saved with the Logic session, it is also not keeping those specific samples loaded in RAM between sessions? Honestly I didn't think you could have extra VEPro instances loaded along with a metaframe that are not part of that metaframe (all on a single computer/VEPro Server). Thanks for clarifying.