Test MIDI data

Topic actions

  • This topic is locked. You cannot reply or edit posts.

First post, by Snover

User metadata
Rank l33t++

It would also be useful if someone with a MIDI editing program could create some basic test files, including:

  • Volume tests (fades, hard cuts)
  • Tuning tests (master tune, individual instrument tune, chords)
  • SysEx patch tests (instrument uploads and playback)

Here are some locations to an abundance of test files, and some specific ones for testing:

From Soundfont Island:
Monkey Island 2

From Quest Studios:
Space Quest 3 (full with internal SysEx) MT-32 / MP3
Space Quest 4 (full with internal SysEx) MT-32 / MP3

More, from "Illusion City" (note, may be invalid, reference audio is from a CM-64)

I am uncertain of the state of SysEx on the Soundfont Island files.
For the Quest Studios files, individual songs come with external SysEx patches (if SysEx was used) or internal (built into the MIDI file) SysEx if it is a collection.

Yes, it’s my fault.

Reply 1 of 6, by MiniMax

User metadata
Rank Moderator

For PC game MIDI music I like Lauras MIDI Heaven.

DOSBox 0.73 ReadMe | DOSBox Wiki | DOSBox 60 seconds guide | How to ask questions
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Win 10 Pro

Reply 2 of 6, by Kaminari

User metadata
Rank Oldbie

Loom and MI2 from Soundfont Island sound correctly on my CM-500. MI2 definitely has an embedded sysex; Loom doesn't have one, but that's probably because it uses the default MT-32 timbres.

About external sysex files, there seems to be a problem with Munt. No sysex manager I tried will succeed in transmitting the patches. Results range from error messages like 'floating point division by zero' (SendSX) to plain crashes. Besides, some MIDI players like Kobarin's MediaPlayer seem unable to transmit embedded sysex to the virtual MT-32 driver without crashing, while others (Yamaha's MidRadio) won't complain.