explaingit

trelisresearch/audio-bits

Analysis updated 2026-05-18

2PythonAudience · researcherComplexity · 4/5LicenseSetup · moderate

TLDR

A research project measuring how much information different speech-to-token methods pack into audio, comparing text transcription against audio codecs.

Mindmap

mindmap
  root((audio-bits))
    What it does
      Measures bits per second
      Compares tokenization methods
      Trains TinyGPT model
    Tech stack
      Python
      Modal
      Weights and Biases
    Use cases
      Compare speech codecs
      Benchmark tokenizers
      Research reproducibility
    Audience
      ML researchers
      Speech engineers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Compare how efficiently text BPE versus audio codecs represent speech

USE CASE 2

Benchmark new speech tokenization methods against published baselines

USE CASE 3

Reproduce the bits-per-second experiments on cloud GPU hardware

USE CASE 4

Study tradeoffs between semantic and acoustic audio codecs

What is it built with?

PythonModalWeights and BiasesHugging Face

How does it compare?

trelisresearch/audio-bits0-bingwu-0/live-interpreter0xkaz/llm-governance-dashboard
Stars222
LanguagePythonPythonPython
Setup difficultymoderatemoderatehard
Complexity4/52/54/5
Audienceresearchergeneralops devops

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 1h+

Requires cloud GPU access via Modal to run the experiments.

MIT license: use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

audio-bits is a research project that measures how efficiently different methods of representing speech can be learned by a small language model. The central question is: when you convert spoken audio into a sequence of tokens, the discrete units that language models process, how much real information do those tokens actually carry per second of speech? The project compares two broad approaches. The first is text BPE (Byte Pair Encoding), the standard technique used to tokenize written text for language models like GPT-2. You transcribe speech to text, then tokenize the text the usual way. The second is audio codecs, programs that compress speech directly into discrete tokens without going through text first. Several codec methods are tested: NeuCodec, Mimi (in two configurations), and SNAC. Each representation is fed into the same small transformer model (called TinyGPT, with about 19 million parameters) trained for exactly one epoch on matched amounts of speech data. The model is then measured on how many bits of information it successfully extracted per second of audio. The headline finding is a three-level hierarchy: text BPE tops out around 22 bits per second, a semantic-only codec reaches about 62 bits per second, and full acoustic codec representations reach around 650 bits per second, though that ceiling mostly reflects reconstruction overhead in the codec rather than content. The code is written in Python and runs experiments on cloud GPU hardware via Modal. Training metrics are logged with Weights and Biases. Published datasets from the experiments are available on Hugging Face. Code is released under the MIT license.

Copy-paste prompts

Prompt 1
Explain how audio-bits measures bits per second for a speech tokenizer
Prompt 2
Help me add a new codec to audio-bits and run the TinyGPT benchmark
Prompt 3
Walk me through reproducing the audio-bits experiments on Modal
Prompt 4
How do NeuCodec, Mimi, and SNAC compare in audio-bits' results?

Frequently asked questions

What is audio-bits?

A research project measuring how much information different speech-to-token methods pack into audio, comparing text transcription against audio codecs.

What language is audio-bits written in?

Mainly Python. The stack also includes Python, Modal, Weights and Biases.

What license does audio-bits use?

MIT license: use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is audio-bits to set up?

Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.

Who is audio-bits for?

Mainly researcher.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.