Browser audio editors expose their effects graphs and presets to anyone
Web Audio lets developers build full audio editors that run inside a browser tab, but everything the client can apply offline must be shipped to the page. Proprietary processors, worklet files, and preset tables for branded chains end up publicly fetchable, so minification and WASM do not truly hide them. The article argues that client-side plan checks cannot protect paid features and that official renders, paid preset packs, and unreleased chains should stay on a server. It suggests the browser can still handle trimming, coarse EQ previews, and uploads, with final processing returned by an entitled worker. Some on-device logic may remain where latency demands it, but anything there should be treated as downloadable.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in