From module to hardware
How the portable module model can extend to pedals and instruments.
Hardware support is upcoming. The design goal is to keep your audio module portable instead of asking you to maintain a separate patch for every device.
The durable boundary
Your module describes the sound, ports, parameters, state, and requirements. A device adapter supplies the audio driver, physical controls, installation, and platform-specific runtime behavior.
That separation lets the same named parameter connect to a web control today and a physical knob later without changing the module's authoring model.
Design for portability now
While hardware packaging is in development:
- keep public parameter IDs stable;
- declare channel, sample-rate, memory, and engine requirements clearly;
- decide which few controls are essential on a smaller physical surface;
- keep networking, file access, and hardware polling outside realtime audio.
Hardware targets will be documented when a device profile and installation path are verified. Until then, treat browser and supported native formats as the available product paths.
See How it works for the shared module model. Verified targets appear in the project and on individual module pages.