Open CoffeeCoder1 opened 1 year ago
How many commercially available keyboards are using that protocol?
I don't know if there are any commercially available keyboards (I think the Behringer X-Touch and some similar devices might support it, but I don't know of anything that would be very good for controlling GrandOrgue), but it would make developing software and hardware to control GrandOrgue much easier.
OSC might work well as a protocol to use for #1563, as it is very audio focused and it is already supported by many control softwares.
How many commercially available keyboards are using that protocol?
This is not about keyboards, it's more about control surfaces (Android/iOS devices) and other programs tht need to control GO.
This is not about keyboards, it's more about control surfaces (Android/iOS devices) and other programs tht need to control GO.
Then it basically, as far as I'm concerned, falls outside the primary scope of what GrandOrgue is supposed to be!
An Open Sound Control API would allow for easier control over GrandOrgue from software like Open Stage Control and custom built control software and hardware. Open Sound Control supports more data types than MIDI allowing for more complete control over software (and making sending text much easier than it is with MIDI), and parameters have paths instead of identifying numbers (instead of controller 1 on channel 1 to toggle stop 1 it might be
/stops/1/enabled
) which gives more flexibility and would allow for there to be a standard API which would have no configuration on the GrandOrgue side.