Version 0.3 milestones

[atsushieno]

So far we had 3 big releases: v0.1, v0.1.4, and v0.2.0. Most features @atsushieno dreamed of for the first UAPMD idea (audio plugin based virtual MIDI 2.0 devices console) had already realized. We should move towards the next goals.

It is a high level summary to not describe individual minor tasks. It will be updated along with the project progress.

---

So far, many of the tasks were just copied from v0.2 milestones (leftover).

Design specifications

• annotate plugin hosting API with thread requirements (audio = realtime, non-audio, UI/main)
• design portable music project requirements (some have been described in our design docs)

plugin hosting and MIDI device hosting

• Android AAP format
• Windows MIDI Services integration
• scanner blocklisting
• out-of-process scanning (needs IPC foundation)

Sequencer engine and uapmd-app

• support for audio buses and side chains (likely requires fully featured DAG)
• latency reporting
• out-of-process audio engine (needs IPC foundation)

Scripting and automation

• design JavaScript object oriented API (like our C++ API) and define its scope
• provide instrumentation entrypoints and feedback outlet
• set up testing foundation (depends on instrumentation and most likely studiorack-cli CI availability)
• MCP server if we need more than instrumentation entrypoints

vFuture

• iOS AUv3 support
• WebCLAP (depending on the specification progress)
• ARA2 or ARA3 (depending on the specification progress)
• SMF2Container format (depending on the specification progress)