OpenDAW – a new holistic exploration of music creation inside the browser

Original Article ↗ Hacker News Discussion ↗

Open-source status & naming

  • FAQ says code will be opened later, after an MVP / standalone v1 and infrastructure for docs and contribution review are in place.
  • Several commenters find this rationale weak: “open” in the name without current source release feels misleading, and there’s suspicion it may never be opened if commercial success arrives first.
  • Others accept a delayed open-source release as reasonable, but still consider the messaging odd.

Browser/PWA vs native/Electron

  • Many are impressed it runs so fully in a browser; zero-install, cross‑platform access and easy onboarding are seen as big wins.
  • Skeptics question why everything must be browser‑based, citing performance “jank”, network dependence, unclear offline behavior, and awkward PWA UX.
  • Supporters note PWAs can be installable, chrome‑less, offline‑capable and close to Electron in capabilities, with better security and smaller footprint.

Latency and audio drivers

  • Big debate on whether a “real” DAW can live in the browser given low‑latency needs for live playing, tracking, and multitrack recording.
  • Some argue browsers lack ASIO/JACK‑class access and multichannel support, so serious recording/monitoring will suffer.
  • Others emphasize latency compensation, direct hardware monitoring, and DSP interfaces can hide much of this, especially for non‑live or education use.
  • Agreement that pro workflows (tight live monitoring, complex setups) remain challenging in a browser.

Plugins and ecosystem

  • Lack of VST support today is widely seen as a fundamental limitation; some compare it to a “car without wheels.”
  • Plans mention future VST in a native wrapper; in the browser, Web Audio Modules are suggested as a practical plugin standard with existing plugins.
  • Interesting contrast: people who complain about plugin scarcity on Linux are now excited by a platform with effectively zero VSTs.

Target audience & use cases

  • Unclear who it’s for: power users already have mature DAWs; beginners may find the UI too advanced; mid‑tier users and students are suggested as a likely target.
  • Education, low‑friction collaboration, and “toy‑to‑serious” exploration are recurring optimistic themes.

UX and learning curve

  • Long subthread critiques DAWs as engineer‑centric; desire for a musician‑first flow: plug in, auto‑detect instrument, hear effects immediately, record takes without setup overhead.
  • Others counter that DAWs inherently push musicians toward engineering concerns; complexity and multiple roles (musician/engineer) are hard to avoid.
  • Ideas raised: “musician mode” vs “engineer mode,” simple voice or natural‑language operations, and better onboarding rather than more knobs.

Technical notes & related tools

  • Safari support is currently broken (missing JS feature); works in Firefox/Chromium.
  • Connections are drawn to earlier browser DAWs like Audiotool (by the same creator), and to existing open‑source or commercial DAWs (Ardour, Bitwig, Reaper, Bandlab, etc.) as reference points.