Hello All,
I’m experimenting with the new Canvas feature and trying to create a button that arm/disarm a track. Since i can’t get the arm state from Ableset I’ve installed AbletonOSC. I can easily send values but I’m hitting a brick wall when it comes to receiving values.
As a specific example, i need to read a track’s armed state in order to set the button color as gray or red. Any help is greatly appreciated!
Hey @RichardB,
That’s an interesting topic and one that I’m working to improve the UX of at the moment. To get a value from AbletonOSC, you can add a new OSC connection from the OSC page:
Then set it up to send to port 11000 and listen on port 11001, and add a command to automatically start listening to the arm state of the track you’d like to work with. For example:
You can replace the 0 with the index of your track. With the current beta, you might have to restart AbleSet or run the command manually from the OSC testing tool or the canvas so AbletonOSC receives it.
Once AbleSet has received a response from AbletonOSC, it will be available as a variable:
The only issue with AbletonOSC at this time is that it sends all values of a property for all tracks to the same OSC address, with the first parameter being the index of the track and the 2nd one being the value, so AbleSet can currently effectively only access the value of one track.
To use the value in a template, you can access it like this:
${osc(":AbletonOSC/live/track/get/arm", 1)}
This returns the 2nd parameter of the OSC address which is the value of the property you requested.
I’ve opened a request for improving AbletonOSC’s API so it’s more compatible with AbleSet: Proposal for API change · Issue #163 · ideoforms/AbletonOSC · GitHub
If this doesn’t work, I might start a fork which sends the values for each track to a different OSC address so they can be used in AbleSet.
Let me know if this helps! 
Hey @leolabs! I thought i had responded but i don’t see it here in the thread. Thank you so much and this solution will work perfectly!
