Vienna Symphonic Library Forum
Forum Statistics

197,167 users have contributed to 43,056 threads and 258,545 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Workflow Recommendation

  • Workflow Recommendation

    M
    M

    New to VEP5 so trying to understand the best way to establish a workflow; here are some of my thoughts.  I use Logic X not that it really matters.

    First, create some individual instance/projects:  one for strings, one for brass, etc.

    Second, create some metaframes.  Start VEP5 server; you can add your instnaces by drag and dropping them into the server window and then save those selected instances as a metaframe.  Being able to drag and drop instances seems to be a great way to quickly load the items you need in a particular project.  Unfortunately you have to do these one at a time; but if you cold multi-select then you could really move fast building up the instances you'd need for a song.

    Now I create a song in LX using the instances in my metaframe.  Should I be saving a metaframe named to match my LX project song?  Then in the future I would open the LX project metaframe first and then my LX song? I think this is what the manual documentation is saying when saving DECOUPLED (see below).

    What I notice is if I open an empty server window with no instances; then open the LX song with preserved instances that the VEP5 server will be loaded with VEP5 instances used in the LX song that had preserve on/active.  Awesome!  However of course in this scenario an unsaved metaframe is created. (or should I just call that a server window becasue it is not a metaframe until saved as a metaframe).

    I'm just looking for some workflow recommendations.

     

    From VEP5 manual:
    Another option for the professionals (if you ́d like to keep DECOUPLE activated) is to save your Vienna Ensemble Pro instances as Projects (*.viframe32/64) or Metaframes (*.mframe32/64) before closing your song in the sequencer, or else there is no way to recall the loaded instruments.
  • J
    J
    last edited
    last edited

    I can't comment on the rest of your post but to this point...

    @michaelhayesmusic said:

    Being able to drag and drop instances seems to be a great way to quickly load the items you need in a particular project.  Unfortunately you have to do these one at a time; but if you cold multi-select then you could really move fast building up the instances you'd need for a song.

     

    You only have to create your template once then just save it.  Then if the next project requires the same string ensemble with the same samples then you just recall the saved template.  It will pull up that entire ensemble with the articulations and settings you want in one click.

    That way, you are only having to invent the wheel once.