what? the web audio api is incredibly robust and performant. there is certainly no cap on voices besides memory constraints. writing your own audio engine in wasm would certainly not provide any advantage.
also all the use of tables + odd/broken styling on the page are red flags
This is very obviously generated by ChatGPT. Sigh.
The javascript bridge including threading bottlenecks are never going away.
It would be faster to put Java Applets back into browsers, including implementing a new sandbox.
Thank you ChatGPT!
was this written by ai?
> Audio Processing | Basic effects, limited voices | Complex DSP, many simultaneous sources | 150-400%
what? the web audio api is incredibly robust and performant. there is certainly no cap on voices besides memory constraints. writing your own audio engine in wasm would certainly not provide any advantage.
also all the use of tables + odd/broken styling on the page are red flags
AGI is here guys