VEP5: possible to block connection from seq?

[Jeff Hayat]

Hi all :)

 

Is it possible to temporarily disable VEP5 from being connected to a seq while open?

 

Thanks in advance.

[Paul]

Hi Jeff, 

The most "disconnected" you can get is to "decouple". 

When decoupled, VE PRO stays available, but there is no data sent to the sequencer. 

Let me ask you this: Which effect would you like to achieve?

Best, 
Paul

[FredB]

I would use such feature if it exist.

In a situation where you whant to switch temporarely to another project without loading the VEP instance and then comeback to the first project. 

 

It would be nice if there was a feature that makes VEP act like it was closed.

[Jeff Hayat]

Fred: exactly.

Paul - and thanks for the reply - it's not that I am lookign for an effect. What I would like to do is this:

Load a new project, with my latest VEP mframe. Then, close that project, and open an old project, which was used in conjunction with an older VEP mframe - but I do not need the older VEP mframe to load. In fact, I want to keep the current (newer VEP mframe) loaded, so when I re-load the new project, the VEP mframe is already loaded.

Currently, the only way to do this, and to not get the older VEP mframe to load, is to exit out of VEP. If not, the older VEP mframe will load, and if the newer VEP mframe is open, the older one will load on top of it. Making things a bit sticky, if both together use 100 GB of RAM, while the system only has 64 GB installed.

Sadly, decoupling does not work here.

Cheers.

[Paul]

Hi, 

Thanks for the explanation. I´ll forward this to our developers, maybe we can add it to the wish-list. 

Best, 
Paul

[Jeff Hayat]

Thank you! :)