Thanks for sharing my project! Thank you for this space and I will bring some information about the project (I hope this is allowed in this forum):
Currently support is with mod-host, however it is possible in a short time to develop an observer to use another host, such as Carla, for example. Just extends UpdatesObserver (and implement the connection to the host).
If someone finds a bug, please report on issues. And if anyone is curious about development, check out the milestones.
I am available to answer questions. Even I think it’s cool so I can improve the documentation
I do not have an official channel for this. Can anyone suggest me one?
This project is part of another larger one: the Pedal Pi. It aims to enable users to assemble their equipment for audio processing. Something like MOD Duo (simpler, of course), but allowing a friendly hardware expansion. Exemplifying:
If a user wants to use mod-ui but wants to add footswitches to control the state of the plugins, he should make changes to the mod-ui itself or implement a system On the outside to consume the WebService that was not documented - as MODEP did.
On my system, I’m preparing you to accept this expansion through a documented API. This will allow developers to implement “components” and lay users choose which components to use and benefit from.
An example of a component is the Raspberry-P0, which allows the pedalboard to be exchanged for two footswitches. Note that I tried to write the Readme of the project so that it is simple for people to set it up.
Another component example is the WebService, which offers the project API as REST and WebSocket web services. It is documented.
Other components can be found in the Components list.