Thanks Marcus,
I think I will just use the shell script solution you proposed, since
I don't use Frescobaldi all the time. Thanks again for all your help!
---
Knute Snortum
(via Gmail)
On Sun, Aug 9, 2020 at 4:27 AM Marcus Weseloh wrote:
>
> Hi Knute,
>
> as your Ubuntu is using pulseaudio as
Hi Knute,
as your Ubuntu is using pulseaudio as sound server by default, alsa is
configured to use pulseaudio as the output "sink". So if you want to
keep the default system configuration of your ubuntu, then it makes
sense to use the FluidSynths pulseaudio driver as alsa will simply
forward all a
Thanks, Marcus.
I disabled the system config for fluidsynth and enabled the user
config. I took PulseAudio out of the config and just used ALSA.
Status looks good and MIDI plays from Frescobaldi when I start the
process "manually" after boot. But when I reboot, I get no MIDI
output and systemctl
Hi Knute,
you say that you used a user unit file file in .config/systemd/user/,
but the output from the status command is a report from a system unit
file in /lib/systemd/system/fluidsynth.service.
If you want to use user-unit files, you need to prefix all systemctl
commands with --user. So you c
Thanks, Ceresa, I read that whole thread but it doesn't seem to apply
to my situation.
I am on Ubuntu 20.04, using systemd now to try to start FluidSynth. I
learned that PulseAudio won't start as root, so I added my service to
~/.config/systemd/user. It looks like this:
[Unit]
Description=Fluid
Hi,
>How would you start FluidSynth at startup automatically? -
Here possible solution.
https://lists.nongnu.org/archive/html/fluid-dev/2020-01/msg00032.html
jjc
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman
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.
Ho
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
I am trying to get fluidsynth to start a server so that an outside
application (frescobaldi) can send MIDI events to it. Here is what I
get when I try to do this:
$ fluidsynth -is /usr/share/sounds/sf2/FluidR3_GM.sf2
FluidSynth runtime version 2.1.1
Copyright (C) 2000-2020 Peter Hanappe and other
