Is there a way to assign this as a global parameter? So that in my DAW, when I select a track and press the assigned button, it'll disable/enable whichever track is selected. At the moment, it's only applying to any instances that I've manually set it up on.

Does anyone know a way to automate it globally so it's not on a per instance basis?

Anyone?

Hi, 

I can't think of a way to do that, it needs to be assigned on a per instance basis, using VE PRO automation. 

Best, 
Paul

@noiseboyuk said:

Running VE Pro with all channels purged is a possible way forward, and in Cubase i could in theory combine this with Cubase's midi transformer, so that all notes played also send out a CC message which VE Pro uses to enable the appropriate channel.  I've tested the theory and it works beautifully.

Except these automation parameters require setting up on every single midi channel on every single instance in VE Pro.  Worse, there is no way of saving or loading automation presets, or copying a configuration between instances.  Its literally a case of clearing a weekend and doing it manually, one by tortuous one.  I'm not sure if my sanity can handle it.

So I have two feature requests - one or other would do.  First, the ability to save / load / copy automation parameters.  Second - and this would be the dream ticket - a setting in VE Pro to enable a channel on any midi note on that channel (wake on midi).  That small checkbox woulld be revolutionary in terms of workflow.

+1000!! Running into the same issues here. Did you ever figure out a solution NoiseBoyUK or did you abandon all hope?

Hi, 

Thanks a lot for your input.

Such a feature is on our check-list after the Synchron Strings I and Synchron Player has been released, along with quite some other improvements. 

For VI/VI PRO, a very convenient approach to save RAM can be achieved by using either the Optimize function or loading cells on MIDI Activity (in the VI/VI PRO Settings). 

Best, 
Paul

@Paul said:

Hi, 

Thanks a lot for your input.

Such a feature is on our check-list after the Synchron Strings I and Synchron Player has been released, along with quite some other improvements. 

For VI/VI PRO, a very convenient approach to save RAM can be achieved by using either the Optimize function or loading cells on MIDI Activity (in the VI/VI PRO Settings). 

Best, 
Paul

Yeah, Thankfully your development team is smart enough to program this functionality directly in VI Pro, but unfortunately I'm needing ram savings for Kontakt & EW Play libraries. Going to use Purge in Kontakt & play for now and hope that will work instead (will cause more RAM in unused libraries due to GUI, etc which I was hoping to avoid).

Hopefully the idea of automatically loading a channel when midi notes are played on that channel can be implemented (exactly like you have done with disabled cells in VE pro) as its a really great feature to have. 

BTW I already preordered Synchron Strings as I have full confidence in VSL and its products. You guys truly are the best in the business and I really look forward to using this library! 

@Paul said:

Hi, 

Thanks a lot for your input.

Such a feature is on our check-list after the Synchron Strings I and Synchron Player has been released, along with quite some other improvements. 

For VI/VI PRO, a very convenient approach to save RAM can be achieved by using either the Optimize function or loading cells on MIDI Activity (in the VI/VI PRO Settings). 

Best, 
Paul

This was very encouraging to read - are we closer to this feature being available?  Many thanks.

+1. I've spent ages on this and can't get it working. It's the main thing that's pushing me towards building a Logic Template without VEPro. I really don't want to do that though.

Has there been any progress here folks? I'm currently setting up a huge Reaper template and would like to map the track freeze channels to corresponding instruments in VEPro.

I hope there will be a better solution in VEPro 7 as soon as it's available.
We have just to wait a little longer...

Bump 2022 (Wishlist):

• Assign Enable/Disable Channel as a global parameter.

If this isn’t doable, and since the midi controllers automation map seems to only get saved with Server Projects (vesp64):

• Save the midi controllers automation map with Projects (vep64).

• Option to save the midi controllers automation map with Channel Set.

• Feature: Save a midi controllers automation map with empty destinations.