You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The package name in Debian is opl3-soundfont. And it is released under a CC-BY-SA 4.0 license.
My reasoning is that it sounds a lot better than the standard FluidSynth GM and GS SoundFonts that come with it. There are volume mixing issues with some instruments when using it. And in general, certain parts of the songs when played with the Jukebox sound terrible with the FluidSynth backend, and are often too loud.
I understand that OpenTTD heavily relies on Timidity+Freepats instead, but I thought a good alternative would be great.
I have also looked at these threads below, so I will reference them:
When I use flatpak run org.openttd.OpenTTD -m fluidsynth:soundfont=/app/share/sounds/sf2/FluidR3_GM.sf2, it works just fine.
However, when I try to run flatpak run org.openttd.OpenTTD -m fluidsynth:soundfont=/usr/share/sounds/sf2/OPL-3_FM_128M.sf2 it returns this error:
fluidsynth: error: fluid_sfloader_load(): Failed to open '/usr/share/sounds/sf2/OPL-3_FM_128M.sf2': File does not exist.
fluidsynth: error: Unable to open file '/usr/share/sounds/sf2/OPL-3_FM_128M.sf2'
fluidsynth: error: Failed to load SoundFont "/usr/share/sounds/sf2/OPL-3_FM_128M.sf2"
Error: Unable to load driver 'fluidsynth'. The error was: Could not open sound font
Even when specifying --filesystem=host or --filesystem=/usr/share/sounds/sf2/, it will still return the exact same error. So for some reason, it won't load.
I even did some research to find out that the mysterious /app/share/ directory actually points to /var/lib/flatpak/app/org.openttd.OpenTTD/x86_64/stable/<HASH>/files/share/, where appears to be some sort of checksum, likely SHA-256.
Anyway, when I copied over the /usr/share/sounds/sf2/OPL-3_FM_128M.sf2 (OPL-3 SoundFont) file to that /var/lib/flatpak/<...>/share/sounds/sf2/ directory, it still refused to load it at all.
If there is any way anybody knows how to make that work, or can provide a fix for OpenTTD, please let me know!
Version of OpenTTD
OpenTTD 1.10.3 (Flatpak stable repo)
The text was updated successfully, but these errors were encountered:
Hi, everyone,
I was hoping that the Flatpak version of OpenTTD could use this OPL3 sound font - https://github.com/Mindwerks/opl3-soundfont
The package name in Debian is
opl3-soundfont
. And it is released under a CC-BY-SA 4.0 license.My reasoning is that it sounds a lot better than the standard FluidSynth GM and GS SoundFonts that come with it. There are volume mixing issues with some instruments when using it. And in general, certain parts of the songs when played with the Jukebox sound terrible with the FluidSynth backend, and are often too loud.
I understand that OpenTTD heavily relies on Timidity+Freepats instead, but I thought a good alternative would be great.
I have also looked at these threads below, so I will reference them:
When I use
flatpak run org.openttd.OpenTTD -m fluidsynth:soundfont=/app/share/sounds/sf2/FluidR3_GM.sf2
, it works just fine.However, when I try to run
flatpak run org.openttd.OpenTTD -m fluidsynth:soundfont=/usr/share/sounds/sf2/OPL-3_FM_128M.sf2
it returns this error:Even when specifying
--filesystem=host
or--filesystem=/usr/share/sounds/sf2/
, it will still return the exact same error. So for some reason, it won't load.I even did some research to find out that the mysterious
/app/share/
directory actually points to/var/lib/flatpak/app/org.openttd.OpenTTD/x86_64/stable/<HASH>/files/share/
, where appears to be some sort of checksum, likely SHA-256.Anyway, when I copied over the
/usr/share/sounds/sf2/OPL-3_FM_128M.sf2
(OPL-3 SoundFont) file to that/var/lib/flatpak/<...>/share/sounds/sf2/
directory, it still refused to load it at all.If there is any way anybody knows how to make that work, or can provide a fix for OpenTTD, please let me know!
Version of OpenTTD
OpenTTD 1.10.3 (Flatpak stable repo)
The text was updated successfully, but these errors were encountered: