Skip to content
reklawdboxreklawdbox

Genre Classification

Assign genres to ungenred tracks from cached provider, label, BPM, and audio evidence, with confidence-based human review and a Rekordbox-compatible metadata XML handoff.

Start here

Section titled “Start here”

Add genres to untagged tracks.

Safety: Review before export

Time
Scope-dependent; low and insufficient confidence tracks require individual review.
You'll get
Approved genre assignments in a Rekordbox-compatible metadata XML file.

Review before import. Changes are prepared only. Approved export creates a backup and XML; import and verify it in Rekordbox, and keep the XML until then.

Online access: Online services are used only when the chosen step needs information that is not available locally.

Classify genres for my ungenred tracks.

What happens next

Section titled “What happens next”
  1. Measure readiness. Check whether enough evidence is ready for ungenred tracks. A searched no-match counts as complete, and optional evidence may remain unavailable.
  2. Prepare evidence. Fill core Discogs, Beatport, and Stratum gaps where practical. Essentia adds richer audio evidence but is not a hard gate.
  3. Classify by confidence. Compare Discogs styles, Beatport genres, label associations, BPM, and audio features against the DJ-oriented taxonomy.
  4. Review and stage. Apply the chosen confidence policy, inspect low or insufficient results individually, preview the aggregate, and export only approved genres.

Decisions and approval checkpoints

Section titled “Decisions and approval checkpoints”
  • High — multiple sources agree and BPM is plausible
  • Medium — partial agreement or single strong source
  • Low — weak or ambiguous evidence
  • Insufficient — conflicting data, needs a manual call

Choose which tiers, if any, may be staged in bulk. Low and insufficient tracks need individual judgment. The built-in taxonomy has roughly 50 DJ-oriented genres and is a starting point, not a closed list; add a genre only when the evidence and your collection vocabulary support it.

What changes and how to recover

Section titled “What changes and how to recover”

Preparation may update enrichment and audio caches. Approved genres are staged in memory; they do not directly edit audio files or master.db. XML export proceeds only after the built-in database backup succeeds or the configured custom backup script exits zero. A failed XML write retains the staged genres for retry; clear unwanted genres before exporting.

You can continue an interrupted preparation pass with the same scope and evidence sources. Start a fresh pass after changing either so every track is classified consistently. Previously prepared evidence remains available, but unexported staged genres do not survive an MCP restart.

Finish in Rekordbox

Section titled “Finish in Rekordbox”

Keep the XML until the import is verified. Follow the metadata XML handoff, then check representative genre values in Rekordbox.

Technical details

Section titled “Technical details”
Technical details, safety, and recovery

Complete reference

Workflow contract

Stages metadata for XML

Classify ungenred tracks from cached provider, label, BPM, and audio evidence with confidence-based review.

Best for
Users assigning consistent DJ-oriented genres to ungenred or noncanonical tracks.
Network
Network when neededOnly preparation for missing provider evidence; classify_tracks itself is cache-only.
Scope
Ungenred and noncanonical-genre tracks, processed with explicit max_tracks and offset pagination.
Time
Scope-dependent; low and insufficient confidence tracks require individual review.
Resuming
Enrichment/audio preparation traverses page.next_offset while page.has_more, records failures, and retries failed explicit track IDs after the scope; restart after selector/library-order changes, enrichment provider/cache-policy changes, or changed audio skip_cached/Essentia availability. Classification keeps its separate caller-managed offset. Caches persist, but staged genres are lost when the MCP process restarts unless exported.
Result
Approved genre assignments in a Rekordbox-compatible metadata XML file.

What can change

Staged metadata
This workflow creates in-memory metadata changes for XML export.
Direct user files
None.
Local state
  • Enrichment cache When needed — Preparation fills missing Discogs or Beatport searches before cache-only classification.
  • Audio-analysis cache When needed — Preparation fills missing Stratum or optional Essentia analysis.
  • Provider session When needed — Discogs authentication is required while filling preparation gaps.
Files created
  • Rekordbox database backup On export — XML export proceeds only after the built-in backup succeeds or the configured custom script exits zero
  • Metadata XML file On export — The user approves staged genre changes.

Before you start

  • A scoped cache_coverage baseline for ungenred tracks.
  • Core Discogs, Beatport, and Stratum gaps filled where practical; incomplete evidence is allowed.
  • A user-selected confidence approval policy.

Approval checkpoints

  • Choose which confidence tiers, if any, may be staged in bulk.
  • Review low and insufficient confidence tracks individually.
  • Review the aggregate staged result and approve XML export.

Recovery

  • Fill evidence gaps or adjust genre overrides, then re-run the affected page of classification.
  • Clear unwanted staged genres before export.
  • A failed XML write keeps staged changes available for retry; keep the exported XML until import is verified.

Rekordbox handoff

  1. Metadata XML file On export — After all approved genre changes are previewed.

Next steps

Section titled “Next steps”