Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Unable to get newer foo_midi versions (Read 2055 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Unable to get newer foo_midi versions

I didn't want to have to do this (register just to get an answer to my problem), but it seems I have little choice. I can't seem to find any other topic with a similar problem, and I can't find any way to contact kode54 directly.

I still remember how excited I was when a MIDI plugin was first created for foobar2000. But in recent iterations, it seems to have gotten worse. Granted, I can now load my own custom SoundFont, but it seems to handle reverb and chorusing/flange in a strange fashion, i.e., producing more than it seems there should be, especially on certain instruments.

I was hoping these quirks would be solved in later versions of the plugin. But alas! It seems I can't upgrade past my 1.122 version! Every time I try to download any newer version and re-load foobar, I receive this error:

Code: [Select]
Failed to load DLL: foo_midi.dll
Reason: The specified procedure could not be found.


Why can I not load a new version of this dll with my new version of foobar? Please, I hope someone can tell me what is going on!

Unable to get newer foo_midi versions

Reply #1 –
The entire component package must be installed correctly, including the bundled libraries. They should be placed in the same directory as the component itself. This is made easy by the component installer introduced in foobar2000 v1.1.

This problem may occur from having older versions of BASS and/or BASSMIDI in the foobar2000 main directory. Please do not keep those there when using this or other components which depend on those libraries. They should be installed in the component directory so they may be updated alongside the component.

Libraries loaded as hard imports in a component may be included in that component's own directory. Libraries loaded by soft imports should be loaded from the component's own directory first by design of the component, as that is outside the range of what the core does to facilitate the hard import paths.
 

Unable to get newer foo_midi versions

Reply #2 –
What he said. I just had to remove the bass.dll and bassmidi.dll from the root directory, and all was well.

Thread closed, may be locked now.