Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: The blue hand #110

Open
Coupe70 opened this issue Jan 7, 2024 · 1 comment
Open

Request: The blue hand #110

Coupe70 opened this issue Jan 7, 2024 · 1 comment

Comments

@Coupe70
Copy link

Coupe70 commented Jan 7, 2024

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.

@ideoforms
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants