yeah! althoug the new build is much better for logic users and "decouple" makes even work at all - please implement a dsconect buttom in the server window!! I also requested it via email. Pleaseeeee do!!!!! :-))

THX Dan

I'd like to add my vote for this one, a disconnect function would be great.

Same here, one more vote for a disconnect button!

Yes, I strongly add my vote to this request. This is our top headache right now. VEPro is such a fabulous piece of software, but when DP crashes some of our VEP instances still think they are "connected" even though we run them "decoupled". As a result, when we relaunch the DP project it won't connect to the "already connected" VEP instances and it requires us having to close VEPro and reload the palette which is a 15-20 min ordeal.

It would be wonderful to have a button that forces VEP to disconnect without having to close the instance so that in the event of a DAW crash, it doesn't require a complete VEP reboot of all the slaves.

Thanks!!

+1

+1 here as well

Hi everybody,

this feature is already on our to-do-list and we hope that it will be integrated in the next major update of VE PRO.

Best,

Paul

Hi all,

I just put the "Force disconnect" feature when deleting an instance into VE Pro. It will appear in the next update.

Martin, that's good news. Does this mean that if the sequencer crashes and closes, the button will be on the server interface, or will we have to open each VE Pro instance and manually click all of them?

DG

This is handled from the VE Pro server window.

I am dying for this feature as well.  I have a slave computer that has 12gigs of ram and is loaded up with 11.3 gigs of samples basically covering a majority of my template.  It takes about 50 minutes to fully load my metaframe on this machine.

 My main machine is quite stable, however it does crash from time to time.  When it does, because I don't have a force disconnect feature on the server, I am forced to unload and exit that whole 11.3 gigs of samples which seems to take about 10 minutes to fully unload that metaframe without force quitting.  Loading that meta frame back up takes almost 50 minutes.  All of this just because we cannot manually disconnect projects when we want/need to.  I have at least 1 hour stolen from my day if I have a crash now.  I don't ANYONE that could deem that as acceptable.

I am a very busy composer and do NOT have time to reload my full orchestra every time my main machine has a crash.  This is the whole reason why I've went with VE Pro in the first Place!!!

 I also think that somehow connecting the force disconnect to the delete project function would do nothing to help this situation.  Think about it.....The whole point is that I do not want to have to delete or unload the VE Pro Projects when my Main Machine crashes.  I need to disconnect without deleting or unloading ANYTHING from my metaframe.

Thanks you all at VSL for your groundbreaking products.  I couldn't make music without you!

Best,

Matt Mariano

@mattzen said:

I am dying for this feature as well.  I have a slave computer that has 12gigs of ram and is loaded up with 11.3 gigs of samples basically covering a majority of my template.  It takes about 50 minutes to fully load my metaframe on this machine.

What? 50 minutes? I would look into this, if I were you. My template is about 24GB, and it takes about half an hour, and I don't have the fastest memory. I really don't think that it should take more than about 15 minutes for yours.

DG

Thanks for your reply DG.  My slave machine is a new i7 quad processor with triple channel memory under windows 7.  My metaframe is very complex but maybe it should load faster, however..... I believe that to be irrelevant to the core of this situation with all due respect.  

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.  Is there a technical problem that would prevent this from being possible?  if so, i would be curious as to what it may be.

Thank you!

-matt mariano

@mattzen said:

Thanks for your reply DG.  My slave machine is a new i7 quad processor with triple channel memory under windows 7.  My metaframe is very complex but maybe it should load faster, however..... I believe that to be irrelevant to the core of this situation with all due respect.  

Sorry, I didn't mean to derail the discussion, but I think there is something wrong with your system if it loads so slowly. If it is of any help maybe I could open the metaframe on my system (if we have the same Collections) and see how long it takes. Then we would know if it is the metaframe or your system. Send me a PM if i can be of any help.

DG

@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

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