MP3 to MIDI tail-gate check: compare the same melody before and after gating.
In this controlled run, the original tail and the gated-tail-click input both produced one event with pitch 64 and identical note boundaries.
Input condition
The test generated the same four-note mono melody with a low-level tail. The gated variant added a short high-amplitude cutoff impulse. Both files were evaluated with the exact deployed detector and MIDI writer in Node VM.
| Input | Observed output | What to inspect |
|---|---|---|
| original-tail.wav | One event, pitch 64, 0.718367–1.297052 s | Baseline note boundary |
| gated-tail-click.wav | One event, pitch 64, 0.718367–1.297052 s | Whether the gate changes the detected note |
Outputs: original-tail.mid, gated-tail-click.mid, and results.json.
What this does not prove
This comparison does not prove that gating preserves every melody, that every tail can be fixed with the same cutoff, or that a full song will keep identical boundaries. It documents only these two generated inputs and this detector run.
After conversion
Keep the original and gated files separate, rerun the same detector, and compare event count, pitch, and start/end boundaries before arranging the MIDI.
Questions about tail gating
Did gating change the tested note?
No. Both tested files produced one pitch-64 event with the same recorded boundaries.
Is the gate result a full-song guarantee?
No. It is a controlled comparison of two generated tail conditions.
What should I compare after processing?
Compare event count, pitch, and note start/end times against the original input.