stemdeckapp/stemdeck

[!IMPORTANT]
macOS first launch (no code signing yet). After dragging StemDeck to Applications, clear the Gatekeeper quarantine flag or macOS will say the app is damaged:

xattr -dr com.apple.quarantine /Applications/StemDeck.app

Optional: start from a clean slate. To reproduce a true first-run experience, open each path in Finder via the Go menu, then Go to Folder (Shift+Cmd+G), and move the folders to Trash:

• ~/Library/Application Support/StemDeck
• ~/Library/WebKit/app.stemdeck.desktop
• ~/Library/Caches/stemdeck
• ~/Library/Caches/app.stemdeck.desktop

You can also delete ~/Library/Preferences/app.stemdeck.desktop.plist the same way. This is optional; the app will work without it.

What's new in 0.8.0 Alpha 6

Exact loop points (type in start / end)

The loop region could only be set by dragging on the timeline, which is hard to make frame-accurate for practicing fast phrases or transcribing.

• Two editable time fields now sit next to the loop button in the transport bar. Type an exact start and end and the loop region and audio update live.
• Fields show mm:ss.mmm and accept either mm:ss.mmm or plain seconds (e.g. 12.48). Enter or click-away commits; Escape reverts.
• Drag-to-select still works and now keeps the fields in sync as you drag. This is additive, for fine-tuning.

Persistent library on the self-hosted server

Running StemDeck as a self-hosted web server (not the desktop app) could silently delete processed tracks: a 24h job cleanup meant for shared/Docker deployments was left on, so older tracks turned into "audio no longer available" / out-of-sync entries after a restart.

• The self-hosted server (run.sh) now treats its library as persistent and user-managed, like the desktop app: processed tracks are no longer auto-deleted. Set STEMDECK_PERSIST_LIBRARY=0 to restore the old disk-hygiene behavior.
• The desktop app was never affected (its library was already persistent).

StemDeck on Unraid and Docker

StemDeck is now available as a prebuilt container image and in Unraid Community Applications, so you can self-host the web player without the desktop app.

• Image on GitHub Container Registry: ghcr.io/stemdeckapp/stemdeck. Tags: edge (rolling, rebuilt on every merge to main), latest (newest stable release), and X.Y.Z (pinned to a release).
• Unraid: search "StemDeck" in Community Applications and install. Map /app/jobs and /cache to persistent appdata paths; the library is persistent and user-managed by default.
• GPU: the image bundles CUDA-enabled torch, so it runs on CPU by default and uses an NVIDIA GPU automatically when started with --runtime=nvidia (on Unraid, install the Nvidia Driver plugin). No separate CUDA install is needed.
• File ownership: the container honors PUID/PGID, which the Community Applications template defaults to Unraid's nobody:users (99/100), so files written to appdata are owned correctly.

Installing

• macOS: drop the .app into Applications and launch (run the xattr command above first).
• Windows: unzip the downloaded .zip, then run StemDeck.exe from the extracted folder.
• Linux: download the .tar.gz for your hardware, extract it, and run ./StemDeck. Install the WebKitGTK + GTK runtime prerequisites first (FFmpeg is fetched automatically on first launch):

  sudo apt install libwebkit2gtk-4.1-0 libgtk-3-0
  

  The NVIDIA build additionally needs a working NVIDIA driver such that nvidia-smi reports your GPU (the CUDA runtime itself is bundled -- no separate CUDA toolkit install needed). If you have no NVIDIA GPU, use the CPU-only tarball.
• Docker / Unraid: install "StemDeck" from Unraid Community Applications, or pull ghcr.io/stemdeckapp/stemdeck:edge and map port 8000 plus the /app/jobs and /cache volumes. Add --runtime=nvidia for GPU acceleration. See the README for the full docker run command.

Artifact scan

• Windows portable packages (CPU + NVIDIA) scanned with ClamAV in CI before upload.
• Linux portable packages (CPU + NVIDIA) scanned with ClamAV in CI before upload.

Artifact build

• macOS arm64 and x64 DMGs and runtime packs built and inspected on a macOS runner before upload.
• Windows portable ZIPs (CPU + NVIDIA) built on a Windows runner.
• Linux portable tarballs (CPU + NVIDIA) built on a Linux runner.