Soundcraft-web
SoundCraft is an open-source digital audio workstation (DAW) for recording, editing, and mixing multitrack audio that runs natively on macOS, Windows, Linux,…
Platform availability
Available on 4 of 9 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
72/100 Good
- Maintained
- 82last commit 0 days ago
- Popular
- 724,078 GitHub stars
- Easy to install
- 504 install platforms, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
No GitHub repository data collected yet.
Resources & Compatibility
Requirements not published yet.
Checked today - source: Docker Hub image tags and published docs
First-install notes
- Run the web files with a small local server Open a terminal in the folder containing the SoundCraft web files, then run `python3 -m http.server 8765` to start a simple local page server if your system has Python. After it starts, open http://localhost:8765/ to use the app on the same computer. source
- Install the native desktop app Download the latest build for your operating system (macOS, Windows, or Linux) from the GitHub releases page and install it to run the app natively. No container or web server is required for this installation path. source
Fetched today - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which official release does the self-hosted web build use?
The self-hosted web build is based on the official v0.13.1 release. It is described as an unmodified static WebAssembly build from the official release zip.
Does the self-hosted server need to process audio for playback?
No, the WebAssembly build is documented as running in the browser. The repository does not describe it as a server-side audio processor.
Are plug-in settings retained in a Soundcraft session?
Yes, Soundcraft saves CLAP, VST3, and Audio Units plug-in state in the session. Each plug-in instance also has its own editor.
Answers sourced from github.com, github.com
Community
Collected today - public community threads