Vienna Symphonic Library Forum
Forum Statistics

194,151 users have contributed to 42,912 threads and 257,925 posts.

In the past 24 hours, we have 1 new thread(s), 12 new post(s) and 84 new user(s).

  • last edited
    last edited

    @mattzen said:

    My main concern is that if we get a force disconnect feature, it should not be attached to deleting a project.  I need to disconnect a loaded project and keep it loaded for best workflow and time managment.  If my main machine goes down, I would like to be able to just go to the VE PRO server select each project, force disconnect on each, and have them ready to be reconnected immediately once my main machine is back up.

    I have made both a separate disconnect feature, and a "force disconnect on delete" feature, so I think it suits you rather well!


  • This is why you VSL folks are the best developers.  Thanks for replying and for foresight to add the disconnect feature!  

    Best,

    -matt mariano


  • Great! Gimme!

  • Fantastic, thanks! Any ideas when the next update will be rolled out? 


  • ... or maybe another public beta.... soon would be great! [:D] plaese please!!! 


  • I know it'll be ready when its ready, but is it almost ready? :)

    I want that disconnect feature so bad my teeth hurt...spent over an hour and a half waiting for templates to load yesterday as I had 3 different crashes in Cubase and my palette takes about 25 min to load.

    Are we talking days, weeks? Throw us a bone here. :)


  • Hi,

    we are already testing, but as you know, it´s not wise to make promises with software.

    I hope we will be ready soon.

    BTW, if your sequencer crashes that often, that´s not really a good sign, I´m afraid....

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • last edited
    last edited

    @Paul said:

    BTW, if your sequencer crashes that often, that´s not really a good sign, I´m afraid....

    No, it's just Cubase5, it crashes often, especially when switching projects. Can't really do much about it.

    A workaround right now is to disconnect VEPRO before switching projects. So if C5 crashes, you just reopen it again.