API-like support via OSC

[DerSpatz]

One request that comes up often is the support for external displays like smartphones etc. Another thing that was requested was some kind of Text-to-Speech (TTS) engine, which would be a great help for visually impaired musicians who want to use OTTO.

Both could be implemented by offering some kind of API which lets users control OTTO, but also gives feedback about what's happening on the screen.

With this API, users who want an external display could redraw the OTTO user interface on the external device from the external device's memory, and synchronize it to the actual OTTO. And users who want TTS could use an external device like a MCU or a smartphone to listen to the messages the OTTO is sending and generate spoken messages which they can use for information.

One solution for this API would be to integrate OSC (https://de.wikipedia.org/wiki/Open_Sound_Control) support. There's already a pull request for OSC support for the OTTO.

OSC relies on every parameter to have an exact name/address. So to have OSC support, we'd only have to make sure that there's a name/adress defined for every parameter, but besides that, the integration of external displays/controls or TTS would be independent from the main code base.