Skip to content
reklawdboxreklawdbox

Genre Audit

Compare existing genre tags with cached provider, label, BPM, and audio evidence; review only conflicts or uncertain cases; and export approved corrections as Rekordbox metadata XML.

Start here

Section titled “Start here”

Check your current genre tags.

Safety: Review before export

Time
Scope-dependent; only conflicts and manual-review tracks are presented.
You'll get
Approved corrections to existing genre tags 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.

Audit my existing genre tags.

What happens next

Section titled “What happens next”
  1. Choose the audit scope. Start after classification, after importing a differently tagged collection, when a genre seems over-applied, or when newer evidence warrants a review.
  2. Measure and prepare evidence. Check whether enough evidence is ready for genred tracks, then fill core Discogs, Beatport, and Stratum gaps where practical. Essentia is useful but optional.
  3. Compare rather than refill. Use the same evidence model as classification, but surface only conflicts and uncertain existing tags.
  4. Review and export. Decide each conflict group, preview the staged corrections, and export only what you approve.

Decisions and approval checkpoints

Section titled “Decisions and approval checkpoints”
  • Keep a current tag when the evidence is incomplete or your collection uses a deliberate convention the sources cannot express.
  • Low-confidence and insufficient-evidence cases require individual review.
  • Use Genre Classification for blank genres; this workflow verifies tags that already exist.

What changes and how to recover

Section titled “What changes and how to recover”

Preparation may update enrichment and audio caches. Approved corrections are staged in memory and do not directly edit audio files or master.db. XML export fails closed unless the built-in database backup succeeds or the configured custom backup script exits zero. Clear unwanted corrections before export; a failed XML write keeps the staged changes available for retry.

You can continue an interrupted audit with the same scope and evidence sources. Start a fresh pass after changing either so every existing genre is judged consistently. Previously prepared evidence remains available, but staged corrections must be exported before the MCP process restarts.

Finish in Rekordbox

Section titled “Finish in Rekordbox”

Keep the exported XML until the correction import is verified. Follow the metadata XML handoff, then check representative corrected and intentionally retained genres.

Technical details

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

Complete reference

Workflow contract

Stages metadata for XML

Compare existing genres with cached evidence and review only conflicts or uncertain classifications.

Best for
Users verifying existing genre tags after classification, imports, or taxonomy changes.
Network
Network when neededOnly preparation for missing evidence; audit_genres itself is cache-only.
Scope
Genred tracks, paginated with caller-managed max_tracks and offset values.
Time
Scope-dependent; only conflicts and manual-review tracks are presented.
Resuming
Enrichment/audio preparation traverses page.next_offset while page.has_more, then retries failed explicit track IDs; restart after selector/library-order changes, enrichment provider/cache-policy changes, or changed audio skip_cached/Essentia availability. Audit pagination keeps its separate caller-managed offset. Caches persist, but staged corrections must be exported before the MCP process restarts.
Result
Approved corrections to existing genre tags 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 the cache-only audit.
  • 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 corrections.

Before you start

  • Existing genre tags to audit.
  • A scoped cache_coverage baseline for genred tracks.
  • Core evidence gaps filled where practical; incomplete evidence is allowed but needs individual review.

Approval checkpoints

  • Approve or reject each conflict group; low-confidence items require individual judgment.
  • Review preview_changes and approve XML export.

Recovery

  • Gather more evidence and re-run the affected page when a conflict is ambiguous.
  • Clear unwanted staged corrections 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 audit corrections are previewed.

Next steps

Section titled “Next steps”