VibeSeq v0.1.1

VibeSeq 0.1.1

This unsigned release provides the VibeSeq desktop runtime, local persistence, arrangement editing, playback, and export.

It embeds the Studio, Stable Audio 3 execution source, a frozen portable CPU runtime, and verified first-run installers, so Node.js, Python, and uv do not need to be preinstalled. Model weights and the optional Windows CUDA runtime 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 CPU TFLite bundle: https://github.com/acidsound/VibeSeq/releases/tag/stable-audio-3-c2949a-windows-x64
• Windows NVIDIA Ampere-or-newer bundle: https://github.com/acidsound/VibeSeq/releases/tag/stable-audio-3-27b5a21-windows-x64-fa2. The app installs an isolated managed Python 3.12 runtime, official PyTorch 2.7.1 CUDA 12.6 wheels, and the digest-pinned community FlashAttention 2.8.3 wheel, runs an actual FlashAttention kernel on the detected GPU, then downloads the exact release checkpoint with the same one-click flow as CPU-only systems.
• Linux x64 TFLite bundle: https://github.com/acidsound/VibeSeq/releases/tag/stable-audio-3-c2949a-linux-x64
• MuScriptor Medium, shared by every desktop platform: https://github.com/acidsound/VibeSeq/releases/tag/muscriptor-medium-f322369

Only the Stable Audio model format selected for the running hardware is downloaded. FlashAttention-compatible NVIDIA hardware must use the CUDA route and never silently downgrades to CPU. CPU-only Windows continues to use the public TFLite route. macOS and Linux store models below ~/VibeSeq Data/models; Windows stores models and its optional runtime below VibeSeq Data beside the installed VibeSeq.exe.

MuScriptor Medium is now available through the same one-click flow on macOS ARM64, Windows x64, and Linux x64. The app downloads the unchanged, digest-pinned public Release assets after the user accepts CC BY-NC 4.0 and the upstream conditions covering noncommercial use, rights in source audio, warranty disclaimer, and indemnification. The installed snapshot includes attribution, the exact upstream source revision, and license links. On NVIDIA Windows systems the same click also installs or repairs the isolated MuScriptor CUDA runtime; system Python is never modified.

Stable Audio and MuScriptor share the base Python/CUDA PyTorch environment and one persistent managed CUDA service on Windows, but install and verify as independent runtime profiles. Missing or broken MuScriptor packages never block Stable Audio readiness or generation. Stable Audio is loaded once and retains VRAM priority across generations; MuScriptor remains GPU-resident only when measured VRAM headroom allows it and otherwise stays on CPU without evicting Stable Audio. CUDA generation uses the official 8-step schedule and exact requested latent duration instead of generating an extra six seconds. FlashAttention 2 remains specific to Stable Audio, and the service never opens a console window.

Windows runtime installation clears and refreshes only the pinned FlashAttention wheel cache before synchronization, then automatically retries with an isolated temporary cache if interrupted installation metadata is incomplete. App shutdown terminates the complete sidecar, CUDA Python, and runtime-installer process trees; the persistent CUDA service also watches its parent process so it cannot remain orphaned and block a later Setup update.

Existing Windows alpha users do not need to uninstall first. Close VibeSeq and run the 0.1.1 Setup over the same installation directory. The installer replaces the application in place and preserves the existing VibeSeq Data directory beside the executable.

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.

Running the unsigned macOS build

Until VibeSeq is signed and notarized with an Apple Developer ID, macOS may report that the downloaded app is damaged or cannot be opened. After verifying the official Release asset with SHA256SUMS.txt, copy VibeSeq.app to /Applications, open Terminal, and run:

xattr -dr com.apple.quarantine "/Applications/VibeSeq.app"

Then open VibeSeq again by double-clicking its icon in Applications. Run this command only for the VibeSeq app downloaded from this official Release.