BE

Beat This! (final0)

BeatGGUF by cstrUpdated 2026-07-20
Download on Hugging Face
Parameters20M
Context—
Layers—
Architecturebeat-this
Smallest quant0.0 GB
Quick answer

Beat This! (final0) 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 2 quants, from 0.0 GB (F16) to 0.1 GB (F32).

Beat This! (final0) – a lightweight beat and downbeat tracker

Beat This! (final0) is a 20.25 M parameter transformer that tracks beats and downbeats using plain peak‑picking. It is released under the MIT license and has no external dependencies on proprietary libraries.

Good at

  • Beat and downbeat detection
  • Peak‑picking post‑processing
  • MIT‑licensed for commercial use

Limits

  • No vision support
  • Small context (8 k tokens)
  • No dynamic Bayesian network

Best for

  • Commercial beat‑tracking applications
  • Audio analysis pipelines
  • Integration with CrispASR

Who it’s for. Developers and audio engineers who need a reliable, open‑source beat tracker that can be embedded in commercial products without licensing restrictions.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
F160.0 GB 0.5 GB
Fits Get file →
F320.1 GB 0.6 GB
Fits Get file →

For 8 GB VRAM, the F16 quantization (0.04 GB file, 0.5 GB memory at 8 k context) is recommended. If more memory is available, F32 (0.08 GB file, 0.6 GB memory) offers higher precision. Both are lightweight and suitable for quick deployment.

What GPU do you need for Beat This! (final0)?

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.1 GB file, about 0.6 GB in use).

Which Beat This! (final0) 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.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturebeat-this
Parameters20M

Source

Quantized bycstr
FamilyBeat
Licensemit
Downloads (HF)1,796
Last updated2026-07-20

Frequently asked questions about Beat This! (final0)

How much VRAM does Beat This! (final0) 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 Beat This! (final0) on an 8 GB GPU?

Yes, with F32: the 0.1 GB file needs about 0.6 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of Beat This! (final0) GGUF?

It depends on the quant: F16 is 0.0 GB, F32 is 0.1 GB.

Where can I download Beat This! (final0) GGUF?

The files are on Hugging Face in the cstr/beat-this-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 Beat This! (final0) use?

Hugging Face lists the license as mit. 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 Beat This! on 8 GB VRAM?

Yes, the F16 quantization requires only 0.5 GB of VRAM at 8 k context, well within an 8 GB budget.

Does Beat This! support multi‑channel audio?

No, the model expects 22.05 kHz mono input and does not process multi‑channel audio.

Is Beat This! compatible with ggml?

Yes, the GGUF files are designed for use with ggml and can be loaded directly in llama.cpp.

Similar models

Browse all →

More from cstr

All by cstr →

Other tiny models

All tiny models →