Multi Script Automation

It would be great to have host automation available for all control devices on a multi script. Why? Because that way you could convert automation to midi CC. Some developers like orchestral tools do not provide host automation for everything. If I wanted to control e.g. the mixer of microphone positions for all instruments in my template via host automation, so that I have the ability to mix all instruments in parallel (which has obvious advantages!) I cannot do that for those instruments that only support midi CC.
I guess this ability to apply host automation to multi script controls could be useful in other context as well, but that was, where I especially missed it.

 

I doubt this is going to happen, unfortunately. Multiscripts haven't had anything added to them in a long, long while.

 

Alright, but can you see this as something being really useful? I guess multiscripts lack a little bit of attention since they are not directly related to developing patches, but they can help a lot with all sorts of template customization including, but not limited to the problem I described.
Other scenarios would be using multiple monophonic patches routed through a multi script to apply modulation parameters by note like you get with polyphonic pressure or Roli Seaboard (MPE), just do adress one issue that also got asked here. That is why I think people should not underestimate the power of multi scripts. ;-)
Thanks for sorting out my account activation, by the way. Cheers!

 

Actually, just FYI, this is incorrect. If a control is MIDI learnable, it can also be host automatable. You just have to assign that control (or those controls) to a host automation slot or slots yourself. The procedure for that is in the manual.

 

It is correct at least for one developer, which happens to be heavily used in my template, which is orchestral tools (capsule). All the controls are not learned by righclicking and learning a CC, but rather through a menu, where every parameter can be applied to a a CC. That is actually a good system, because you do not need to apply your settings for every patch separately, which would be a tedious task ... you rather apply your setting to one instrument and are able to import those settings for every other instrument.
That means, it is not possible to apply automation to these. Well, I guess it is more promising to wait for orchestral tools to update their libraries with automation enabled. As far as I understand, their Inspire 1 and 2 libraries have Komplete Kontrol support, which would suggest the need for automation capability (I do neither own these libraries, nor a KK Keyboard, so I am not sure ...).
Still, it would be great to have that feature, as it makes what you can achieve with automation more flexible in Kontakt.