On Tue 04 Feb 2025 at 18:38:34 (+0100), Ben Engbers wrote: > It showed that fluid-soundfont-gm and fluid-soundfont-common were > already installed. I only had to add fluid-soundfont-gs. > > I also found this page: > https://discussion.fedoraproject.org/t/how-to-midi-audio-on-fedora-with-fluidsynth/103401 > > It tells me that the command "fluidsynth -is" is used to verify if it > is up and runing. > This command returns: > Copyright (C) 2000-2024 Peter Hanappe and others. > Distributed under the LGPL license. > SoundFont(R) is a registered trademark of Creative Technology Ltd. > > fluidsynth: error: Failed to bind server socket: 98 > Failed to create the server. > Continuing without it. > fluidsynth: warning: Failed to set thread to high priority > fluidsynth: warning: Failed to set thread to high priority > > After googling this warning, I found this page: > https://jackaudio.org/faq/linux_rt_config.html > > I created the file audio.conf with this content: > @audio - rtprio 95 > @audio - memlock unlimited > > and added my userid to the (existing) group "audio" > > I'll have to reboot to verify if this helps.
I've just played the same MIDI file with audacious (which has a MIDI plug in) and I see that it accessed /usr/share/sounds/sf2/FluidR3_GS.sf2. I've also just played a MIDI file with timidity and I see that it accessed /usr/share/sounds/sf2/FluidR3_GM.sf2. Both methods also access the file /usr/share/fluidr3mono-gm-soundfont/FluidR3Mono_GM.sf3, but only one via the symlink pointing to it, /usr/share/sounds/sf3/FluidR3Mono_GM.sf3. AFAICT, these files stick around in memory, as stat doesn't show them being reaccessed on subsequent playings by either method. OTOH, /usr/bin/fluidsynth was last accessed in Dec 2023. It looks as though its principal use is to play sounds from a MIDI device, of which I have none. When the system (Debian) is idle, neither timidity nor fluidsynth is running. I vaguely recall some people in the past having problems with running timidity themselves, and the fix was killing their timidity daemon. I've never encountered that problem, never having seen such a daemon. I don't remember reports of what might have started it. Cheers, David.
