Hmm, so it needs to be MIDI but needs to include sysex data? I think just capturing / trimming a MIDI capture of the output of mt32-pi-control should achieve that. The syntax for the sysex messages looks simple enough, but making that into a MIDI seems pretty complicated, comparing it with a similar implementation.
I think this is the best utility to use to send the sysex messages right now: https://github.com/gmcn42/mt32-pi-control

There's something similar for reconfiguring the MT32 to work as close as possible to a GM device with MTGM.MID: http://www.houseofsynth.com/roland-mt-32-to-g … version-utility

So with the utility, and something to capture MIDI output, it should be possible.

In your setup you'll probably want different MIDI files to perform each switch. You can't pass a parameter to the file so each like you had in your example you'll have one that does switch to soundfont 0, soundfont 1, etc. Another thing to consider is that it will take at least a second or two for the new soundfont to load, you may want to have some empty padding so the switch is performed and then a few seconds of silence, otherwise you could be missing the beginning of the next track.

Thermalwrong wrote on 2021-04-27, 10:10:

Hmm, so it needs to be MIDI but needs to include sysex data? I think just capturing / trimming a MIDI capture of the output of mt32-pi-control should achieve that. The syntax for the sysex messages looks simple enough, but making that into a MIDI seems pretty complicated, comparing it with a similar implementation.

Thanks, I'll have a look into that.

SScorpio wrote on 2021-04-27, 12:14:

In your setup you'll probably want different MIDI files to perform each switch. You can't pass a parameter to the file so each like you had in your example you'll have one that does switch to soundfont 0, soundfont 1, etc. Another thing to consider is that it will take at least a second or two for the new soundfont to load, you may want to have some empty padding so the switch is performed and then a few seconds of silence, otherwise you could be missing the beginning of the next track.

What you have described - a separate file for each soundfont selection - is basically what I had in mind. That would allow the setup of customised playlists involving myriad soundfonts - press play, then forget about it and get on with work.

As per your smart suggestion thanks, I should indeed add a couple bars of rests to allow for SF2 load time. Based on knowing how long each SF2 takes to load, can also tailor that rest phase to suit each SF2's particular loadtime requirement.

My impression from quick Googling (e.g., + reference image below) is that MIDI experts could manually whip up such things in a text or hex editor. Header, one track, SYSEX instructions, rests, done. But as a MIDI-file-format noob - albeit ok with music theory - it's going to take some time to turn that simple abstraction into coded reality.

Perhaps further research will allow me to alter the above to suit.

Spent some time reading about the granular detail of the MIDI file format.

Had to skim over some parts as it's a bit of a rabbit-hole, and I don't really want to invent the whole world just to have a cup of tea (you know how it is).

Made a couple of initial attempts at manually constructing a rudimentary .mid containing just the SYSEX instruction, but what I have tried so far is having zero effect at all upon the unit when played. (e.g. the below is supposed to send the sysex "03 00" to the MT32pi, which should cause it to change from Soundfont Mode to MT-32 Mode.... but nothing happens)

<now-redundant image redacted>

I'll keep beavering away at it. If anyone can see any obvious errors in the above, or methodology, please let me know.!GAH! SPOKE TOO SOON. FOUND A SIMPLE ERROR. (I'd left the manufacturer code out of the sysex instruction ... which means then having to increment the length bytes for the Mtrk & Sysex too, <micro-sigh>).

So here's the working one:

Does the main job. Now I'll pad it out with the necessary hold-times etc, to end up with the MT32-Pi's full control set in MIDI form. Pleased!

Hi,
1. You said you used FSMP for playback. In the right click context menu of the playlist you can find 'Pause between Songs' and you can set 0,1,2,3 sec. pause so setting delay in the Midi file itself is not so necessary. I think 2 sec. delay between Midi files is ideal regardless of soundfont switching and most likely it's also enough for reasonable sized soundfonts to load.

2. With the help of FSMP + SYXtoMID you can speed up the creation process of your Midi files with included SyeEx.
Use right click context menu of 'Reset' button ->Select /Send Custom SysEx. Here you should check 'Use Hex String' and type the required SysEx message. In your case e.g: F0 7D 02 01 F7 to change soundfont to 1. Then press 'Save as Syx'. Finally open the saved Syx in SYXtoMID.exe and set your desired delay in 'Packet Delay(ms)'.

Falcosoft wrote on 2021-04-29, 07:43:

Hi, 1. You said you used FSMP for playback. In the right click context menu of the playlist you can find 'Pause between Songs' […]
Show full quote

Hi,
1. You said you used FSMP for playback. In the right click context menu of the playlist you can find 'Pause between Songs' and you can set 0,1,2,3 sec. pause so setting delay in the Midi file itself is not so necessary. I think 2 sec. delay between Midi files is ideal regardless of soundfont switching and most likely it's also enough for reasonable sized soundfonts to load.

2. With the help of FSMP + SYXtoMID you can speed up the creation process of your Midi files with included SyeEx.
Use right click context menu of 'Reset' button ->Select /Send Custom SysEx. Here you should check 'Use Hex String' and type the required SysEx message. In your case e.g: F0 7D 02 01 F7 to change soundfont to 1. Then press 'Save as Syx'. Finally open the saved Syx in SYXtoMID.exe and set your desired delay in 'Packet Delay(ms)'.
SYXtoMID.zip

Awesome, thanks! Shows I've still got a lot to learn about FSMP.

Attached a basic set in case anyone wants to bend to their own purposes.