Vienna Symphonic Library Forum
Forum Statistics

199,024 users have contributed to 43,150 threads and 258,877 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEPRO 6.0.16502 Clicking Tab will not Open Instance

  • VEPRO 6.0.16502 Clicking Tab will not Open Instance

    T
    T

    Hello, I'm having a problem where one of the three instances in my server project will not open the instance when I click on it. The problem happened in this way –

    1. Unsnapped my "Brass" instance from the server window (two other instances opened, also running MIR PRO).

    2. Opened MIRx preset for Teldex Scoring Stage in a newly created fourth instance, which caused VE PRO to crash. 

    3. I reopened VE PRO and the unsnapped "Brass" instance would not respond when I clicked on it, besides changing the name and connecting/preserving. It is fully functional and able to connect with my DAW Cubase and perform the instruments I have loaded, but I am not able to edit or add anything anymore. (The two other instances I have are working fine normally). The autosave function saved over my instance and now I do not have a server project file that is not corrupted.

    Is there any way to fix this VE PRO instance? I spent a lot of time making it and it would be great if I could get it back to working properly.

    Edit: Here are my specs

    VEPRO 6.0.16502. There are some instances of Kontakt 5.6.8 with CineSymphony Lite loaded, and many VIPRO 2.4.15962 instances in this particular un-openable instance.

    Mac Hackintosh El Capitan 10.11.4. 32GB RAM. 3.99GHz Intel Core i7.

     

    Thanks,

    Aaron
  • marnixM
    VSL Team
    marnixM

    Hi Aaron,

    Is it possible, that the unsnapped Brass instance was placed on a second display, which is not connected/turned on?

    Do you want to send a zipped copy of your Server Project to support@vsl.co.at, so I can see if I can do something about this?

    Best, Marnix
  • T
    T

    Hi Marnix,

    Thanks for your reply, now that you mention that, I was trying to get a third display working on my Hackintosh while I was making that instance, and my computer was having problems with that monitor (I think I'm lacking a driver or some operating system level extension) so I ended up disconnecting it and stopped using it. I tried reconnecting that monitor with my server project loaded, and the VEPRO instance interface didn't reappear, unfortunately. I will keep trying in the meantime. 

    I just sent the zipped server project to support. Thanks again!
  • C
    C

    I'm running into the same problem. If I snap an instance to it's own window, save the server project, then reload said server project, the snapped instance is gone. I can't click the instance tab, I can't raise the instance from within Cubase. It's somewhere though, because it's playing my VST instruments! Single monitor setup. 

    I can recreate this problem simply by opening VEP server, create 2 instances and snap one away to it's own window. Save, reopen the server project, and the snapped instance is gone... possibly hidden somewhere with no way to raise it. :(

    We need to be able to right click the instance tab and unsnap it.

    Rob

    EDIT: I found a workaround hack for the time being. When a server project loads, the last instance is selected regardless of whether it's snapped away or not (this has to be a bug, too). This allows you to select View -> Snap instance, select another instance tab, then select the last tab again and magically the missing instance reappears! If you have more instances that are snapped away and hidden/lost, move the missing instance to the end of the tab list, save server project, reopen and repeat until all missing instances are found.
  • T
    T

    @csdstudio Thanks, this workaround is so helpful to know if this ever happens again. Marnix, quickly helped solve this problem for me, my instance was indeed on my third monitor, which I couldn't access due to problems with that monitor on my end. I agree, it would be helpful to have an unsnap right-click button as a safeguard, but regardless I'm very happy this problem has been solved, and for the quickness and helpfulness of our VSL support team.