MP3 to MIDI: transcription gives note data; arrangement is a separate step.
The measured workflow here writes detected note events to MIDI; it does not invent a new instrument part or finish an arrangement. That boundary is the quickest way to choose the next tool after conversion.
What the controlled run actually produces
The public source.mp3 is a short four-note melody. The detector records event count, pitch, and start/end windows in results.json, then writes editable MIDI note data.
| Stage | Measured or not | What you receive |
|---|---|---|
| Transcription | Measured on the isolated fixture | Detected pitches and timing windows |
| Arrangement | Not established by this fixture | No invented part for a missing instrument |
| Production edit | Must be checked after export | Manual octave, timing, velocity, and track decisions |
Why a clean melody matters
The controlled detector run is designed for a clear solo line. Chords, drums, layered vocals, and dense mixes can produce missing or incorrect notes. Treat those as separate checks instead of assuming the four-note result scales to a full song.
After conversion
Open the MIDI in an editor, compare it with the source, then decide whether to keep the transcription, edit it, or arrange a new part yourself. A MIDI file is editable note data; it is not the original audio and it is not a finished production.
Questions about the boundary
Does MP3 to MIDI automatically arrange a missing instrument?
No. This measured workflow reports detected note events; it does not claim to generate a new instrument arrangement.
Can I use the MIDI in a DAW?
Yes. Import the exported MIDI, inspect the notes, and make arrangement decisions in your editor or DAW.
What should I do with a full mix?
Mark it as a separate, untested condition. Start with a clear solo melody when you need to compare the detector output with a known source.