Vienna Symphonic Library Forum
Forum Statistics

199,030 users have contributed to 43,150 threads and 258,878 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Basic Workflow Question -- VE Pro Build 7384 -- SOLVED

  • Basic Workflow Question -- VE Pro Build 7384 -- SOLVED

    M
    M

     I'm using VE Pro on a master computer in Sonar, and loading all VE Pro Instances on a slave computer. There are nine VE Pro Server Interfaces open in Sonar, all of which are decoupled to speed up saving, and nine VE Pro instances on the slave, all of which are preserved. I save the VE Pro instances on the slave as a Metaframe. I save the Sonar song file on the DAW with all the server interfaces "connected" and still decoupled. So that's the workflow, basically.

    Now, when I go to start a new day, I launch VE Pro on the slave. One of two things happens now:

    1. If I launch Sonar on the DAW and open the song file, VE Pro (on the slave) will load up the instances which I had worked with in the song file, but will not load any of the instruments. They are just empty instances with the same names as I had in the metaframe. All the instances are connected. So, I have to disconnect all nine server interfaces in Sonar, then delete the instances on the slave, then load the metaframe, and then reconnect all the instances.

    2. If I first load my Metaframe (on the slave) so that all the instruments are loaded and then open the Sonar song file, the "blank" instances load on the VE Pro slave again, so that I have double the instances there. The new instances are, of course, empty, but I have to then delete them before I save the metaframe (should I make changes).

    I think what I'm asking is: Is there a way to open the sequencer song file (having been saved in a decoupled, connected state), and have it load up the VE Pro instances and instrument data on the slave and be connected? Basically, call up the complete Metaframe when the song file opens.

    Seems to me I remember doing this sort of thing and never having to recouple/save/reconnect. i thought I remembered just opening the metaframe, letting it load, then opening the song file and it was automatically connected without opening "blank" instances.

    Of course, I could be confused and overly confusing the issue.

    Thanks for any help.

    Mahlon
  • civilization 3C
    civilization 3C

    Here's how I work: as you describe, but once I've opened a Cubase project (connected with but decoupled from VE Pro) I recouple VE Pro to Cubase. (It does mean a lot longer save time in Cubase.)

    I've found that if I open the Cubase project while VE Pro is still loading on the slave I might get an empty instance for one of the connections and have to disconnect (then it disappears). Generally I launch the .cpr after VE Pro is done loading. I don't know that this recouple move is why I don't have your issue, but that's what I do and I don't have your issue. It may not help at all [C]... If not, I would try disconnecting and decoupling on your last save before quitting out Sonar.

    If you want Sonar to load VE Pro from blank servers, just don't decouple when you save the Sonar project at the end of your day. In all likelihood, Sonar loading VE Pro and itself at the same time will happen a lot slower than each separately, I think. I used to do that, but the loading times were too much.
  • M
    M

    Thanks for your help. Turns out, I wasn't letting the Metaframe finish loading before I launched the Sonar file. You're right, if it's completely loaded, then Sonar connects to the already open instances and doesn't create any new ones.

    Mahlon
  • civilization 3C
    civilization 3C

    y.w.

    glad you're sorted. that was my first thought. before coffee as it happens...