Hi Mrdangerous,

I assume you've missed one way to solve the problem you describe: downgrading the application. Munt version 2.4.0 incorporates a new implementation of the MIDI recording function, so regressions are well possible. To be honest, I only did no more than a smoke test of this particular function on Windows. You are welcome to rollback and try the previous version of the synth application which you can get from here.

Thanks for the unique suggestion! However, the problem seems to still be there. Loaded a save, recorded the midi, and played it back. Still messed up when played back in MUNT despite being fine during gameplay.
I gotta admit though that the sound is very different between those two versions. I suspect that would be due to the newer version being more accurate overall?
In any case, I attached redid the MEGA Rar to have that midi file in there (as the forum won't let me attach an older version of MUNT's Midi seemingly).

Well, if rolling back does not help, it seems that the problem lays in something different. The recordings attached suggest that they are missing SysEx messages that contain custom timbres/patches. I'll double-check if the new version records them correctly, but the old version surely did that.

Checked MIDI recorder on Windows and found no problems.

Obviously, when I start recording after the initial bunch of SysExes has passed already, the captured MIDI sounds weird. But when I start recording before starting a game, everything is dandy. Maybe ScummVM sends the SysEx bank differently these days?

I think you may have solved my problem! I had actually seen stuff about SysExs while trying to solve this issue on my own, even on this forum. However, I didn't really understand them that well and figured that they were something the game simply kept sending out instead of just doing it at the beginning. I did a few recordings with MUNT, but took your advice and recorded from the Logo start up and kept it going through the entire process instead of simply recording at the part that I wanted. It seems to work from even loading when doing this!
If I have any new issues of this manner I will put them in this thread, but I think for the moment you helped me understand what my problem is.
Thanks for expanding my knowledge of midis more!

As a suggestion though, maybe the install of MUNT could come with a "general tips" sort of readme in the "Docs" folder to explain things like this to people such as myself without the deep knowledge of how Midis fundamentally work, especially older types like the non-standard MT-32 variety, along with that whole actually uninstalling everything when using the uninstall program instead of leaving the settings (or maybe have a tickbox option to add deleting the settings as well). Just some extra thoughts I wanted to throw out there, but in any case thank you very much sergm!

Great, I'm glad you figured it out.

BTW, I have one more tip on MIDI recording. When a game uploads new tones at the very startup only (which is a quite common case), you may make a recording of that timbre bank just once. To make other recordings sound "correct", you may merely prepend that SysEx bank to each of captured tracks using a good MIDI editor. Alternatively, just play that timbre bank before a tune (though, the emulated synth should be "pinned" to avoid resetting between the played MIDI files).

And yes, I'm all for improving documentation 😀

Ah, so I can simply record the logo track at the beginning of the game, save that as a midi, and then simply have that pinned in MUNT while I play other tracks? Or is there some special method required to save SysEX files in midi format? I assume the former, but no harm in asking if it's the latter.

Yes, I mean exactly having a single "init" recording with just SysExes. But that will work if the game only loads custom timbres once at startup, of course. Some games are known to send timbres per tune, and rarely, even while playing a tune.

Oh midi, what a complex cloth you weave with all these strange differences between games. In any case, thanks for the extra clarification!