3 ms·
Sadly the performance limitations of doing serious work in the browser seem to be holding back web-based DAWs. I'd love to see a set of bindings come out that
by superb-owl 4y ago
Sadly the performance limitations of doing serious work in the browser seem to be holding back web-based DAWs.
I'd love to see a set of bindings come out that allow us to build web DAWs with the WebAudio API, but utilize native C/C++ when run locally via e.g. Electron
- rutierut 4y agoWASM and WebGPU do help a lot. WebAudio is still severely limited though.
- antidnan 4y agoAre there any projects using WASM for DAWs?
- jcelerier 4y agoIt's still alpha but https://ossia.io/score-web https://ossia.io/score-web is the whole https://ossia.io https://ossia.io (C++ / Qt) compiled to WASM. I haven't implemented file import at all yet though and there are enough UI bugs and latency / performance is too poor to make this nothing more than a fun but useless experiment... but it'll come as soon as I have some time to spend on it :-)
- capableweb 4y agoNot sure how much WASM would help, except for very complicated effects and/or sound generators. It would introduce latency as JS<>WASM still needs to communicate since you can't play audio directly from WASM. The problem with DAWs in browsers is more around latency and precise timing, which browsers don't exactly excel at compared to desktop applications.
- p0nce 4y agohttps://www.webaudiomodules.org/ https://www.webaudiomodules.org/
- stevehiehn 4y agoThis is very interesting thanks!
- stevehiehn 4y agoAgreed, I'm trying to work the angle where you quickly arrange loops and midi then download a bundle to import into your favorite desktop DAW.