AUDIO → MIDI · DRUM INPUT BOUNDARY

Audio to MIDI for drums: inspect the input before trusting the notes.

A drum recording is not the same test as a single-note melody: before using an audio to MIDI result, check whether the output preserves separate hits, timing, and silence between hits. The current Note Foundry workflow is designed around clear melodic input, so this page explains the boundary instead of promising drum separation.

For a melodic file, use the audio to MIDI converter. MP3 and WAV-specific checks are on the MP3 to MIDI and WAV to MIDI pages.

What to check in a drum conversion

1. Listen for each hit in the source and mark its expected time.
2. Open the MIDI and count whether separate hits remain separate events.
3. Check for extra notes between hits and missing events after louder transients.
4. Keep the source recording beside the MIDI so timing differences are visible.

Why the melodic workflow has a boundary

The browser detector on this site estimates one pitch at a time. Drums contain transients and noise rather than one stable pitched line, so a nonempty MIDI file would not by itself prove that each drum hit was identified correctly. No drum-specific experiment is claimed on this page.

Questions

Can I treat every MIDI note as a drum hit?

No. Compare each event with the source recording before assigning a drum sound or editing the pattern.

What should I do when timing looks wrong?

Keep the source, inspect the first and last hit, and correct the MIDI timing in your editor instead of assuming the conversion is exact.

Where should I start with a clear melody?

Use the audio to MIDI converter and then inspect the resulting notes.