how to make a gui element automatable?

NaN · Unread post by **NaN** » 23 Jun 2010, 22:19

I wonder why some knobs/faders can be automated with "Vst Parameter..." from the context menu and some not (for most this option is grayed out).
E.g. if I drag a fader from the browser into the patch then it is not automatable by default. ("Vst Parameter" is grayed out) while most faders in the Step Filter can be automated. I tried to recreate the settings of the fader that represents the "Q" parameter of the Step Filter, on first sight my clone has similar settings - just I have no chance to enable the automation.
If I copy'n'paste the original "Q" fader from the Step Filter then this copy is also automatable.

Which switch do I have to toggle for a gui element so that "Vst Parameter" is not grayed out anymore?

Greetings,
NothanUmber

nay-seven · Unread post by **nay-seven** » 23 Jun 2010, 22:45

maybe you fader is in a sub patch..?
if yes, just link it to an oher fader in the main patch , will work...

NaN · Unread post by **NaN** » 23 Jun 2010, 22:55

Hi,

Edit: The key factor seems to be that the fader was created at root level. Then I can cut and paste it into a sub module and it still works (just connecting with a main level fader did not do the trick in my case). That seems to be a small bug.

Thanks for helping!

Greetings,
NothanUmber

nay-seven · Unread post by **nay-seven** » 23 Jun 2010, 23:08

mm, sorry , maybe something i don't understand , cause can't reproduce the problem..?

maybe you can try to reproduce it in a simple patch and upload it or make a clear screenshot..?

NaN · Unread post by **NaN** » 23 Jun 2010, 23:15

sorry, edited my text presumably while you were writing your answer

The bug is easy to reproduce: Insert a submodule, add a fader inside it. Now most items (including "Vst Parameters" in the context menu of the fader are grayed out). Now cut the fader and insert it at the main level. (This enables all greyed out items). Afterwards cut it again and paste it back into the submodule. Now it works!

Thanks again for your tip with the main level, this lead to a viable workaround.

Greetings,
NothanUmber

nay-seven · Unread post by **nay-seven** » 23 Jun 2010, 23:22

ok, the most important for the moment is that it's work for you..

and finally , you maybe don't find a bug but a workaround ...

woodslanding · Unread post by **woodslanding** » 26 Jun 2010, 02:09

sounds like a bug AND a workaround!

YouTube · Unread post by **senso** » 26 Jun 2010, 09:07

this small issue will be fixed in the 5.18
From now all controls created in Usine will be midi-learn enabled what ever their location.

multiphone · Unread post by **multiphone** » 26 Jun 2010, 18:50

I just want to say : Woooaouuw !

Thanks for that !

Welcome to %s forums

how to make a gui element automatable?

Login • Register