Folder Disable/Enable automation

[stuartbeattie]

I recently bought VEP 7. Amazing software!

The marketing video suggested that folder disable/enable functions would be automatable. Doesnt seem to be the case. Do you have plans to add this in a future release?

Thanks,

Stuart

[stuartbeattie]

Automatable folder selection would also be useful.

[Digi_Joe]

+1

Paul, could you please pursuade the Devs to fix that quickly. You could click "learn" and then diable a folder but VEP only safes the disable for the first plugin in that folder. That is quite painful in large templates. And since the folder button is doing exacly what we need, that could not be so much effort to fix :)

Thanks an BR

Joe

[stuartbeattie]

Would be great if this could be implemented guys. Are you able to give some indication as to when support for this will be added? It's advertised on the VEP 7 feature list (still there as "Folder disabling (automatable)" and was one of the reasons I paid for the upgrade. Thanks, Stuart

[Paul]

Hi,

I checked with our development team about the current state of affairs, and circumstances changed quite a bit during development after release, so I'm afraid we currently cannot offer folder automation, for technical reasons.

We’ll see what is possible for a future update, but for now I have also removed it from the product page. Sorry for the inconvenience, we definitely have it on our list.  

Best,
Paul

[stuartbeattie]

Thanks for the update Paul. Stuart

[Jaybee]

+1 for this as soon as possible please. I upgraded yesterday from VEPro 6 and Folder Automation was high on my list of needs.  I spent a couple of hours trying everything last night following the instruction manual and then gave up. The folders have no "disable" automation available. 

Could I respectfully ask that if this feature is going to be a while coming you change page 46 of the VEPro 7 manual to state this feature is not yet working? It would save a lot fo people who are picking this upgrade up on BF sales a lot of time (and you a lot of support Qs I'm sure!). 

Other than that, appreciate all the new developments! 

Thank you. 

@Paul said:

I'm afraid we currently cannot offer folder automation, for technical reasons.

[Paul]

Hi Jaybee, 

Sorry that I overlooked this in the manuals. Will correct it asap. 

I'm afraid that folder enable /disable will not be available anytime soon, for technical reasons, and I hope you can manage with channel and instance disabling. 

Best, 
Paul

[Jaybee]

@Paul said:

 I hope you can manage with channel and instance disabling. 

Best, 
Paul

Yes, the Instance disabling is a huge bonus, I'll wait for the icing of folder disabling later on... 😊 

Thanks!

[MikeC]

Did this ever get addressed? Is it likely to arrive anytime soon?

Thank you!

[Paul]

Hi MikeC, 

This was not addressed, we had to remove this feature for technical reasons. 

Best,
Paul

[MikeC]

Thanks Paul, and sorry to be annoying, but the second part? Is it something that is simply impossible forever? Or might it be the sort of thing that might be possible to include in future updates?

I'm asking because I think I probably have around 1,000 VST instruments in my template, and enabling/disabling each one (especially because it's not currently possible to copy over the automation) is going to take a big old chunk of time and I would rather sit tight for a bit if it were theoretically possible. I know it's often hard to answer these questions (and maybe you're working on a smarter solution than this anyway!) but I'd be grateful for any info you feel you can share.

Thanks so much!

Mike

[Paul]

Hi Mike, 

Help me out on a saturday night: What is the second part? Copying automation parameters?

Best, 
Paul

[MikeC]

Of course Paul! (sorry it's now Sunday morning but I hope it's helpful nevertheless ;-))

I meant that, for every instrument I have in my template, I have to manually create a mapping command (CC121 in my case) which enables/disables the instrument. I currently (unless I've missed something and if I have please tell me!) have to create an individual routing command manually for every single instrument I have in my template. There are no shortcuts or ways to achieve this any faster - it's all got to be done individually.

Hence my original question really - I organise all my libraries into folders (VSL Synchron Woods for example) and while there are still a lot of folders it's more like 50-100, rather than the 1000+ individual insturments I have. 

Because I'm rarely using every instrument I own in a given cue (who is?) being able to activate and deactivate instruments is a fantastic feature, (even when purged kontakt instruments use a lot of RAM for example) but currently the amount of time it will take to set it up is prohibitive. 

I hope that was helpful, more than happy to provide any further info!

Mike

[Paul]

Hi Mike, 

Got it. Yes, I'm also waiting for more comfortable ways to set this up. 

I will talk to our developers - pretty busy times ahead, but maybe they can squeeze such a feature in. Can't make any promises there. 

Best,
Paul

[MikeC]

OK, thanks Paul. At the moment it looks like a deactivated Cubase template might be the best option, but I'd rather stick with VEP for a whole host of other reasons, so that'd be great if it happened. 

Thanks for the info!

Mike

[Macker]

Not sure how actual automation of folder enable/disable would be much use in any real-time situation; I seriously doubt if I'd ever try to use such a facility. But I'd most certainly welcome the ability to assign a good old-fashioned MIDI CC for manual remote control of any one or more folder enable/disable buttons.

[Paul]

Hi Macker, 

You could use MIDI CCs to disable instances and channels already. Maybe that helps?

Best, 
Paul

[Macker]

Paul, yes already have lots of instrument and instance enable buttons assigned to a couple of momentary buttons (both on the same assigned MIDI CC, one high value, one low value) on my keyboard. But anyway thanks very much for your support, it's much appreciated.