2 Oct
2014
2 Oct
'14
10:16 p.m.
Hi
you are my last resource.
I'm trying to start fluidsynth in daemon mode (-s) at the startup. At
first I tried to adapt a guide for Arch but I realized that in Debian
(sid) the configuration is different:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760210
I'm using systemd. I've tried several times to write a proper
fluidsynth.service but I always failed.
Here's my last try:
--------------->----------------------------->---------------------------->
[Unit]
Description=FluidSynth Synthesizer
After=syslog.target
Before=sound.target
Requires=dbus.socket
[Service]
Type = forking
ExecStart=/usr/bin/fluidsynth -s -a alsa
/usr/share/sounds/sf2/FluidR3_GM.sf2
Environment=DISPLAY=:0
#Restart=always
#RestartSec=5
[Install]
WantedBy=default.target
#WantedBy=multi-user.target
----------------->-------------------------->----------------------------->
This is the error:
# systemctl status -l fluidsynth.service
● fluidsynth.service - FluidSynth Synthesizer
Loaded: loaded (/etc/systemd/system/fluidsynth.service; disabled)
Active: inactive (dead)
ott 02 19:56:00 fede-xps systemd[1]: Started FluidSynth Synthesizer.
ott 02 20:13:51 fede-xps systemd[1]: Stopped FluidSynth Synthesizer.
ott 02 22:09:05 fede-xps fluidsynth[24181]: fluidsynth: warning:
Requested a period size of 64, got 940 instead
ott 02 22:09:05 fede-xps fluidsynth[24181]: fluidsynth: warning:
Requested 16 periods, got 8 instead
ott 02 22:09:05 fede-xps fluidsynth[24181]: FluidSynth version 1.1.6
ott 02 22:09:05 fede-xps fluidsynth[24181]: Copyright (C) 2000-2012
Peter Hanappe and others.
ott 02 22:09:05 fede-xps fluidsynth[24181]: Distributed under the LGPL
license.
ott 02 22:09:05 fede-xps fluidsynth[24181]: SoundFont(R) is a
registered trademark of E-mu Systems, Inc.
ott 02 22:09:05 fede-xps fluidsynth[24181]: Type 'help' for help topics.
ott 02 22:09:05 fede-xps fluidsynth[24181]: >
The error about the period size can be avoided setting "-z 940", but I
don't understand why this error appears only when fluidsynth is started
as a systemd service and not when I run that command in a terminal. I
guess that it may be related to when the command is launched in systemd
levels. I think that I should play with the values of After, Before and
Requires in the Unit section.
But I hope that someone in this list can help me, I don't have time
currently to study systemd (and it would be probably too complex for
me).
Thank you in advance.
Federico