Vienna Symphonic Library Forum
Forum Statistics

181,965 users have contributed to 42,196 threads and 254,639 posts.

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

  • System restore, cant open saved VEP project.

    Hi.
    I have been working with one Cubase VEP project for the last three weeks. I have manualy (Save as) the VEP project four times under different names.

    Today I had to do a restore on the W7 VEP computer.
    It restored to a point befor I installed VEP.

    I installed VEP again.I installed the latest version.

    Now I cant open any saved VEP Projects, if I try I get a Window window that tells me that VEP has to close.
    If I open the Cubase project I have been working on, VEP opens an new Project (one Master, one empty Instrument)

    If I open a new VEP Project, and a new Cubase Project/VEP project and saves the Cubase project , VEP save and then opens the corresponding project when starting the Cubase project.

    Is VEP saving to some secret location (on the C disc)?

    Is there a 100% safe way to Store/Save?


  • i could think of the following issue: going back to your restore point also custom presets and/or matrices you had saved to your custom data folder have been *restored* (i.e. removed)

    your cubase project (better: VE PRO referenced in your cubase project) is looking for those no longer existing presets ... vframe, mframe, ect)

     

    possibly the following procedure helps:

    - create a restore point now (to save your current state)

    - go back to a restore point you expect the custom data folder (usually C:\Users\Public\Documents\VSL Custom Data) to be still there

    - copy the content of this folder to a location not affected by system restore (eg. your sample drive, a USB stick)

    - retrurn to the restore point from above (today)

    - copy back the files bauckuped before

     

    hth, christian


    and remember: only a CRAY can run an endless loop in just three seconds.
  • Thanks for the reply.
    I dont think anything should be saved to a "secret" location, it seems like realy bad idea.

    If I (manualy using Save As) Save my VEP project. Close my Cubase folder. I defenetly think that VEP should open my saved VEP project not something hidden in a mysterious folder.

    What wories me even more is that I cant open my manualy saved project.

    Is ther a way to set this "secret" save folder?


  • fortunately this is not a secret folder - it is actually in the public files and you can select the location for custom data folder location from the directory manager.

    if you run system restore all content for monitored drives is affected ... this is by design.

    christian


    and remember: only a CRAY can run an endless loop in just three seconds.
  • Thanks Christian for clearing this up.
    Even if its not a secret folder, now that you told me, its a strange consept to save to an other file than the manualy saved file. But as long as you know whats happen ist (sort off) okay.


  • maybe i have not been clear enough:

    - i can think of this could be a reason for your issue ... sounds like that at least ...

    - you can choose the location of your custom data folder at your convenience (as you can do with the location for VST plugins, project files, whatever)

    - everything on the C-drive (if monitored and system restore turned on) is affected by going back to a former system restore point (your images, personal files, public files, programs, mailbox, ect ..)

    christian


    and remember: only a CRAY can run an endless loop in just three seconds.
  • You have been very clear.
    My main issue here is that when you manualy save, in this case saving your project to a spesific file and location, the program (VEP) should not do a save to an other location.

    VSL has in my mind made a mistake here, As it is now it save to two locations.

    -The one you shoose when you do a Save as.
    -A default VEP folder where the save prosesse is initiated by doing a Save on the host program (like Cubase).

    I dont think this the last save idea is a briliant one. A Save should save to one place. I would suggest that VSL change this and make a Save initsiated by the host (cubase in my case) save to the manualy selected file.

    I guess this consept of saving comes from how VST pluggins settings are normaly saved. As I see it VEP is a standalone program and therfor should function as such.

    And, I movede the VSL default folder out of the C disc ;-). I learnt this the hard way ......


  • understand - well, though the idea is good, how should VE know which paths your host has set in its preferences (to my knowledge this can actually vary between projects), especially if eg. VE PRO runs on a slave computer ... VST does not offer submitting such an information.

    there are also further considerations making this appear impracticable under other points of view.

    sorry though for the hassle, christian


    and remember: only a CRAY can run an endless loop in just three seconds.
  • Its possible to store VST instrument setup, thats done on all VST instruments that I know of, it works beatifull in Cubase so why not In VEP?


  • last edited
    last edited

    @yguddal_3972 said:

    Its possible to store VST instrument setup, thats done on all VST instruments that I know of, it works beatifull in Cubase so why not In VEP?

     

    What would be more sensible, IMO, is to stress to customers to back up the Custom Data folder. I also had no idea that it could be removed by System restore, because I'd always thought that it was only system files that were restored, rather than user files.

    DG


  • last edited
    last edited

    yguddal, you can store the instrument setup, you cannot store custom presets or custom matrices, you can just reference them.

    DG, if a drive is monitored this affects all files stored on this drive even including the My Documents hierarchy (except document file types) - this behaviour has changed from XP to VISTA.

    On Windows Vista, this (monitored) set of files is defined by monitored extensions outside of the Windows folder, and everything under the Windows folder.

    however, it was just an idea what might have caused the issue, i'm using restore points rarely and will double check on next occasion how it behaves in fact for the custom data folder.

    the content of the custom data folder is NOT affected by a software uninstall operation for a vienna application.

    christian


    and remember: only a CRAY can run an endless loop in just three seconds.