ideoforms
commented
10 months ago Yep, looks like this would be a Song property, appointed_device (from docs). Would need a bit of additional logic to allow the API user to specify the object path of the device (e.g., track 2 device 3) and vice versa.
When you select a device in Live it gets the blue hand symbol and the first up to 16 parameters of the device will be automapped to a MIDI controller if there is a remote script running for this controller. But the data to query is not exactly 'selected device', because you can lock the blue hand to a device, decoupling it from the selected device.
This would make it possible to have 16 faders in TouchOSC and always have the names and values of the selected device in access.
The data to query seems to be a song property called 'appointed device'. I would assume that it returns track number and device number. I don't think there are dedicated parameters like 'blue hand device parameter 1', instead you would use the already implemeted device calls to handle the device after finding out which one has the blue hand.
So this would "only" mean to implement get/set(?)/listen appointed device.