Hi, qsynth doesn't seem to be happy. I tried @rsadowskis version from August last year, but also updated to 0.9.12.
20:40:55.637 Qsynth1: Synthesizer engine terminated. 20:40:58.001 Qsynth1: Creating synthesizer engine... 20:40:58.004 Qsynth1: Loading soundfont: "/usr/local/share/generaluser-gs/GeneralUser_GS.sf2" (bank offset 0)... 20:40:58.193 Qsynth1: Loading soundfont: "/home/sebastia/mucke/downloads/_MIDI/arachno/Arachno SoundFont - Version 1.0.sf2" (bank offset 1)... 20:40:58.794 Qsynth1: Creating audio driver (file)... 20:40:58.795 Qsynth1: Failed to create the audio driver (file). Cannot continue without it. fluidsynth: error: Unknown string setting 'midi.sndio.device' fluidsynth: error: Unknown string setting 'audio.jack.id' fluidsynth: error: Unknown integer parameter 'audio.jack.autoconnect' fluidsynth: error: Unknown integer parameter 'audio.jack.multi' also, in the past, the audio driver was "sndio", now fluidsynth only has "file" and "sdl2" available. Sebastian On Saturday, January 20, 2024 17:36 CET, "Sebastian Reitenbach" <sebas...@l00-bugdead-prods.de> wrote: > On Saturday, January 20, 2024 10:37 CET, Rafael Sadowski > <raf...@sizeofvoid.org> wrote: > > > On Thu Jan 18, 2024 at 10:55:59PM +0100, Solène Rapenne wrote: > > > Le mercredi 17 janvier 2024 à 12:01 -0500, Thomas Frohwein a écrit : > > > > Hi, > > > > > > > > Following up on [1], I adjusted the fluidsynth diff to the latest > > > > version 2.3.4. Got interested in this when revisiting simutrans [2] > > > > which looks for fluidsynth>=2.1. I tested fluidsynth with shockolate > > > > and generaluser-gs-soundfont which works as previously. I assume from > > > > looking at the prior discussion that updating fluidsynth would require > > > > updating qsynth (see [3]). > > > > > > > > One (minor?) issue is that the test binaries aren't built and so `make > > > > test` doesn't show any useful results. I looked a little through the > > > > cmake files and couldn't spot the problem, but that could probably be > > > > revisited later...? > > > > > > > > ok to catch up our fluidsynth port? > > > > > > > > > > I don't have much opinion about the diff, but the ports using > > > audio/fluidsynth all build well with it > > > > Double checked. OK to update fluidsynth! > > > > Only stumbled upon this threat right now. I'll see to get qsynth updated as > well. > > Sebastian >
