Vienna Symphonic Library Forum
Forum Statistics

200,651 users have contributed to 43,206 threads and 259,114 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. Decoupled & preserved - I don't get it

  • Decoupled & preserved - I don't get it

    P
    P

    From the manual:

    "Activating Decouple does not save or load the viframe project data when the master host saves or loads. This can speed up the workflow a lot when using 3rd party plug-ins like Native Instruments’ Kontakt. In other words: Decoupled, the Vienna Ensemble PRO Server Interface only saves the connection information (the slave it is connected to and, if applicable, the preserved instance)."

    I have the VEP RTAS plugins set to decoupled on the master, and all server instances on the slave are preserved. Today, I opened a recent project, and the VEP server instances were all from another song. Naturally, I freaked out, and couldn't believe where I'd gone wrong. Luckily, I keep a lot of backups of the Pro Tools session files, so I was able to import session data from BEFORE I started using decouple and preserve. Where did I go wrong? You can't say for sure I guess, but where do you think I messed up?

    Also, how should I go about this workflow to be 100% sure not to run into this sort of thing in the future?

    - I want to use decouple to avoid that big sample streamer plugins cause hiccups every time Pro Tools auto-saves.

    - I want to preserve at least the 64-bit version of VEP server because it tends to disconnect fairly often if I don't. Please advise - thank you!
  • P
    P
    OT: I want to add that I wrote the post in sections, but somehow it all got smacked together when I posted it.
  • D
    D

    If you run decoupled, you won't be saving any data with your project. That means that you will always have to load the server manually. I would suggest that before you put a project to bed, you re-couple (is that even a word?) and then there will never be a problem.

    DG
  • D
    D
    last edited
    last edited

     

    @ptlover said:

    OT: I want to add that I wrote the post in sections, but somehow it all got smacked together when I posted it.

    I think you have to enable something or other in your Profile.

    DG
  • P
    P
    last edited
    last edited

    @ptlover said:

    OT: I want to add that I wrote the post in sections, but somehow it all got smacked together when I posted it.

    I think you have to enable something or other in your Profile.

    DG

     

    That's correct. Thanks! 😊
  • P
    P

    But, the snippet below from the manual confuse me:

    Decoupled, the Vienna Ensemble PRO Server Interface only saves the connection information (the slave it is connected to and, if applicable, the preserved instance).

    Under what circumstance will the preserved instance be saved? And doesn't that mean the server instance with ALL it's plugins and plugin settings?

  • D
    D

    The Preserved Instance, including all the information it contains, is only saved when you save coupled the server to the sequencer.

    EDIT: I don't think I completely answered your question.

    The point of Preserve is that if you don't use Preserve, then closing the sequencer project would unload the samples. Think of Preserve plus de-couple as using a standalone, but without the need for virtual MIDI or audio cables.

    DG
  • P
    P

    I totally understand that. I've seen many times during auto-save in Pro Tools that "Project saved" doesn't appear in the lower left corner of VEP server. But, if applicable, the preserved instance will be saved. When is that?