The curatorial step that transforms machine‑clean metadata into library‑grade truth
Once the metadata has been extracted (Step 1) and normalized (Step 2), the next phase is the most important one in the entire workflow: human review. This is where the machine’s best guesses are checked, corrected, clarified, and elevated into a clean, authoritative dataset.
Deterministic filename generation and internal metadata repair
Once the metadata has been extracted (Step 1) and normalized + human‑curated (Steps 2–3), the final stage of the workflow is to apply the new metadata to the actual MIDI files. This renamer script is the engine that transforms a chaotic library into a clean, consistent, future‑proof collection.
The script uses the curated metadata spreadsheet as the single source of truth and performs two major tasks:
Transforming raw MIDI metadata into a clean, consistent, human‑editable dataset
After extracting the raw metadata from your MIDI library, the next step is to convert that unfiltered snapshot into a normalized, machine‑clean, human‑friendly spreadsheet. The Metadata Normalizer script takes the raw dump and produces a structured, consistent, encoding‑safe metadata file that is ready for human review.
This step is crucial because raw metadata often contains:
Creating a complete, unfiltered snapshot of your MIDI library
The first step in normalizing a MIDI library is to capture everything we can possibly know about each file before any cleanup or renaming occurs. This is the “archaeological dig” phase: we gather the raw material that all later steps depend on.
A dedicated metadata‑dump script scans the target folder and extracts: