lyrics room final refiner ozan v1 needs about 14.9 GB of memory at Q8_0 (a 13.0 GB file) with an 8K context window, so it fits on a 16 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 5.4 GB.
Lyrics Room Final Refiner – 12B model that de‑slops and rewrites lyrics into strict JSON.
The model is a Q8_0 quantized 12B LLM fine‑tuned from Ozan‑v1‑12B. It rewrites sung lyrics and style prompts into JSON, removing AI‑style filler while preserving song identity. It is served via llama.cpp, LM Studio, or Ollama.
Good at
- Low‑slop lyric rewriting
- Strict JSON output for lyrics and style
- Fine‑tuned from Ozan for creative writing
Limits
- Requires ~15 GB VRAM at 8 k context
- No vision support
- Apache‑2.0 license only
Best for
- Rewriting Suno Director output
- Generating JSON lyric files
- Removing AI‑style filler from lyrics
Who it’s for. Musicians and lyricists who need clean, singable lyrics and structured JSON for production. The model is ideal for local deployment on high‑memory GPUs.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q8_0 | 13.0 GB | 14.9 GB | Too big | Get file → |
The only available quant is Q8_0, 13.02 GB. It needs roughly 15 GB VRAM for 8 k context. If you have less memory, the model cannot be run without off‑loading or a smaller context.
What GPU do you need for lyrics room final refiner ozan v1?
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: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: the best quant that fits is Q8_0 (13.0 GB file, about 14.9 GB in use).
Which lyrics room final refiner ozan v1 quant should you choose?
Q8_0 (13.0 GB) is the middle option in this repository. 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 lyrics room final refiner ozan v1
How much VRAM does lyrics room final refiner ozan v1 need?
About 14.9 GB at Q8_0 with an 8K context window. That is the 13.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 lyrics room final refiner ozan v1 on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 14.9 GB, so you would need a larger GPU or CPU offloading.
What is the file size of lyrics room final refiner ozan v1 GGUF?
It depends on the quant: Q8_0 is 13.0 GB.
What context length does lyrics room final refiner ozan v1 support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 1.3 GB at 8K and 5.4 GB at 32K.
Where can I download lyrics room final refiner ozan v1 GGUF?
The files are on Hugging Face in the rambrogi/lyrics-room-final-refiner-ozan-v1-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 lyrics room final refiner ozan v1 use?
Hugging Face lists the license as apache-2.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 this model on 8 GB VRAM?
No. The Q8_0 quant requires about 15 GB VRAM at 8 k context, so 8 GB is insufficient.
Does this model support vision or image input?
No. The model is text‑only and has no vision capabilities.
What is the maximum context length I can use?
The model was trained on 131,072 tokens, but practical inference is limited by VRAM; 8 k context is typical.