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 us
fluidsynth: error:
Failed to open the "default" audio device
Aug 07 08:19:27 knute-NUC7PJYH fluidsynth[1810]: Failed to create the
audio driver
Any ideas why ALSA is trying to connect to PulseAudio? Is there some
other way for me to start FluidSynth at boot time?
---
Knute Snortum
(via G
ailed
with result 'exit-code'.
Any ideas why the PulseAudio connection fails?
---
Knute Snortum
(via Gmail)
---
Knute Snortum
(via Gmail)
On Wed, Aug 5, 2020 at 2:41 PM Ceresa Jean-Jacques
wrote:
>
> Hi,
>
>
>
> >How would you start FluidSynth at startup automa
found.
How would you start FluidSynth at startup automatically?
---
Knute Snortum
(via Gmail)
On Wed, Aug 5, 2020 at 11:59 AM Marcus Weseloh wrote:
>
> Hi Knute,
>
> as you want FluidSynth to respond to MIDI events, you don't need to
> start a server but simply specify which audi
trying to bind to socket 98, but according to
/etc/protocols, that socket is in use by another app. Is there a way
to change sockets or will that just confuse frescobaldi?
I'm on Ubuntu 20.04, using the fluidsynth version that apt gets.
---
Knut
