btc chords needs about 0.5 GB of memory at F16 (a 0.0 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 6 quants, from 0.0 GB (Q8_0) to 0.0 GB (F32).
BTC chord recognition model for audio-to-chord conversion
BTC chord recognition converts audio into a chord timeline. The model is small, with 0.00292 billion parameters, and is available in GGUF format for use with CrispASR. It supports a 170‑class vocabulary and can collapse to major/minor chords on demand.
Good at
- Accurate chord detection
- Compact size
- Easy integration with CrispASR
Limits
- CC‑BY‑NC‑SA‑4.0 license restricts commercial use
- No vision or language support
- Quantization limited to Q8_0 and F16
Best for
- Music transcription tools
- Educational chord analysis
- Non‑commercial research projects
Who it’s for. Developers building music analysis applications who need a lightweight chord recognition model and are willing to comply with a non‑commercial license. The model is ideal for academic or hobbyist projects.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q8_0 | 0.0 GB | 0.5 GB | Fits | Get file → | |
| Q8_0 | 0.0 GB | 0.5 GB | Fits | Get file → | |
| F16 | 0.0 GB | 0.5 GB | Fits | Get file → | |
| F16 | 0.0 GB | 0.5 GB | Fits | Get file → | |
| F32 | 0.0 GB | 0.5 GB | Fits | Get file → | |
| F32 | 0.0 GB | 0.5 GB | Fits | Get file → |
For 8 GB VRAM, the Q8_0 quantization uses about 0.5 GB of memory at 8 k context and has a file size of 0.01 GB. The F16 quantization offers the same memory usage but a slightly larger file. Both are suitable for low‑budget setups. If memory is very tight, Q8_0 is recommended.
What GPU do you need for btc chords?
These figures add the file size, an fp16 KV cache at an 8K context window 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: the best quant that fits is F32 (0.0 GB file, about 0.5 GB in use).
Which btc chords quant should you choose?
F16 (0.0 GB) is the middle option in this repository. The unquantized model. It gives original quality and needs the most memory, so it is mainly for conversion or reference.
If memory is tight, the smallest file is Q8_0 at 0.0 GB, with the quality trade-offs that come with fewer bits. Close to lossless. It costs roughly twice the memory of a 4-bit file, so it suits cases where you have plenty of VRAM.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about btc chords
How much VRAM does btc chords need?
About 0.5 GB at F16 with an 8K context window. That is the 0.0 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 btc chords on an 8 GB GPU?
Yes, with F32: the 0.0 GB file needs about 0.5 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of btc chords GGUF?
It depends on the quant: Q8_0 is 0.0 GB, Q8_0 is 0.0 GB, F16 is 0.0 GB, F16 is 0.0 GB, F32 is 0.0 GB, F32 is 0.0 GB.
Where can I download btc chords GGUF?
The files are on Hugging Face in the cstr/btc-chords-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does btc chords use?
Hugging Face lists the license as cc-by-nc-sa-4.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run BTC chords on 8 GB VRAM?
Yes. The Q8_0 quantization requires approximately 0.5 GB of VRAM at 8 k context, well within an 8 GB budget.
Is the model suitable for commercial products?
No. The weights are licensed CC‑BY‑NC‑SA‑4.0 and may not be used commercially.
What quantization should I use for the smallest file?
Use Q8_0; it is indistinguishable from F16 but smaller in file size and memory usage.