WebAssembly / WebAssembly/tool-conventions
audio/MIDI/CV graph functionality?
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 372
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
would/could these conventions provide the abstractions/system to supply the features of an audio graph?
as in, that could be used to connect audio/MIDI/CV consuming/producing web tools
such a system would enable not just an audio effects rack style flow, but actual in-browser intra-tool modular synthesis, say, between Cardinal and other such apps
if CV streams are a new one to anyone, they're part of the JACK/PipeWire API and the LV2 plugin format
fwiw fyi, the JACK and LV2 systems have a client/port metadata system that is likely worth looking at, in this regard
Carla, set to multi-client mode (system wide audio graph, not separate internal/external graphs), exposes LV2 plugins it hosts as JACK clients in their own right, using the appropriate plugin metadata as properties for the JACK port type, name, pretty-name, etc.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the JACK API, LV2 plugin format, and the cited Carla multi-client behavior, then compare them with the conventions used by this repository. Define the scope and abstractions needed for interoperable audio, MIDI, and CV graph connections; done requires an agreed design rather than a single implementation change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100