With files ripped from a SHARP X68000 game, I get messages on stderr such as these when played from the built-in "MIDI Player" (from both raw SysEx and standard midi format files) and the programming is done improperly as a result:
MidiParser: Fragmented SysEx / escape, unsupported
MidiParser: Adding sync event for 2 divisions
MidiParser: Fragmented SysEx / escape, unsupported
MidiParser: Adding sync event for 2 divisions
MidiParser: Fragmented SysEx / escape, unsupported
MidiParser: Adding sync event for 2 divisions
MidiParser: Fragmented SysEx / escape, unsupported
MidiParser: Adding sync event for 2 divisions
MidiParser: Fragmented SysEx / escape, unsupported
MidiParser: Adding sync event for 3 divisions
... snipped...
MT32: "playSysex: Message lacks end-of-sysex (0xf7)"
MT32: "playSysex: Message lacks end-of-sysex (0xf7)"
MT32: "playSysex: Message lacks end-of-sysex (0xf7)"
MT32: "playSysex: Message lacks end-of-sysex (0xf7)"
MT32: "playSysex: Message lacks end-of-sysex (0xf7)"
It doesn't only affect version 2.1.0, as I also saw it in 1.5.0 (but I haven't testet earlier)
The interesting thing is, it's probably a simple bug because, read from MUNT's input port, playing from external MIDI players (tested in audacious2 and aplaymidi) works great, with no stderr messages of the kind and proper programming.
I'm attaching two example files which should contain the same data (one in raw SysEx format and the other in SMF)
This was also mentioned, as I discovered it, in this thread: https://www.midimusicadventures.com/phpbb/viewtopic.php?f=4&t=28
Ticket moved from /p/munt/bugs/29/