zaphod77 wrote on 2026-09-05, 16:05:

So we still need vst midi driver to mix 64 and 32 bit plugins, while we can directly use sc va and 64 bit clap plugins in 64 bit player, and everything else needs 32 bit player, right?

If you have JBridge 1.76+ then you can use 32-bit plugins also with the 64-bit version of FSMP. E.g. S-YXG50 works perfectly.
Support for JBridge is integrated into my fork of BASS_VST so no wrappers/renamed dll files are required. If you have JBridge v1.76+ installed you can load the 32-bit VSTi dll files directly from 64-bit FSMP.

That helps. I'll probably still stick to vst midi synth, as that handles things, and jbridge isn't free.

I also figured out how to use multiport mode of VST Midi Synth with other stuff. as long as the sequencer/player understands port select meta events, and has the ports mapped in it, you can use it.

I was able to load up END.MID in cakewalk, and as long as both vst midi ports are configured in the midi device setup (as both selected) then the midi plays back properly. Both copies of Sound Canvas VA will open.

For those who have a free cakewalk 9, and want to mess with multi port midis, you simply have to open device setup, move vst-synth port a and port b to the top, and select them both before clicking okay. then the midi port events will direct the tracks to the ports desired. This works with existing midi files and any new ones you want to make.

When 88Emu gets released it should be just as usable, because it should bind to the appropriate virtual midi cable ports on load like nuked-sc55.

Unfortunately the release announcement became the last but one post of the previous page. So once again:
FSMP version 6.6 has been released:
https://falcosoft.hu/softwares.html#midiplayer

Original post:
Re: Falcosoft Soundfont Midi Player + Munt VSTi + BassMidi VSTi

Thank you for your continued work on your MIDI player and your other software projects. Your efforts are greatly appreciated.

Falcosoft wrote on 2026-09-05, 10:27:

FSMP version 6.6 has been released: https://falcosoft.hu/softwares.html#midiplayer Test version is no longer available. […]
Show full quote

FSMP version 6.6 has been released:
https://falcosoft.hu/softwares.html#midiplayer
Test version is no longer available.

version 6.6

1. Added GS/XG LCD Bitmap display to Visualization dialog. LCD Bitmap display related settings can be changed in the right click context menu of the dialog.
2. Added Midi 2.0 Clip file format support (.midi2) . Midi 2.0 events are converted to Midi 1.0 events s so the conversion is lossy.
3. Added Human Interface Music file format support (.hmi, .hmp).
4. Added MusicXML file format support. Zip compressed version is also supported (.xml, .mxl, .musicxml).
5. Added option to enable sending SysEx messages during seeking (Main menu -> SysEx options).
6. Added 'Autoselect Patch Names' option based on linking Midi systems to instrument definition files.
7. Added /render parameter to render wave files offline mode from command line.
8. Added BssMidiFontInitFlags and Emulate SC-55 drums option to the Bassmidi settings part of the Device Settings dialog.
9. Added new version 3.0 of the MUNT VSTi plugin (supporting the new external MT-32 Editor library).
10. Added new version of the Mod2Midi converter.
11. Added Clap to VST2 wrapper plugin to the x64 version so CLAP plugins like Nuked SC-55 CLAP version can be used as a VST2 plugin.
12. Many other fixes and enhancements.

Hi Falco,

I wanted to try the Clap to VST2 wrapper out, but it didn't work for me:

I copied the Nuked-SC55.clap and the clapasvst2.dll to a distinct folder then renamed the clapasvst2.dll to Nuked-SC55.dll (If I understood the instruction correctly).
But when I tried to load the Nuked-SC55.dll, i got the error message: "VSTi Plugin cannot be loaded! Make sure you selected a valid 64 bit VSTI plugin."

What did I do wrong? Thanks!

You probably made the same mistake as I: Not providing the ROM files for ALL SC-55 variants. Only creating a folder with the ROM you actually want to use isn't enough. You may have even tried to run this without any ROM files at all, which would lead to the same result. See here for details about a solution.

Note that I have also posted a step-by-step guide over at the Duke4.net forums, maybe this will also prove to be useful to you.

Trelokk wrote on 2026-09-13, 10:25:

You probably made the same mistake as I: Not providing the ROM files for ALL SC-55 variants. Only creating a folder with the ROM you actually want to use isn't enough. You may have even tried to run this without any ROM files at all, which would lead to the same result. See here for details about a solution.

Note that I have also posted a step-by-step guide over at the Duke4.net forums, maybe this will also prove to be useful to you.

Thank you, it works! (I tought I had to manually select the appropriate ROM files AFTER loaded the plugin as for the MUNT VSTi).

Lord Myn wrote on 2026-09-13, 10:11:

Hi Falco, […]
Show full quote

Falcosoft wrote on 2026-09-05, 10:27:

FSMP version 6.6 has been released: https://falcosoft.hu/softwares.html#midiplayer Test version is no longer available. […]
Show full quote

FSMP version 6.6 has been released:
https://falcosoft.hu/softwares.html#midiplayer
Test version is no longer available.

version 6.6

1. Added GS/XG LCD Bitmap display to Visualization dialog. LCD Bitmap display related settings can be changed in the right click context menu of the dialog.
2. Added Midi 2.0 Clip file format support (.midi2) . Midi 2.0 events are converted to Midi 1.0 events s so the conversion is lossy.
3. Added Human Interface Music file format support (.hmi, .hmp).
4. Added MusicXML file format support. Zip compressed version is also supported (.xml, .mxl, .musicxml).
5. Added option to enable sending SysEx messages during seeking (Main menu -> SysEx options).
6. Added 'Autoselect Patch Names' option based on linking Midi systems to instrument definition files.
7. Added /render parameter to render wave files offline mode from command line.
8. Added BssMidiFontInitFlags and Emulate SC-55 drums option to the Bassmidi settings part of the Device Settings dialog.
9. Added new version 3.0 of the MUNT VSTi plugin (supporting the new external MT-32 Editor library).
10. Added new version of the Mod2Midi converter.
11. Added Clap to VST2 wrapper plugin to the x64 version so CLAP plugins like Nuked SC-55 CLAP version can be used as a VST2 plugin.
12. Many other fixes and enhancements.

Hi Falco,

I wanted to try the Clap to VST2 wrapper out, but it didn't work for me:

I copied the Nuked-SC55.clap and the clapasvst2.dll to a distinct folder then renamed the clapasvst2.dll to Nuked-SC55.dll (If I understood the instruction correctly).
But when I tried to load the Nuked-SC55.dll, i got the error message: "VSTi Plugin cannot be loaded! Make sure you selected a valid 64 bit VSTI plugin."

What did I do wrong? Thanks!

You should try what Trelokk suggested.
It's not intuitive at all but you need all known ROM versions in order Nuked SC-55 CLAP version to work. This is not a requirement of the wrapper or FSMP but the CLAP plugin itself. You can find the needed ROMs here:
https://archive.org/details/nuked-sc-55-clap-rom-files

Falcosoft wrote on 2026-09-13, 10:58:

You should try what Trelokk suggested. It's not intuitive at all but you need all known ROM versions in order Nuked SC-55 CLAP […]
Show full quote

Lord Myn wrote on 2026-09-13, 10:11:

Hi Falco, […]
Show full quote

Falcosoft wrote on 2026-09-05, 10:27:

FSMP version 6.6 has been released: https://falcosoft.hu/softwares.html#midiplayer Test version is no longer available. […]
Show full quote

FSMP version 6.6 has been released:
https://falcosoft.hu/softwares.html#midiplayer
Test version is no longer available.

version 6.6

1. Added GS/XG LCD Bitmap display to Visualization dialog. LCD Bitmap display related settings can be changed in the right click context menu of the dialog.
2. Added Midi 2.0 Clip file format support (.midi2) . Midi 2.0 events are converted to Midi 1.0 events s so the conversion is lossy.
3. Added Human Interface Music file format support (.hmi, .hmp).
4. Added MusicXML file format support. Zip compressed version is also supported (.xml, .mxl, .musicxml).
5. Added option to enable sending SysEx messages during seeking (Main menu -> SysEx options).
6. Added 'Autoselect Patch Names' option based on linking Midi systems to instrument definition files.
7. Added /render parameter to render wave files offline mode from command line.
8. Added BssMidiFontInitFlags and Emulate SC-55 drums option to the Bassmidi settings part of the Device Settings dialog.
9. Added new version 3.0 of the MUNT VSTi plugin (supporting the new external MT-32 Editor library).
10. Added new version of the Mod2Midi converter.
11. Added Clap to VST2 wrapper plugin to the x64 version so CLAP plugins like Nuked SC-55 CLAP version can be used as a VST2 plugin.
12. Many other fixes and enhancements.

Hi Falco,

I wanted to try the Clap to VST2 wrapper out, but it didn't work for me:

I copied the Nuked-SC55.clap and the clapasvst2.dll to a distinct folder then renamed the clapasvst2.dll to Nuked-SC55.dll (If I understood the instruction correctly).
But when I tried to load the Nuked-SC55.dll, i got the error message: "VSTi Plugin cannot be loaded! Make sure you selected a valid 64 bit VSTI plugin."

What did I do wrong? Thanks!

You should try what Trelokk suggested.
It's not intuitive at all but you need all known ROM versions in order Nuked SC-55 CLAP version to work. This is not a requirement of the wrapper or FSMP but the CLAP plugin itself. You can find the needed ROMs here:
https://archive.org/details/nuked-sc-55-clap-rom-files

Thank you too. Yes, I had all the ROM files, but didn't know the CLAP version worked that way.
But in the meantime, I have another question: How the GS/XG LCD bitmap display works? I've turned it on in the dialog box, but it has no effect.

Lord Myn wrote on 2026-09-14, 08:41:

Falcosoft wrote on 2026-09-13, 10:58:

You should try what Trelokk suggested. It's not intuitive at all but you need all known ROM versions in order Nuked SC-55 CLAP […]
Show full quote

Lord Myn wrote on 2026-09-13, 10:11:

Hi Falco, […]
Show full quote

Hi Falco,

I wanted to try the Clap to VST2 wrapper out, but it didn't work for me:

I copied the Nuked-SC55.clap and the clapasvst2.dll to a distinct folder then renamed the clapasvst2.dll to Nuked-SC55.dll (If I understood the instruction correctly).
But when I tried to load the Nuked-SC55.dll, i got the error message: "VSTi Plugin cannot be loaded! Make sure you selected a valid 64 bit VSTI plugin."

What did I do wrong? Thanks!

You should try what Trelokk suggested.
It's not intuitive at all but you need all known ROM versions in order Nuked SC-55 CLAP version to work. This is not a requirement of the wrapper or FSMP but the CLAP plugin itself. You can find the needed ROMs here:
https://archive.org/details/nuked-sc-55-clap-rom-files

Thank you too. Yes, I had all the ROM files, but didn't know the CLAP version worked that way.
But in the meantime, I have another question: How the GS/XG LCD bitmap display works? I've turned it on in the dialog box, but it has no effect.

You need Midi files that use such SysEx messages. Here are some examples for testing:

Falcosoft wrote on 2026-09-14, 09:21:

Lord Myn wrote on 2026-09-14, 08:41:

Falcosoft wrote on 2026-09-13, 10:58:

You should try what Trelokk suggested.
It's not intuitive at all but you need all known ROM versions in order Nuked SC-55 CLAP version to work. This is not a requirement of the wrapper or FSMP but the CLAP plugin itself. You can find the needed ROMs here:
https://archive.org/details/nuked-sc-55-clap-rom-files

Thank you too. Yes, I had all the ROM files, but didn't know the CLAP version worked that way.
But in the meantime, I have another question: How the GS/XG LCD bitmap display works? I've turned it on in the dialog box, but it has no effect.

You need Midi files that use such SysEx messages. Here are some examples for testing:

The attachment LCDBitmap_Midis.zip is no longer available

Ok, now I see it, thanks!

I have tested s-mu2k with vst midi driver and falcosoft, using the clap plugin wrapper.

when running as standalone you can just hook it up to your virtual midi ports, and falcosoft can find it, but you can only select one port that way, as falcosoft only lets you do two if using the vst midi drivers special 32 channel mode. Any midi player that actualy both understands port select tricks and allows you to pick multiple output ports as well will work fine with the standalone.

if you use vst midi driver, and 32 channel mode, it WILL work with midi player when bass mode is turned off, but it will of course run two instances. whether it works with everything else is very hit or miss. i had it totally crash the vst midi driver when i tried to open it in chiptune.app.

Note that even the genos keyboards you can get now only do XG level 1. that's why the final fantasy midis sound correct on them.

zaphod77 wrote on Today, 02:27:

I have tested s-mu2k with vst midi driver and falcosoft, using the clap plugin wrapper. […]
Show full quote

I have tested s-mu2k with vst midi driver and falcosoft, using the clap plugin wrapper.

when running as standalone you can just hook it up to your virtual midi ports, and falcosoft can find it, but you can only select one port that way, as falcosoft only lets you do two if using the vst midi drivers special 32 channel mode. Any midi player that actualy both understands port select tricks and allows you to pick multiple output ports as well will work fine with the standalone.

if you use vst midi driver, and 32 channel mode, it WILL work with midi player when bass mode is turned off, but it will of course run two instances. whether it works with everything else is very hit or miss. i had it totally crash the vst midi driver when i tried to open it in chiptune.app.

Note that even the genos keyboards you can get now only do XG level 1. that's why the final fantasy midis sound correct on them.

Hi,
Thank you for the testing!

1. FSMP allows you to select multiple output ports with the help of the included WinMM MultiPort plugin:

2. Can you share a download link for the 'chiptune.app' that caused the VST Midi driver crash?

@Edit:
Ahh, I think I found what you meant by 'chiptune.app'. It's this website, isn't it?
https://chiptune.app/
I have tested this website and I could not reproduce the crash you mentioned. Here is my test video:
https://youtu.be/gOZXWsdnMPY

@Edit2:
In case of these web applications the 'Keep host open even if ports are closed' option on the 'Advanced' tab of VST Midi driver's configuration dialog can help. It seems especially Chrome always opens and closes all available ports like crazy.

Yeah i couldn't reproduce it again either. but what happened was both opened up and the i hear da loud crack and both closed, and the vst driver icon just straight up vanished. i think it depends on what midi you try to play, because it loves to fast forward the start.

zaphod77 wrote on Today, 08:52:

Yeah i couldn't reproduce it again either. but what happened was both opened up and the i hear da loud crack and both closed, and the vst driver icon just straight up vanished. i think it depends on what midi you try to play, because it loves to fast forward the start.

As I said check the 'Keep host open even if ports are closed' option. Chrome opens/closes all available ports regardless if they are slected or not.