ArrayArrayArrayArrayArrayArrayArrayArrayArray BrainModular BrainModular Users Forum 2010-06-26T18:50:19+02:00 https://brainmodular.com/forums/app.php/feed/topic/2258 2010-06-26T18:50:19+02:00 2010-06-26T18:50:19+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14422#p14422 <![CDATA[how to make a gui element automatable?]]>
Thanks for that !

Statistics: Posted by multiphone — 26 Jun 2010, 18:50

]]> 2010-06-26T09:07:05+02:00 2010-06-26T09:07:05+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14418#p14418 <![CDATA[how to make a gui element automatable?]]> From now all controls created in Usine will be midi-learn enabled what ever their location.

Statistics: Posted by senso — 26 Jun 2010, 09:07

]]> 2010-06-26T02:09:45+02:00 2010-06-26T02:09:45+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14416#p14416 <![CDATA[how to make a gui element automatable?]]> Statistics: Posted by woodslanding — 26 Jun 2010, 02:09

]]> 2010-06-23T23:22:47+02:00 2010-06-23T23:22:47+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14362#p14362 <![CDATA[how to make a gui element automatable?]]>
and finally , you maybe don't find a bug but a workaround ...:)

Statistics: Posted by nay-seven — 23 Jun 2010, 23:22

]]> 2010-06-23T23:15:31+02:00 2010-06-23T23:15:31+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14360#p14360 <![CDATA[how to make a gui element automatable?]]>

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

Statistics: Posted by NaN — 23 Jun 2010, 23:15

]]> 2010-06-23T23:08:00+02:00 2010-06-23T23:08:00+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14359#p14359 <![CDATA[how to make a gui element automatable?]]>
maybe you can try to reproduce it in a simple patch and upload it or make a clear screenshot..?

Statistics: Posted by nay-seven — 23 Jun 2010, 23:08

]]> 2010-06-23T22:55:04+02:00 2010-06-23T22:55:04+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14358#p14358 <![CDATA[how to make a gui element automatable?]]>
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

Statistics: Posted by NaN — 23 Jun 2010, 22:55

]]> 2010-06-23T22:45:17+02:00 2010-06-23T22:45:17+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14357#p14357 <![CDATA[how to make a gui element automatable?]]> if yes, just link it to an oher fader in the main patch , will work...

Statistics: Posted by nay-seven — 23 Jun 2010, 22:45

]]> 2010-06-23T22:19:57+02:00 2010-06-23T22:19:57+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14356#p14356 <![CDATA[how to make a gui element automatable?]]> 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

Statistics: Posted by NaN — 23 Jun 2010, 22:19

]]> BrainModular BrainModular Users Forum 2010-06-26T18:50:19+02:00 https://brainmodular.com/forums/app.php/feed/topic/2258 2010-06-26T18:50:19+02:00 2010-06-26T18:50:19+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14422#p14422 <![CDATA[how to make a gui element automatable?]]>
Thanks for that !

Statistics: Posted by multiphone — 26 Jun 2010, 18:50

]]> 2010-06-26T09:07:05+02:00 2010-06-26T09:07:05+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14418#p14418 <![CDATA[how to make a gui element automatable?]]> From now all controls created in Usine will be midi-learn enabled what ever their location.

Statistics: Posted by senso — 26 Jun 2010, 09:07

]]> 2010-06-26T02:09:45+02:00 2010-06-26T02:09:45+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14416#p14416 <![CDATA[how to make a gui element automatable?]]> Statistics: Posted by woodslanding — 26 Jun 2010, 02:09

]]> 2010-06-23T23:22:47+02:00 2010-06-23T23:22:47+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14362#p14362 <![CDATA[how to make a gui element automatable?]]>
and finally , you maybe don't find a bug but a workaround ...:)

Statistics: Posted by nay-seven — 23 Jun 2010, 23:22

]]> 2010-06-23T23:15:31+02:00 2010-06-23T23:15:31+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14360#p14360 <![CDATA[how to make a gui element automatable?]]>

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

Statistics: Posted by NaN — 23 Jun 2010, 23:15

]]> 2010-06-23T23:08:00+02:00 2010-06-23T23:08:00+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14359#p14359 <![CDATA[how to make a gui element automatable?]]>
maybe you can try to reproduce it in a simple patch and upload it or make a clear screenshot..?

Statistics: Posted by nay-seven — 23 Jun 2010, 23:08

]]> 2010-06-23T22:55:04+02:00 2010-06-23T22:55:04+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14358#p14358 <![CDATA[how to make a gui element automatable?]]>
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

Statistics: Posted by NaN — 23 Jun 2010, 22:55

]]> 2010-06-23T22:45:17+02:00 2010-06-23T22:45:17+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14357#p14357 <![CDATA[how to make a gui element automatable?]]> if yes, just link it to an oher fader in the main patch , will work...

Statistics: Posted by nay-seven — 23 Jun 2010, 22:45

]]> 2010-06-23T22:19:57+02:00 2010-06-23T22:19:57+02:00 https://brainmodular.com/forums/viewtopic.php?t=2258&p=14356#p14356 <![CDATA[how to make a gui element automatable?]]> 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

Statistics: Posted by NaN — 23 Jun 2010, 22:19

]]>