I'm using a 486 playing a game that uses MIDI signals (Ultima Underworld 1). it sends them out its joystick port pin12 (so far, nothing special). This gets converted with my custom cables into a midi cable, that I send into a modern MIDI USB interface, plugged on my 2024 PC. I then intercept those MIDI signals with the darker window screencapped above. I can analyze which instrument is loaded as the command passes through. I can learn which instrument # is being used as a playback is done. for bonus points, I'm using MIDITRIX, a midi matrix input/output setter so that the signal will not be merely analyzed and stopped on my 2024 PC, but will also get sent back through the midi interface, back into a real Roland MT-32 so I can also hear it as intended, while it's being scrutinized
Goals with this: I can spy which instrument is being used in MT-32 or sound canvas music for each channel and I can reproduce them by playing/recording them one by one, to do some covers...........
Setup #1 used:
486's midi out to modern usb 1x1 midi interface's IN (plugged into a modern 2024 PC).
usb 1x1 OUT to MT-32 in.
MIDItrix modern app acting as a signal repeater to make the interface act as a THRU
MIDIView to display MIDI commands as they're read from the interface in real time
Problem with setup #1: most of the time, it will give a blue screen of death (even in windows 11) because I guess it creates an avalanche of midi command echoes since the IN and OUT are through the same device. I swear it has worked temporarily under certain conditions
Last edited: