mashakos wrote on 2026-01-26, 04:07:Don't know if this is the right place to ask, but I'm trying to set up FSMP MIDI Player with vstdriver's VST Midi proxy + loopMI […]
Show full quote
Don't know if this is the right place to ask, but I'm trying to set up FSMP MIDI Player with vstdriver's VST Midi proxy + loopMIDI + Coolsoft MIDI Mapper and haven't quite gotten vstdriver proxy to play nice with FSMP.
After following instructions, I started with:
Creating a port named FalcomodPort in loopMIDI
ensure that loopMIDI is running
VST Midi proxy running
Set vstdriver MIDI port to "FalcomodPort" in vstdriver config MIDI tab
Result:- no audio in FSMP MIDI Player
--------
after that I tried all of the above except:
Set vstdriver MIDI port to "VST MIDl synth Global (port A)" in vstdriver config MIDI tab
Audio now works and is being run through the proxy, but any 32ch midi is mangled with incorrect timing of instruments
--------
Summary: in vstdriver, if I set the port to loopMIDI "FalcomodPort", no audio in FSMP. If I set port to "VST MIDl synth Global (port A)" midi file audio plays through FSMP but it's mangled. Setting port to "MIDl synth (port A)" works fine but then I lose the convenience of FSMP not needing to pause while vstdriver loads vsti plugin dll.
Hi,
VST MIdi Proxy is based on LopMidi's kernel driver which does not support the needed 0xF5 port select Midi message. So multi port /32 channel Midi files do not work with either LoopMidi or VST Midi Proxy. Since LoopMidi's development seems to have been stopped and the author does not respond to messages there is not much hope of fixing left.
So for multi port Midi files you have to use the non-global ports of the VST Midi driver.
Set vstdriver MIDI port to "FalcomodPort" in vstdriver config MIDI tab
It seems you misunderstood the role of the MIDI tab. It does not set something special for VST driver.
Actually it only does what Coolsoft's Midi mapper does. That is it sets the default Midi out port for all other Midi programs that use the default port by design.
This is not relevant for FSMP at all since in FSMP you can set the desired Midi out port explicitly.
Overall in the context of FSMP I think you should always use the normal/non-global VST Midi driver ports since FSMP does not close the connection to the ports when a track playing is finished (unlike e.g. Windows Media Player) . Thus the driver stays loaded and you do not have to pause the player when you want to change plugin. In this regard everything should behave the same way as with the global proxy ports.
The global Midi proxy was mainly written for Midi players like Van Basco and WMP that close the connection after each track and thus you have to wait for loading heavy plugins before another track can be played. FSMP does not work this way.
