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 53 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Saving vesp and vep projects issue

  • Saving vesp and vep projects issue

    D
    D

    Saving both vesp and vep projects is obviously an important part of workflow. With VEP7 this can be confusing because of nomenclature. VEP7 refers to the saving of both as "save project". It would be clearer to me if VEP referred to saving an instance as Save Instance instead of Save Project. Just sayin'

    Also when I am working I occasionally save the vesp project (for safety's sake). Instead of simply saving, VEP7 asks me to name the project all over again...almost all of the time. Occasionally it will simply save. But only occasionally. After I save - and rename again - when I quit VEP7, it asks me to name the project (YET AGAIN). This is cumbersome, although of course doable.

    I know the autosave feature is there, but I am still nervous about trusting a large project will be saved properly all the time. Maybe I'm worrying needlessly. So I could use a little clarity on this issue.

    Thanks, 

    Paul R
  • V
    V

    Absolutely confusing 

     

    The most important part (to save the work done) is too complex. There are too many combinations between couple, decouple, preserve, unpreserve, autosave on daw, autosave on VEP, the notifications leading you to save wrong on what is already saved correctly…

     

    this is my first impression 
  • Andreas8420A
    VSL Team
    Andreas8420A

    Hi!

    I believe auto-safe is fairly self-explanatory. When an instance is coupled all the VE Pro data is saved in the DAW project file. If you decouple instances, then you will have to save the VE Pro project separately. This can make sense for several reasons. But the biggest advantage is that saving the DAW session is a lot quicker as some plugins like Kontakt do save a lot of data and that results in much longer saving times for your DAW project. Decoupled Mode solves that.

    And preserved instances stay up and running even if you close the DAW project (and the connections to VE Pro) entirely. That can be helpful if you use the same instruments for multiple projects. Preservers instances allow you to switch to other projects without the need to reload instruments in your VE Pro Server. Unpreserved instances are closed completely, once you disconnect them from the host (= DAW).

    Best regards,
    Andreas

    VSL Team | Product Specialist & Media Editing