Please help with Midifile optimizer

Please let our ADS show!

This sites offers only FREE software and it's supported by a few advertisement boxes (no intrusive popups).
Please:

  • disable your AdBlocker by adding CoolSoft website to whitelist
  • give the proper cookie consent
  • enable JavaScript for this website

This seconds wait is to let you update your browser configuration...

Ok, I've done the required changes... now show me your content!
!!! Please enable JavaScript !!!
Posts: 4
Joined: April 19, 2017 - 12:40
Please help with Midifile optimizer

I use Midifile optimizer. We used several versions of software, but also several adjustments when upload an SMF receive the following message http://img217.imageshack.us/img217/8540/virtualmidisyntherror.jpg . I would be very grateful for a donation even if I get help. Thank you!

Posts: 1972
Joined: March 25, 2012 - 01:19
This is a DLL versioning issue

This is a DLL versioning issue:

I tried version 7 trial (the last one) of Midifile optimizer and it works, no issues.
So I searched for an older version 5 trial (the same version you have, as for the linked screenshot) and with this one I got the same error you have.

The issue is related to Midifile optimizer using the same BASS libraries I use for VirtualMIDISynth.
Midifile optimizer 5 uses a really old BASS library version 2.3.x (which misses the required BASS_UpdateChannel function), while Midifile optimizer 7 uses the newer 2.8.x series.

That said, there's really nothing I can do to fix this error, this is an architectural limit of Windows User Mode drivers: they are DLLs, so they're loaded into the same process space as the client.
When you load Midifile optimizer it loads its own DLLs, including BASS.dll. Choosing VirtualMIDISynth as your output device will cause VirtualMIDISynth.dll to be loaded inside Midifile optimizer process.
VirtualMIDISynth now can't load BASS.dll again, because it was already loaded by the host process  (Midifile optimizer), so it is forced to use the already loaded one.
This works only if the already loaded BASS DLL is compatible with the one expected/required by VirtualMIDISynth.

To solve the architectural limit, a 2.x version of VirtualMIDISynth is being developed. In this version the driver and the sound-server are two separate processes; the first (loaded into MIDI client) won't use BASS at all, so it should be compatible with every MIDI application; the latter is the process which renders MIDI sound and, being a separate process, it could load its own BASS library.
A preview of the 2.x version of VirtualMIDISynth has been released here: http://coolsoft.altervista.org/comment/457#comment-457
Please note that it's not ready for production use, only for testing!

Finally you have two choices:

  1. upgrade Midifile optimizer to version 7 (I don't know how much does it costs and if it worths a try)
  2. try the 2.x version of VirtualMIDISynth (and give me confirmation that it works)
Posts: 4
Joined: April 19, 2017 - 12:40
Thanks for your reply! I

Thanks for your reply! I tried all the variations I found on this site, all displaying the same error. I've downloaded the software demo Midifile Optimizer 7 and it works. It will cost 100 euros to upgrade from 5 Pro and hopefully it will worth every penny. I say this because I found some tones out of control and it  sounds long. I tried 3 SoundFont packs with the same problem. On XP I used Roland VSC and Yamaha XG Synthesizer. They have worked very well with Midifile Optimizer. I have a Dell laptop with i7 processor, 6 gb ram Windows 7 64bit. I installed XP on it but I didn't found all the drivers needed. It is interesting that the old Cakewalk 9.03 which are usually works flawlessly Van Basco also works well. It's very difficult to work with MIDI on the W7. I don't know what the people from Microsoft thought. The Midi had left as it was on XP. Again all respect for your work and further success.

Posts: 1972
Joined: March 25, 2012 - 01:19
If W7 is poor on MIDI side,

If W7 is poor on MIDI side, W8 is even worst...
I don't know if 100€ worths a try, that's up to you wink.

Anyway version 2.x of VirtualMIDISynth can't show that error message, because it simply doesn't load BASS dll dynamically.
And so it should work with Midifile Optimizer 5.

Have you tried it?
Please note that it's not "officially" available, but you can find its download link here: http://coolsoft.altervista.org/comment/457#comment-457.