VibeSeq v0.1.0-alpha.11
Pre-releaseDesktop runtime validation prerelease
This unsigned prerelease is for clean-machine validation of the VibeSeq desktop runtime, local persistence, arrangement editing, playback, and export.
It embeds the Studio, Stable Audio 3 execution source, frozen real-model runtime, and the verified first-run model installer, so Node.js, Python, and uv are not required. Model weights are not included in the executable.
On every launch VibeSeq checks the current platform's exact Stable Audio files. If VibeSeq Data is absent, empty, incomplete, or missing a required file, the Inference readiness panel offers a resumable SHA-256-verified download after the model terms are accepted:
- macOS ARM64 MLX bundle: https://github.com/acidsound/VibeSeq/releases/tag/stable-audio-3-c2949a-macos-arm64
- Windows x64 TFLite bundle: https://github.com/acidsound/VibeSeq/releases/tag/stable-audio-3-c2949a-windows-x64
- Linux x64 TFLite bundle: https://github.com/acidsound/VibeSeq/releases/tag/stable-audio-3-c2949a-linux-x64
- MuScriptor Medium: https://huggingface.co/MuScriptor/muscriptor-medium
Only the Stable Audio model format for the running OS is downloaded. macOS and Linux store it below ~/VibeSeq Data/models; Windows stores it below VibeSeq Data/models beside the installed VibeSeq.exe.
MuScriptor remains gated and is not redistributed. Each user accepts its Hugging Face conditions, downloads the pinned config.json and model.safetensors in their browser, and places them directly under SAVE CACHE UNDER. That exact revision folder opens in Finder, File Explorer, or the Linux file manager. VibeSeq does not download, select, or move these files or request or store a Hugging Face token; Verify files in cache only validates the files already in that folder.
Powered by Stability AI.
Windows is distributed as a current-user assisted NSIS installer so extraction progress is visible and VibeSeq Data remains beside the installed executable. The installed app then shows Local data, Audio engine, Health check, and Studio startup stages while its local service starts. Windows SmartScreen and macOS Gatekeeper may warn because code-signing identities are not configured yet. On Linux, run chmod +x VibeSeq-*.AppImage before launching. Verify the downloaded asset with SHA256SUMS.txt before running it.