Thanks, Marcus! That works if I start FluidSynth manually in a terminal and leave it there, but I'd like to get it to start every time the system reboots. I have put the command in the Startup Applications (which I think is just a GUI for systemd) but Frescobaldi says that no output was found.
How would you start FluidSynth at startup automatically? --- Knute Snortum (via Gmail) On Wed, Aug 5, 2020 at 11:59 AM Marcus Weseloh <mar...@weseloh.cc> wrote: > > Hi Knute, > > as you want FluidSynth to respond to MIDI events, you don't need to > start a server but simply specify which audio/midi driver to use. The > "server" that can be started with the -s command-line option is a way > to access the FluidSynth command shell and not required for your > use-case. > > I've never used frescobali, but looking at the docs at > https://www.frescobaldi.org/uguide#help_preferences_midi it seems like > it only supports ALSA MIDI. And assuming you are on a modern distro, > your sound system is probably based on pulseaudio. So you could start > FluidSynth with the following command-line: > > fluidsynth -a pulseaudio -m alsa_seq /usr/share/sounds/sf2/FluidR3_GM.sf2 > > (Alternatively, if you have a pure ALSA based system, replace -a > pulseaudio with -a alsa). > Then start frescobaldi and open the MIDI settings. You should be able > to choose the FluidSynth MIDI ports as output. > > For further details, you could have a look at the manual: > https://github.com/FluidSynth/fluidsynth/wiki/ExampleCommandLines#fluidsynth-with-pulseaudio > > Cheers > Marcus > > _______________________________________________ > fluid-dev mailing list > fluid-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/fluid-dev _______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
