Vienna Symphonic Library Forum
Forum Statistics

201,028 users have contributed to 43,227 threads and 259,190 posts.

In the past 24 hours, we have 7 new thread(s), 33 new post(s) and 74 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. How to un-install VE Pro?

  • How to un-install VE Pro?

    R
    R

    I have another thread here about losing aux inputs every time I close a DP7.21 file and open a new one. It's getting to the point where I really would rather not work like this as I have to reconstruct it every time I create a new cue.

    Is there a way to uninstall the program, then I could re-install the original version that I purchased when VEPro was first released? I didn't have this problem before upgrading to the latest versions of VEPro and Vienna Instruments. I assume I will need to go back to both VEPro original release version and Vienna Instruments might also have to be rolled back?
  • PaulP
    VSL Team
    PaulP

    Hi Rob,

    we´re trying to reproduce your problems here.... is anybody else experiencing this?

    To uninstall, it´s best to use the included uninstaller (Applications => Vienna Ensemble PRO Folder). Vienna Instruments is a different software. If you´re only using VI within VE PRO, you don´t have to roll back there. 

    Best,

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • R
    R

    Thank you Paul.

    I will update with any further info especially if I can clarify the exact course of events. Please understand I am busy with composing and deadlines so sometimes my info is not as detailed as you could benefit from in reproducing. Once it works I tend to just try to get my work done and record and move on to the next cue. Allow me to refrain from posting further details until I am sure of what I am saying in terms of procedure. I've looked closely at the manual especially the "song 1, song 2" info which is great, but for me, and I'm trying to notice any user error, it isn't as simple as that it seems. Thanks.
  • R
    R

    HI again Paul,

    For the moment may I outline my procedure that occurred last night:

    Start up Ve Pro machine, start 32bit and 64bit servers. Load my metaframe template for this project (a movie) into each. (each contains several instances, with labels like "LASS strings 1, LASS strings 2, pianos, drums, bass, EWQLSO GOLD PLAY, Orchestra FX etc)

    Start DP7 machine, start DP7, open a file I had been working on.

    DP7 had lost it's aux inputs (which were labeled VEPro LASS strings 1, VEPro LASS strings 2, VEPro pianos etc as above to reflect what is in the metaframes).

    Re-created new aux inputs (new stereo bundles in DP7) etc to get it working again.

    Continued writing and recording the music. SAVED the metaframes (32 and 64) (not save as). SAVED the file (DP7).

    Closed the DP7 Song 1 file. Copied it. Renamed the copy (eg "Song 2"). Open Song 2.

    This time VEPro metaframe attempted to load new instances. Crashed due to memory error (probably overloaded).

    The day before, I had worked on a (lets say) SONG 1 file, completed it. Saved it. Re-opened it 4 hours later (after leaving the studio) and all of the VEPro Aux tracks in DP had lost their input assignments. In that particular case all I had done was saved the DP file after completing work. Closed it. No other work on either computer whatsoever. RE opened that same file 4 hours later to discover the above.

    Please note this is not a "one off" event, for about a week now opening files has resulted in similar results but in previous cases I am not 100% sure what I did or didn't do that might have been user error in terms of saving the metaframes etc. I outline the 2 particular events above because I am sure of my step by step procedure there. But opening DP7.21 files this past week usually results in lost aux input assignments, disconnections from VEPro, and sometimes re-loading of the metaframes again, resulting in memory errors on the VEPro machine as it attempts to load large files on top of the material already loaded. Reading the mainal very carefully about how that can happen but I thought I had done everything correctly.

    I will provide more info as I work further, and when I am sure of what I have done or not done. Thank you.
  • R
    R

    Hello again, an update.

    Today I thought I'd try something that I thought would be fool proof: Instead of loading the metaframes up at the beginning of the day and risk them being re-loaded and twice, I did the following thinking DP7 would tell VEPro what to load in and not make any mistakes:

    Started VEPro machine, started the 32 and 64 bit servers. Left them empty ( I don't usually do this).

    Started the DP7 machine, started DP7 and loaded SONG 2 from last night (and previous post above).

    As expected DP7 pushed the info to the VEPro machine and began loading the servers / metaframes.

    The 64 bit version appeard to successfully and fully load it's instances.

    During the 32 bit version loading, VEPro 32bit crashed.

    EDIT: I tried this again and the same result. The above procedure is repeatable. This is now an additional issue I have.

    ALSO please note although the 64bit version push-loaded, in DP7 all aux in assignments are once again, lost. They can only be recreated all over again by creating new stereo bundles for each aux track (one per instance, I have a total of 13 instances).
  • R
    R

    So instead I went back to how I usually start up. Started VEPro machines first and loaded the metaframes.

    Started the DP7 machine, opened the Song 2 file. All Aux inputs had been lost. 

    Recreated the aux input bundles in DP, Hit SAVE in DP.

    DP froze / not responding, and I'll have to force quit and start all over again.

    (Force quit DP, restart DP song 2 file, and VEPro machine now tries to load the instances all over again in addition to the stored ones, resulting in a memory error and crash of the VEPro machine).

    This has left me with no way it seems right now on my system with these versions, to access VEPro!!!! I am going to have to try un-installing the software and going back to my original purchased version. However I don't recall if it was discs or download? I'll check this site for available versions to re-download if possible.
  • R
    R

    I would like to go back to my original version of VEPro which is the version that was initially released, and also the version of Vienna Instruments that would be compatible with that. At this website, in the ARCHIVE version dated 2010-08-27 is the oldest available. Is any access available to much older versions? I know that the version that worked for me was before the de-couple feature was released, and I think it was the very first release of the software.
  • R
    R

    minor update:

    Started VEpro machine, started and loaded 32 and 64bit metaframes. (Song 1)

    Started DP7.21 machine, started DP and Song 1 from example above. Aux in channels are in italics, thus lost.

    However, as it tries to complete fully loading the following happens:

    VEPro machine now attempts to load AGAIN song 1 metframe material, this will result in a memory crash. So this time I FORCE QUITTED the VEpro 32 but application on the VEPro machine. I know it's headed for a memory crash so I thought I'd see what happens.

    After it force quitted, THE DP MACHINE DE-ITALICIZED THE AUX INPUT CHANNELS. 

    This is very interesting. Of course I don't know what to do next. But once the 32 bit server was force quitted on the VEPro machine, DP found the aux inputs and returned to "normal".
  • M
    M

    Hi, Paul -

    Yes, I am.  Here's my story and it matches Bob's a good bit.   

    I just got hired to help with a film scoring project and was required to use the in-house rig which is DP7 based.  To work around the memory limits of 32-bit, I instantiated VE Pro shells to run multiple instances of virtual instruments.  it works quite well except one thing: periodically, DP7 loses the audio routing from VE Pro outputs to the additional DP7 aux inputs intended for VEP outputs 3 thru 32.  My template includes VE Pro as an AU instrument plus additional aux inputs to receive audio from additional VE Pro outputs.  When i start a new cue by loading the template, the DP7 aux inputs are no longer connected to VE Pro.  (Note: the original VE Pro instrument in DP7 is still intact as is the connection from the main VE Pro outputs, 1&2).  

    On the matter of workflow...

    I don't load the metaframes first.  I load the sequences and close them before opening another and this works like a charm.  DP7 unloads all of the instances in the VEP server on close and reloads everything when i open another sequence.  I.e, I'm not using 'preserve'.  I haven't had a crash yet.  It is, however, a bit slow.

    BTW, Paul, is it the fault of DP that only one midi port is available per instance?  I've heard on the forums out there that it's the AU's responsiblity to handle that task.  if this is true, anybody know what the chances are that this'll get fixed?  

    Many thanks.
  • J
    J

    Just my $.02 here..

    I remember I had really frustrating issues with DP7 losing it's routing with VEP.  and I was at DP7.21.  I upgraded to DP7.24 and all was fixed!

    Might not solve your issue, but I noticed you were on DP7.21  and there were some major bugs in that version.  especially with bundles. DP7.24 is very rock solid!! ..IMHO..

    ~J
  • M
    M

    Oh, that's my personal rig in the signature.  The studio i'm working in is 7.24,  I just upgraded it.  

    so, you had this problem before and now you don't?  

    Thanks for the 2 cents!