muscriptor large needs about 5.7 GB of memory at its main file (a 2.8 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 2 quants, from 2.8 GB to 5.6 GB.
Muscriptor Large – Audio‑to‑MIDI transcription model
Muscriptor Large is a 1.38 billion‑parameter model designed for audio‑to‑MIDI transcription. It uses llama.cpp as the transformer backend and supports an 8192‑token context window. The model is available in two GGUF quantizations.
Good at
- Audio‑to‑MIDI transcription
- Fast inference with llama.cpp
- Large context support
Limits
- No vision support
- License not specified
- Requires conditioning weights
Best for
- Transcribing music recordings
- Generating MIDI from audio clips
- Batch audio transcription
Who it’s for. Developers and musicians who need accurate MIDI conversion from audio. The model is suitable for integration into audio processing pipelines or standalone transcription tools.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 2.8 GB | 5.7 GB | Fits | Get file → | |
| — | 5.6 GB | 8.5 GB | Too big | Get file → |
For 8 GB VRAM, use the 2.78 GB file (est. 5.7 GB memory at 8k context). For 12 GB VRAM, the 5.55 GB file (est. 8.5 GB memory) provides higher precision.
What GPU do you need for muscriptor large?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: no quant fits at an 8K context.
- 6 GB VRAM: the best quant that fits is the main file (2.8 GB file, about 5.7 GB in use).
- 8 GB VRAM: the best quant that fits is the main file (2.8 GB file, about 5.7 GB in use).
- 12 GB VRAM: the best quant that fits is the main file (5.6 GB file, about 8.5 GB in use).
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about muscriptor large
How much VRAM does muscriptor large need?
About 5.7 GB at its main file with an 8K context window. That is the 2.8 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run muscriptor large on an 8 GB GPU?
Yes, with the smaller files: the 2.8 GB file needs about 5.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of muscriptor large GGUF?
It depends on the quant: file is 2.8 GB, file is 5.6 GB.
What context length does muscriptor large support?
The GGUF header lists a trained context length of 8,192 tokens (8K). The KV cache grows with the context you use: about 2.4 GB at 8K and 2.4 GB at 8K.
Where can I download muscriptor large GGUF?
The files are on Hugging Face in the byzp/muscriptor-large-gguf repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
Can I run Muscriptor Large on 8 GB VRAM?
Yes, the 2.78 GB quantized file requires about 5.7 GB of VRAM at 8k context, which fits within 8 GB.
Do I need to extract conditioning weights?
Yes, the conditioning weights (~11 MB) must be extracted once from the full safetensors before running transcription.
What context length does the model support?
The model was trained with an 8192‑token context window.