A sonic cartography tool for DJs who treat tempo as a landscape, not a constraint.
BeatWeaver is an open-source companion for selectors, bedroom curators, and touring artists who want their sets to breathe. Where legacy BPM utilities bark numbers at you like a metronome with an attitude problem, BeatWeaver paints a living map of your library — key clashes, half-time mismatches, and that tantalizing 4-BPM bridge between two tracks that shouldn't work but absolutely do.
This project is the spiritual successor to the ideas explored in small, focused tempo helpers, rebuilt from the ground up with a modular engine, a redesigned visual language, and a philosophy that the human ear still outranks the algorithm.
- The Story Behind BeatWeaver
- What It Does
- Key Features
- Visual Philosophy
- Multilingual & Global Reach
- Supported Formats & Integrations
- The Tempo Graph
- Harmonic Mixing Engine
- Performance & Responsiveness
- Roadmap for 2026
- Frequently Asked Questions
- Community & Support
- Contributing
- License
- Disclaimer
Every DJ knows the moment. The floor is locked in, you're three tracks deep, and suddenly you need to know: can I jump from 124 to 128 without breaking the spell? Most tools answer with a single number. BeatWeaver answers with context — the trajectory, the drift, the emotional cost of that jump.
The original spark for this project came from a tiny helper script that did one thing: read a folder, print BPMs. It was humble, it was useful, and it was the seed of something bigger. BeatWeaver is what happens when you take that seed and grow an entire orchard — analysis, visualization, harmonic suggestions, and a workflow that respects both the technical and the artistic side of selection.
Think of it less as software and more as a co-pilot for your ears.
At its core, BeatWeaver ingests your audio library, extracts rhythmic and tonal information, and presents it in a way that helps you make split-second decisions without leaving the booth.
- Reads tempo, key, energy, and spectral character from a wide range of audio formats.
- Builds a navigable graph of your entire collection based on musical proximity.
- Suggests transitions ranked by groove compatibility, not just BPM distance.
- Lets you annotate tracks with personal tags, moods, or "do not play before 2am" flags.
- Exports setlists as structured documents you can share or archive.
Whether you're preparing a two-hour warm-up or improvising at an afterparty, BeatWeaver keeps the information flowing without ever shouting over the music.
The layout adapts fluidly from a 13-inch laptop on a cramped booth table to a wall-mounted display in a studio. Panels collapse, graphs rescale, and controls stay within thumb's reach on touch devices. Every interaction is designed to feel like adjusting a fader rather than filling out a form.
- Adaptive grid that reflows based on viewport.
- High-contrast and low-light themes for dimly lit venues.
- Keyboard-first navigation for power users who never touch a mouse between tracks.
- Customizable density: compact mode for glanceable reading, relaxed mode for deep analysis.
Music crosses borders, and so should the tools that serve it. BeatWeaver ships with translation coverage for fourteen locales, with community-maintained strings that evolve as the lexicon of electronic music does.
- Interface fully translated, including error states and tooltips.
- Locale-aware number formatting for BPM decimals and time signatures.
- Right-to-left layout support.
- Community translation portal for adding new languages without touching core code.
A global user base means questions arrive at every hour. The project maintains a rotating support presence — asynchronous help channels, a knowledge base written in plain language, and a triage process that ensures no question sits unanswered for long.
- Structured issue templates that guide reporters toward useful detail.
- Maintainer rotation across time zones so responses don't wait for one person's morning.
- A living FAQ that grows from real conversations.
- Onboarding walkthroughs for first-time contributors and first-time users alike.
The analysis engine doesn't just count beats — it understands phrasing. It recognizes when a track drifts intentionally, when a breakdown resets the grid, and when two bars of silence are actually a bridge rather than an error.
- Multi-pass onset detection tuned for four-on-the-floor, broken beat, and live percussion.
- Confidence scoring so you know when to trust the number and when to trust your ear.
- Manual override with gentle learning: your corrections inform future analysis of similar material.
Keys are not islands. BeatWeaver builds a relational map using camelot-style and classical notation side by side, then layers tempo on top to reveal transitions that feel inevitable rather than forced.
- Dual notation display for DJs trained in either system.
- Energy-aware suggestions that respect the arc of a set.
- "Bridge finder" that surfaces intermediate tracks when two favorites sit far apart.
Draft, rearrange, and archive sets in a dedicated canvas. Drag tracks between slots, see cumulative runtime update live, and export when the picture feels right.
- Version history for setlists you keep revisiting.
- Export to plain text, structured markup, or printable cue sheets.
- Private notes attached to any slot, visible only to you.
BeatWeaver refuses the spreadsheet aesthetic that dominates DJ tooling. Numbers matter, but they live inside a visual grammar that mirrors how selectors actually think — in clusters, in waves, in color-coded moods.
- The tempo graph uses soft gradients instead of harsh gridlines.
- Color encodes energy, not arbitrary categories.
- Transitions are drawn as curves, echoing the way a crossfader feels under the hand.
- Nothing blinks. Nothing demands attention unless something is genuinely urgent.
The result is a workspace you can stare at for four hours without fatigue, and glance at for two seconds and still extract meaning.
Localization here is not an afterthought bolted on at release. It is threaded through the architecture.
| Locale | Status | Notes |
|---|---|---|
| English | Complete | Reference implementation |
| Spanish | Complete | Community maintained |
| French | Complete | Community maintained |
| German | Complete | Community maintained |
| Portuguese (BR) | Complete | Community maintained |
| Italian | Complete | Community maintained |
| Dutch | Complete | Community maintained |
| Japanese | In progress | Seeking reviewers |
| Korean | In progress | Seeking reviewers |
| Mandarin | In progress | Seeking reviewers |
| Polish | Planned | Contributions welcome |
| Turkish | Planned | Contributions welcome |
| Arabic | Planned | RTL layout tested |
| Hindi | Planned | Contributions welcome |
If your language is missing, the translation portal is open. No coding required — just fluency and a love for precise wording.
BeatWeaver reads what you already have. No conversion rituals, no proprietary lock-in.
- Common lossless and lossy audio containers.
- Metadata harvested from standard tag fields, with graceful fallback when tags are sparse.
- Folder-watching mode that picks up new arrivals automatically.
- Export bridges for popular setlist and library-management ecosystems.
The philosophy is simple: your library is yours, and BeatWeaver is a guest that tidies up after itself.
Picture every track in your collection as a star. Tracks with similar tempo and mood sit close together; outliers drift to the edges. Zoom in and clusters reveal themselves — the deep house nebula, the drum-and-bass spiral arm, the strange ambient void where nothing quite fits but everything belongs.
You can:
- Pan and zoom with intuitive gestures.
- Lasso a cluster and send it straight to a setlist.
- Overlay key compatibility as a color wash.
- Filter by energy ceiling or floor.
It is, frankly, the most fun you can have while preparing to work.
The harmonic engine is where BeatWeaver earns its keep. It weighs tempo distance, key relationship, and energy delta, then produces a ranked list of next-track candidates that respect the direction you're already heading.
- Adjustable weighting: prioritize groove, prioritize key, or prioritize energy.
- "Lock" a track and explore everything reachable within two transitions.
- A "wildcard" toggle that occasionally surfaces an unexpected but defensible choice.
The goal is never to replace your instinct — only to hand it better fuel.
Analysis runs in the background without freezing the interface. Large libraries are indexed incrementally, so you can start working before the scan completes.
- Multi-threaded analysis pipeline.
- Cached results keyed to file fingerprint, so re-scanning is near-instant.
- Memory-conscious graph rendering even with tens of thousands of tracks.
- Graceful degradation on older hardware.
A tool that stutters is a tool that gets closed. BeatWeaver stays out of the way.
- Q1 2026 — Stable 1.0 release with full locale coverage for the initial fourteen languages.
- Q2 2026 — Collaborative setlist editing for duos and back-to-back partners.
- Q3 2026 — Live mode with real-time tempo tracking from an external audio input.
- Q4 2026 — Plugin surface for community-built analysis modules.
Priorities shift with community feedback. The roadmap is a conversation, not a contract.
Does BeatWeaver replace my existing library software? No. It complements it. Think of BeatWeaver as the analysis layer that sits beside your catalog, not on top of it.
Is my library uploaded anywhere? Never. All analysis happens locally. Your music never leaves your machine.
Can I use it without an internet connection? Yes. The core tool is fully offline. Only translation updates and optional telemetry-free crash reports require a connection, and both are opt-in.
What if the BPM detection is wrong? Correct it manually. BeatWeaver remembers your correction and weighs similar material accordingly.
Is there a mobile version? The responsive interface works on tablets today. A dedicated mobile companion is on the 2026 roadmap.
The project lives because people care about it. Whether you file a precise bug report, translate a stubborn string, or simply tell a friend, you're part of the engine.
- Discussion spaces for workflow tips and set-sharing.
- A weekly digest of merged changes and community highlights.
- Mentorship pairing for first-time contributors.
- A code of conduct that treats everyone like a colleague, because they are.
Support is not a department here — it is a habit.
Contributions of every size are welcome. Before opening a pull request:
- Read the contribution guide and code of conduct.
- Check open issues to avoid duplicating effort.
- Keep changes focused; small pull requests merge faster.
- Write clear commit messages that explain why, not just what.
- Be patient and kind during review — everyone here is volunteering time.
Translation contributions go through a separate, gentler workflow that requires no development environment at all.
BeatWeaver is released under the MIT License. You are welcome to use, modify, and distribute it in accordance with the terms of that license.
Read the full text here: MIT License
Copyright (c) 2026 BeatWeaver Contributors
BeatWeaver is provided as-is, without warranty of any kind, express or implied. The authors and contributors are not liable for any damages arising from its use, including but not limited to missed transitions, emptied dancefloors, or arguments about whether a track is "really" 128 BPM.
Tempo detection is an estimation, not a truth. Always trust your ears over any number on a screen. Respect local noise ordinances. Credit the artists you play. Tip the bartenders.
This project is not affiliated with any hardware manufacturer, music service, or venue. All trademarks mentioned belong to their respective owners.