Skip to main content

SplitScore

Separate an audio file into 6 stems with BS-RoFormer-SW, then transcribe the stems you choose to MIDI with MuScriptor. A local web console (FastAPI + vanilla JS).

audio ──▶ BS-RoFormer-SW ──▶ 6 stems ──▶ MuScriptor ──▶ per-stem .mid

Quick start

uvx splitscore

This auto-detects your NVIDIA GPU and installs the correct CUDA torch backend. First run downloads models (~3 GB total) into ~/.cache/.

Requirements

  • Windows 11 / Linux, Python 3.13, uv
  • NVIDIA GPU recommended — requires CUDA 12.x Toolkit installed for GPU acceleration (auto-detected; falls back to CPU if missing)
  • Apple Silicon (MPS) and AMD (ROCm) GPUs are also supported

Setup (development)

uv run python sync.py          # auto-detect GPU, install correct CUDA torch
uv run python -m app           # start server

MuScriptor weights are gated: you need a free Hugging Face account.

  1. Open https://huggingface.co/muscriptor/muscriptor and accept the CC BY-NC 4.0 (non-commercial) license.
  2. Log in from the terminal:
    uv run hf auth login
    
    (or export HF_TOKEN=hf_... in your shell).

Usage

  1. Drop an audio file (wav / mp3 / flac / ogg / m4a / aiff).
  2. Separation runs automatically — wait for the 6 stems to appear.
  3. Tick the stems you want, adjust per-stem instrument (empty = auto), hit Transcribe selected to MIDI.
  4. Download the .mid files. Each stem is named <song>_<stem>.mid.

Every setting (model size, device, precision, temperature, beam/batch size, output folder) is adjustable in the Settings panel and persists across runs.

Notes & limitations

  • MuScriptor does not preserve velocity — output is timing, pitch, and instrument.
  • Drums and "other" stems tend to transcribe poorly to readable MIDI; melodic stems (vocals, piano, guitar, bass) give the best results.
  • MIDI + stem WAVs are written under the configured output folder (./output/<job_id>/stems|midi/).
  • One job at a time by design.

License

  • Code: MIT — see LICENSE.
  • Models: the separation model and the MuScriptor weights are separate and distributed under their own licenses. In particular, MuScriptor's weights are CC BY-NC 4.0 (non-commercial) and gated on Hugging Face; that restriction applies to the models regardless of this project's MIT license.

Metadata

Release files for splitscore 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for splitscore 0.1.1
File Size Uploaded
splitscore-0.1.1.tar.gz 40.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for splitscore 0.1.1
File Interpreter ABI Platform
splitscore-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 76.9 kB

Release files / splitscore-0.1.1.tar.gz

Download URL splitscore-0.1.1.tar.gz
Size 40.7 kB
Tags Source
SHA-256 checksum
How to use checksums
cc5978debd401bae86d4a4e739bb6b8c1c87a61546a41162e71a74c1b65783ec
BLAKE2b-256 checksum
How to use checksums
5952312804c96a3e4238cb7158138f1e7ad0fcd05c8e02adcd06c20cf5e9d172
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.

Transparency log

Release files / splitscore-0.1.1-py3-none-any.whl

Download URL splitscore-0.1.1-py3-none-any.whl
Size 36.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e70cf5e548e41d78c195fd25db5b89e7a4c85c7386065759cbbf12542e83e911
BLAKE2b-256 checksum
How to use checksums
563353805ed93f803b00b4232f90036b5b46b96b0f7a8ce925aca7a0515f27b7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

This release

0.1.1 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page