Falcosoft wrote on 2026-05-02, 04:59:Hi,
I meant a screenshot about the ...About box where the versions can be seen.
BTW, I have just tested also the newest test ver […]
Show full quote
zaphod77 wrote on 2026-05-02, 04:42:i think it's because i'm on windows 11. […]
Show full quote
i think it's because i'm on windows 11.
you are on windows 10, and it works.
messing with compatibility didn't help.
for my final test i'm closing down chrome completely.
didn't matter. tyrus 1,256,000,000 ver and vampire do not load, and it's definitely the 32 bit player
test version didn't change anything.
Hi,
I meant a screenshot about the ...About box where the versions can be seen.
BTW, I have just tested also the newest test version on Win 11 and it works perfectly :
The attachment vampire_w11.png is no longer available
Some things you can try:
1. Try to run FSMP as Administrator (although this is not needed, maybe it can show what kind of problem you have).
2. Make sure the dll is not blocked by Windows (blocked state is the default for downloaded files).
Finally I could reproduce the problem related to Vampire VSTi.
The point is that you have to have at least that much free and continuous memory as the plugin's payload size. In case of Vampire it is about ~1.4 GB.
You can check the free and continuous memory by looking at Main Menu -> About... -> Detailed Memory Info -> Largest Free Block 1 field:
The attachment free_mem.png is no longer available
Vampire is a 32-bit plugin so it only works with the 32-bit version of Midi Player. By default 32-bit applications only have 2GB address space available. This can be a problem for such large plugins and SF2 soundfonts.
Windows restart can help (as zaphod77 wrote) since after a fresh restart the memory is less fragmented. But after using Windows/32-bit Midi Player for a while the problem can appear again.
There is a PE flag (Large Address Aware) that can be set to allow 32-bit applications to use up to 4GB memory. It has some risks since all the plugins and external libraries also have to support large addresses to prevent problems.
It's hard to test and I have met VST effect plugins that cannot work with large addresses. That is why this PE flag is not set for the 32-bit Midi Player by default.
But you can do it for yourself if you have to deal with such large VST(i) plugins or SF2 soundfonts. Vampire has no problem with large addresses so it is recommended to set the flag for this plugin.
Here is a package that helps doing this:
The attachment Largea.zip is no longer available
You have to copy both files into Midi Player's folder and then start Largea.bat. The you should see this result page:
The attachment large_address_aware.png is no longer available
After running Largea.bat you should check Main Menu -> About... -> Detailed Memory Info. You can see that the virtual address space is doubled and you should see larger free continuous blocks:
The attachment free_mem_4G_Address.png is no longer available