search

vogonsorg / fluidsynth

Software synthesizer based on the SoundFont 2 specifications
https://www.fluidsynth.org
GNU Lesser General Public License v2.1
0 stars 0 forks source link

Not compatible with XP, find last working ver #1

Open vogonsorg opened 2 years ago

vogonsorg commented 2 years ago

FluidSynth version

Execute fluidsynth --version and provide the output.

Describe the bug

Provide a clear and concise description of the current situation, e.g. how the bug manifests.

Expected behavior

Provide a clear and concise description of what you expected to happen.

Steps to reproduce

Please explain the steps required to duplicate the issue, esp. if you are able to provide a sample application. E.g. how to start fluidsynth, what shell commands to enter, what midi events to send, etc.

Additional context

If you are able to illustrate the bug with an example, please provide simple source code below or as attached file. List any other information that is relevant to your issue, e.g. stack traces, related issues, build logs, suggestions on how to fix, links to related discussions at fluid-dev, etc.

insert code snippets, soundfonts or anything relevant here, or attach it as extra file(s) if it's too much
Gerwin2k commented 2 years ago

Earlier I found a precompiled v2.01 (10-2018) working on Windows XP: https://sites.google.com/site/qsynthwindows/binarios-de-fluidsynth-2-0-1

I did compile FluidSynth up to v1.1.11 (05-2018) with MSVC 10 / 2010, and that worked.

Just checked out the official binary releases, which they now offer for download since v2.1.5 (09-2020): fluidsynth-2.1.7-winXP-x86 (01-2021) -> Works in XP fluidsynth-2.2.0.beta1-winXP-x86.zip -> Starts but gives wasapi and midi-in errors. No sound. fluidsynth-2.2.1-winXP-x86.zip -> Starts but gives wasapi and midi-in errors. No sound. fluidsynth-2.2.4-winXP-x86.zip -> Starts but gives wasapi and midi-in errors. No sound.

Gerwin2k commented 2 years ago

Did some further investigations:

Latest fluidsynth-2.2.4-winXP-x86.zip is actually Windows XP compatible.

But since 2.2.0-beta it no longer accepts this parameter that was in my batch files: -o midi.winmidi.device="MIDI Portname of your system" I found it now requires: -o midi.winmidi.device="x:MIDI Portname of your system" Where x is the index number of the port, first one being 0. You can of course skip such a parameter when the midi port is port 0, it will be used by default. Also it accepts just the index number like this: -o midi.winmidi.device=0

The wasapi error is still there, but it is not fatal.

I can build v2.2.4 on Windows XP with MSVC 10 / 2010. I failed to build it on Windows XP with GCC 8, because of libgthread exports issues. The created libfluidsynth-3.dll looks for g_mutex functions in libglib-2.0-0.dll which are not there.