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: foo_midi (foobar2000 v2.0) (Read 50198 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: foo_midi (foobar2000 v2.0)

Reply #275 –
Quote from: pqyt on
Quote from: raekuul on
The current version seems to be ignoring libADLMIDI and libOPNMIDI if a soundfont path is set - regardless of what player I choose the console reports the following:

Code: [Select]
Opening track for playback: "D:\Synth\rips\1991 - Jimmy White's Whirlwind Snooker\01 - Snooker.mid"
foo_midi failed to initialize FluidSynth: Invalid FluidSynth directory: The system cannot find the path specified (0x00000003)
foo_midi uses SoundFont "D:\soundfonts\HiDef.sf2" with bank offset 0.

clearing the soundfont path allows libADLMIDI and libOPNMIDI to operate as normal, it's only when a soundfont path is set that they're getting overridden.
Thx. for reporting. The player override logic has been updated to support layered soundfonts but it looks like it's a bit too assertive.
Fixed in 2.15.1.