Skip to content

0.11.1

Choose a tag to compare

View all tags
@thcp thcp released this 17 Aug 21:35
· 29 commits to main since this release
v0.11.1
1d537a7

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.11.1

A patch release: the macOS setup wizard's "Checking FFmpeg" step - reported broken by multiple users in different regions (#388) - now has a real second source, fails fast instead of hanging, and tells you what actually happened instead of dumping raw curl output.

StemDeck is still alpha. A leading 0. means no stability promise.

FFmpeg setup no longer has a single point of failure

  • A second, CDN-backed source. macOS FFmpeg came from exactly one host, evermeet.cx, with no fallback - the same problem Windows already hit and fixed a few releases ago by moving off its own single mirror. It's now the fallback only; the primary is a per-architecture build served from GitHub Releases, which is what actually fixed this for Windows too.
  • Fails in ~20 seconds instead of ~75+. There was no connection timeout, so an unreachable host meant a long, silent hang before setup gave up - exactly what #388's report showed.
  • Retries automatically for connection-class failures (a flaky network, not a fully blocked one) before giving up.
  • A readable error, not a raw curl dump - and it now correctly says "FFmpeg" instead of a copy-pasted "runtime pack" from an unrelated download path.
  • A documented way around it, if your network genuinely can't reach the download host: the setup screen now points at the STEMDECK_FFMPEG_URL override that already existed but was never surfaced anywhere.

Under the hood

  • The four new pinned checksums were verified independently before shipping: downloaded fresh, hashed locally, cross-checked against the upstream project's own published checksums, and confirmed as valid binaries by their file signature - not just trusted from a webpage.
  • Added an on-demand real-macOS compiler check to the project's CI. Until now nothing had ever type-checked the macOS-only parts of the desktop app before merging; this fix itself was verified against it before release.
  • None of this is visible in the app. It exists so the fix above stays fixed.

Notes on the beat detection model

Unchanged, repeated here for anyone upgrading from an older release:

  • The first time you use the click track, StemDeck downloads a 77 MB beat-detection model (MIT licensed, code and weights). It is cached alongside the Demucs models, so this happens once.
  • If that download is unavailable, for example on a machine with no internet, detection falls back to the classic librosa tracker automatically. The click still works; it is just more likely to pick half or double tempo on fast material, which /2 and x2 correct.
  • Known limitation: tracks whose time signature changes bar to bar, such as odd-time progressive material, get a usable steady pulse but the bar accents will not follow the written meter. No current beat tracker handles that automatically. The grid editor is the way to fix it by hand.
  • Tracks with no drums fall back to detecting on the full mix and are less reliable.
Assets 16
Loading