Hi everyone, in a similar fashion to what we did for the original MOD Audio reboot at Reboot updates we want to have a dedicated forum topic to give updates on this phase 2 of the reboot.
If you haven’t read the official announcement regarding phase 2, please check MOD Reboot - Phase Two
Please note that in order to keep things on topic, no user comments are allowed.
So you can use this thread as single source of info.
Whenever there is a bigger post, or something that requires feedback, we will create that topic separately but still link it from this one.
We have renamed the GitHub organization from “moddevices” to “mod-audio” (the “modaudio” name was already taken). On the last reboot we were in the middle of some updates and had a very tight schedule, so we did not want to risk breaking anything by doing an organization rename at such crucial time.
Since we got a 2nd chance, the official GitHub org link is now https://github.com/mod-audio.
Another open-source tool, and now the full chain is open.
This is the tool that sits in between the controller/HMI and the Linux system, doing system commands and providing direct communication with mod-host for handling HMI Widgets.
Implementation for a generic buildroot mk file online builder is done
This is the first step, now we need:
Persistent storage (I am thinking a docker volume per target mounted to a path on the server)
Add checkbox to this buildroot generic builder to allow to build for duo, duox and dwarf at the same time
Create a special “store” page that lists the plugins that were built this way (or “hidden” page per build? would more complicated)
Add install step for that new “store” page
The first 2 are simple enough, the last 2 are more complicated.
There are many possible ways to do it, but I am tending towards a full “store” page with all plugins built so far, because that would be the simplest to do and also the one that provides more visibility for the community built plugins.
But that also means only 1 possible build per plugin, would not allow for custom specialized builds (tricky to support and would take some time to setup)
Will let you know once things proceed.
PS: We did not push these changes to the online builder yet.
Still related to the online builder, the puredata support (through hvcc) now supports uploading multiple files and then selecting which one is the “main” entry point.
Also there are MIDI options too, for generating synths or MIDI tools based on puredata.
I dont know much of puredata myself, @dreamer is the one leading the hvcc project for its integration with DPF and MOD.
We hope to create a “quick start guide” for this setup soon.
Also, the “generic” builder through a buildroot mk file is online now as well, though it is accessible only via builder.mod.audio/buildroot manually, as it is quite technical in nature (beyond stuff like faust, max-gen and puredata) and thus not useful for 99% of users.
very technical post