One of the best things about Artillery is the modulation section - the lfo's and envelopes and such for the effects. However I'm disappointed that these are not exposed for host automation. This also means they are not visible for host based parameter control, like with Ableton's instant mapping and mapping to Kore's macro knobs.
Am I missing something? This seems like a crucial matter. I was pleased to see that the effectrix on/off buttons were made visible to the host, could the same be done for Artillery's mod controls? This is an essential thing for live performance and Artillery is otherwise suited for live performance except for this.
Cheers
Artillery 2 - Can't automate mod parameters?
-
Echoes in the Attic Echoes in the Attic https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=180417
- KVRAF
- 12036 posts since 12 May, 2008
-
Echoes in the Attic Echoes in the Attic https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=180417
- KVRAF
- Topic Starter
- 12036 posts since 12 May, 2008
Yes I am aware that they are midi assignable. As I said, I am talking about the controls being being visible to the plug-in host. I suggest to re-read my thread.AKJ wrote:controls are assignable via midi learn. I suggest to read the manual.
It is becoming more common to use control surfaces which really on parameters being exposed for host automation. For example assigning controls in novations automap, or assigning controls to knobs in NI Kore, or configuring controls from plug-ins to Ableton live devices and racks or various other DAW based parameter learning. This type of control surface is much more useful and versatile.
In Artillery, the controls like filter cutoff, res etc. are exposed, however mod amounts and mod controls like lfo speed are not. At the very least the mod amounts should be.
Thanks
-
- KVRian
- 1339 posts since 27 Apr, 2007
Well this is a problem about the maximum number of parameters a plugin should expose to the host. Note that with 128 possible effects with 5 parameters and each with an own modulator with 5 knobs you get 128*5*5=3200 controls.
I remember that especially Live had problems with more then 128 parameters. (not sure if this still counts) So this was the reason we left it out initally. Nowadays i think the better way would maybe to let the user exactly choose the parameter he wants to expose(although this would break the easy workflow).
Unfortunatly this change is not easy to do (without breaking existing projects), but i am thinking about it and noted it.
Best,
Robert
I remember that especially Live had problems with more then 128 parameters. (not sure if this still counts) So this was the reason we left it out initally. Nowadays i think the better way would maybe to let the user exactly choose the parameter he wants to expose(although this would break the easy workflow).
Unfortunatly this change is not easy to do (without breaking existing projects), but i am thinking about it and noted it.
Best,
Robert
-
Echoes in the Attic Echoes in the Attic https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=180417
- KVRAF
- Topic Starter
- 12036 posts since 12 May, 2008
Thanks Robert. I can definitely understand why it is the way it is.
Yes Live used to only be able to access the first 128, but now you chose the order of the plug-in parameters in Live 8 and if there are more than 128, you specify which ones you want available. So I don't think it would be a problem if they are all exposed, at least not in Live.
But if that would be a problem with other hosts, then I think it's also a good option to allow the user to chose the mod parameters to expose. And I don't think that would break the easy workflow, as it would only be used if needed. A good way is the way Omnisphere does it, where you right-click and chose 'enable host automation' just like how you would midi learn the controls.
cheers
Yes Live used to only be able to access the first 128, but now you chose the order of the plug-in parameters in Live 8 and if there are more than 128, you specify which ones you want available. So I don't think it would be a problem if they are all exposed, at least not in Live.
But if that would be a problem with other hosts, then I think it's also a good option to allow the user to chose the mod parameters to expose. And I don't think that would break the easy workflow, as it would only be used if needed. A good way is the way Omnisphere does it, where you right-click and chose 'enable host automation' just like how you would midi learn the controls.
cheers