YouTube-to-MIDI input test

Should you use WAV or MP3 for YouTube to MIDI?

Use WAV when you already have it; do not convert a clean MP3 to WAV just to use this tool. In our controlled test, both versions found all four intended pitches. The WAV produced five note events, while the 128 kbps MP3 produced six because it added one more short boundary fragment.

Convert an audio file

This is one generated four-second source, not a universal accuracy ranking. Source clarity and musical complexity can matter more than the container or codec.

What we tested in the current converter

We generated a mono, 44,100 Hz source containing A4, C5, E5, and G5 for one second each. We saved the same samples as an uncompressed WAV and encoded them as a 128 kbps MP3. No video, performer, title, channel name, or copyrighted recording was used.

InputFile sizeIntended pitches foundMIDI result
WAV352,844 bytesA4, C5, E5, G55 events: 4 long notes, 1 short fragment
128 kbps MP364,783 bytesA4, C5, E5, G56 events: 4 long notes, 2 short fragments

The WAV decoded to exactly 4.000 seconds. The MP3 decoded to about 4.049 seconds and shifted the detected starts by roughly 0.023 seconds. Both outputs retained the four intended notes longer than 0.9 seconds. The extra MP3 event was a 0.059-second C5 fragment near a note boundary.

When WAV is the better input

Choose the original WAV when it is already available. WAV can preserve the source samples without lossy encoding, so it avoids adding compression artifacts before pitch analysis. In this test it also produced one fewer short fragment. That does not mean every WAV will beat every MP3: a noisy WAV can still be a worse source than a clean MP3.

When MP3 is a reasonable input

Use the existing MP3 when that is the file you legitimately have. The 128 kbps version in this test was less than one fifth the size of the WAV and still preserved all four intended pitches. Converting that MP3 to WAV later cannot restore audio information removed by the earlier lossy encode; it only places the decoded audio in a larger file.

What the converter actually accepts

The current local-file picker accepts MP3, WAV, and M4A. Each selected file is decoded by the browser and resampled to mono at 22,050 Hz before note analysis. M4A is accepted by the interface, but it was not part of this controlled comparison, so this page does not claim a measured M4A result.

A practical choice

  1. Keep the cleanest original you have. Avoid another lossy export before transcription.
  2. Use WAV directly when it is the source. There is no need to make an MP3 copy first.
  3. Use an existing MP3 directly. Rewrapping it as WAV does not recreate lost detail.
  4. Review short boundary notes. If they appear, try the minimum-note-length cleanup before downloading.

What this test does and does not prove

It verifies that the current converter processed both generated files and found the four intended pitches in this run. It does not establish an accuracy percentage, guarantee that WAV always creates fewer events, or compare every bitrate, codec, browser, or recording.

For simultaneous notes, see the controlled chord test. If a conversion produces nothing, use the no-notes checklist.

After the note draft: MIDI Agent is a text-to-MIDI AI music plugin for a DAW that can help develop editable melody, chord, drum, and bassline parts from prompts.

Explore MIDI Agent