Nick Suda

I'm trying to dynamically construct a modular UI based on certain devices added, deleted or moved in a channel.

These UI modules use live.dial objects which need to have their ranges, automapping indices, etc. set upon creation via JavaScript.

Currently, all of these features are not remotely addressable. They say "(hidden)" in the Inspector, and the only way to change them is from manual input in the Inspector.

I realize that the ability to change a parameter's automatability and its index potentially opens up a huge can of worms - maybe just leave those behind for now. But, still, there's no reason why I can set the Value attributes of a dial remotely, adjusting its @min and @steps and such, but I can't do this with a live.dial.

I'm trying to dynamically construct a modular UI based on certain devices added, deleted or moved in a channel.
These UI modules use live.dial objects which need to have their ranges, automapping indices, etc. set upon creation via JavaScript.
Currently, all of these features are not remotely addressable. They say "(hidden)" in the Inspector, and the only way to change them is from manual input in the Inspector.

I realize that the ability to change a parameter's automatability and its index potentially opens up a huge can of worms - maybe just leave those behind for now. But, still, there's no reason why I can set the Value attributes of a dial remotely, adjusting its @min and @steps and such, but I can't do this with a live.dial.


feature-request-expose-parameter-attributes-of-ui-objects-to-scripting

There is a trick, in the inspector in the "modify attribute" menue, you can copy the atribute you want. Then paste it into a textedito or a message box to see how its called. Example attached. But as you say, might be a can of worms, especially inside Ableton Live..

There is a trick, in the inspector in the "modify attribute" menue, you can copy the atribute you want. Then paste it into a textedito or a message box to see how its called. Example attached. But as you say, might be a can of worms, especially inside Ableton Live..
Hope that helps a bit, cheers!


Holy crap, that's totally it! Thank you so much!

Wow, so they are completely addressable. I wonder why they're hidden, then?

Holy crap, that's totally it! Thank you so much!
Wow, so they are completely addressable. I wonder why they're hidden, then?


how did you know what the names of these "hidden" parameters are?

for example, I'd love to achieve exactly the same thing with the "automapping index" but I cannot see what the parameter name is for it.

how did you know what the names of these "hidden" parameters are?
for example, I'd love to achieve exactly the same thing with the "automapping index" but I cannot see what the parameter name is for it.


In the bottom of the inspector, click the @ button. This will display the scripting name of every attribute; many will be (hidden). If they are hidden, try clicking the + button, which will create an [attrui] object revealing the scripting name.

Feature request - expose Parameter attributes of UI objects to scripting