Vienna Symphonic Library Forum
Forum Statistics

181,903 users have contributed to 42,191 threads and 254,624 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Best practice when using Decoupled

  • Best practice when using Decoupled

    R
    R

    I've always used VEP in coupled mode so the metaframes are saved within my Cubase session but I'm thinking of setting up a template with all of my main libraries loaded into and then decoupling. So I get that everything in VEP will not be saved with the Cubase project, and for example I should use automation and pan/volume in Cubase rather than in VEP ... but what about those libraries where there are settings in the sample library GUI ? Such as choosing a specific patch. That is within VEP so how do I save those settings ? I don't "get" this part of how people work with VEP ...
  • C
    C

    VE Pro is a host so all of it is saved in the state upon saving the Project or Server Project.
    Save as, and then continue saving when you make a change.
  • R
    R

    But the whole point of decoupling a large template in VEP is that you don't have to keep reloading the same libraries for every prject. If I'm saving it as you suggest, there is no benefit: it must be reloaded every time.
  • BillB
    BillB

    He means saving in VEP, not your DAW.

    Dorico, Notion, Sibelius, StudioOne, Cubase, Staffpad VE Pro, Synchon, VI, Kontakt Win11 x64, 64GB RAM, Focusrite Scarlett 18i20, August Forster 190
  • R
    R

    I realise he means saving in VEP but then when I next load another project I don't want to be using this amended template, so I'll have to reload it. Which brings me back to my original point: what is the benefit of using large templates in Decoupled mode if you still need to save & reload every time you change project. I don't see the benefit ....
  • B
    B

    I decouple all my big libraries and I use a seperate instance (not decoupled) for VSTis that I want to tweak. I also use a seperate instance (not decoupled) for audio reverb sends.
  • M
    M

    Myself and the guy I work with don't use different templates for different projects.  I think that is the point of Decoupled templates.  You have your main big template that you always use and so you load that up at the beginning of the day-or week-or whatever, and then you may work on different projects but they all use the same VEP template.  
  • C
    C
    last edited
    last edited

    @rjay said:

    I realise he means saving in VEP but then when I next load another project I don't want to be using this amended template, so I'll have to reload it. Which brings me back to my original point: what is the benefit of using large templates in Decoupled mode if you still need to save & reload every time you change project. I don't see the benefit ....

    The benefit of decoupling is 1) it's independent of the DAW. Saving VEP every time you save in the DAW is, with a project of any goodly size, less stable for one thing and a save can take significantly more time. And obviously the need to save the work in the DAW does not through itself mean a need to save the VEP project(s).
    2) in this independence you may leave the same server project up and move to other projects in the DAW, and the DAW does not load anything for you. See above as to stability and ease.

    You save the changes you make on the VEP end as you need to. If you LIKE the DAW to load VEP, which is definitely slower at any rate, do that.  :shrug:
  • C
    C
    last edited
    last edited

    @mbira said:

    Myself and the guy I work with don't use different templates for different projects.  I think that is the point of Decoupled templates.  You have your main big template that you always use and so you load that up at the beginning of the day-or week-or whatever, and then you may work on different projects but they all use the same VEP template.  


    I do not have "a template" for all seasons, every project relates to a DAW project. I do save a lot of things for further use, and I save it set up in Cubase or Nuendo as a template there. But I may subtract from this, I may introduce other things, I'm certain to make changes which suit the project.

    The advantage is the independence, and I see no upside to coupling since it saves no time unless these projects are mighty little. It may well be that I keep a server project up and have another version of the DAW project, or it's a starter 'template' which is my modus operandi when I design the sound for a new project per se; so the established project is up and I instantiate 'new project' in Cubendo.