I use nanohost to open the VST, since Midiplayer does lock up when I send XG through the midi cable to play the Yamaha VSTs and it also does not like to save stuff in the VST.

Hi,
1. What steps should I try to reproduce this lock up problem? (e.g. what VSTi you used exactly etc.)
2. There is no such VSTi config saving problem that I know of. You have to save the settings manually to an .fxb file by pressing 'Save' in the VSTi dialog. This way you can have multiple settings instead of 1 automatic one. You can also auto-load the last loaded/used settings at startup if you check the 'Autoload last used settings file' checkbox (besides 'Autoload at Startup').

BTW, if you have Midi Player related problems you can report them here:
Falcosoft Soundfont Midi Player + Munt VSTi + BassMidi VSTi

Also there is a new test version with a new Bass_VST library. You can try it to see if it helps with your lock up problem.
https://falcosoft.hu/midiplayer_61_test.zip
Bye

Hey Falcosoft, I can usually lock up midi player when I feed xg midi to the s-yxg50 vst through a real midi connection from one pc to another.
From one audigy to another or from a audigy to my main pc with a m-audio usb midi dongle or the other way around, does not matter.
It will hang and not stop changing banks and instruments, even when I stop the playback feed on the other computer.
I tested it on Windows XP Sp3, Windows 7, Windows 10 and with Wine in Raspberry Pi OS.

And yes you are spot on with the saving, I am just a little stupid. Sorry I am new to this midi and vst stuff. I usually only loaded the biggest
soundfont that I could fit into my ram.

You can recreate this by sending a XG midi internally through loop midi from the new player to the old one, the vst interface will lock up but continue to play.
The new player seems to work fine. Thanks buddy!

Robertkopp wrote on 2022-04-12, 00:30:

You can recreate this by sending a XG midi internally through loop midi from the new player to the old one, the vst interface will lock up but continue to play.
The new player seems to work fine. Thanks buddy!

Hi,
No matter how hard I tried I could not reproduce your lock up issue. I used your zip packaged Midi Player 6 (together with your config) as host and the new version as the client. Here is the video about my test:
https://youtu.be/v0fA8O_88pI
Maybe in such cases you should try 'Main menu -> Storage of Settings -> Reset Settings to Default' to determine if some corrupted settings are causing your problems or not.

@Edit
Some tips for your packaged Midi Player config in the zip:
1. It's not the best option to enable 'Channel -> Follow' in Midi In configuration section if your main goal is Midi file playback. It's mainly for manual playing on Midi keyboards so that the player reflects the used channel (usually only 1). In case of playing back files the interface switches back and forth like crazy since Midi files send messages to different channels interleaved.
2. You should not set 'Use Capital Tone Fallback' and select the GS mode instrument definitions of S-YXG50 as default. It can ruin XG Midi playback (e.g Drums become piano since bank 127 on channel 10 is not defined in GS mode).
3. It's not portable if you leave absolute paths in the config file (Midiplayer.ini) for your VST(i) plugins or soundfonts. You can edit Midiplayer.ini with any text editors to set relative paths that reflect the structure of folders in your package.
As an example you can have a look at the Midiplayer.ini file in the Bassmidi edition of Midi Player that uses relative paths the above described way:
https://falcosoft.hu/midiplayer_60_bse.zip

Thanks for the tips, it does not hang anymore at all. I wish there was a MIDI guide for the total noob, but that is what I am also working on.

I tested the Raspberry Pi one more time. I had the idea from a guy using reaper and vsts on the pi and he does not seem to have had any problems.
It's just powerful enough, but any hiccup will ruin your midi playback until you restart the vst.
I think I will follow his advice and get the original power supply to rule everything else out.
I had the lightning symbol on this device with another install. This would also allow a bit of a overclock, which should give me a little more headroom.

Finally I tested the virtual midi synth drivers for win9x. The Edirol VSC just crashes while installing and with the Yamaha we got the same result as in XP, no driver installed.

the google drive link has been TOSsed. 🙁