now after startup there are two processes:
fluidsy+ 20 0 625032 16652 13068 S 14,9 0,2 1:56.71 pulseaudio
fluidsy+ 20 0 909016 196852 8440 S 10,2 2,4 1:23.55 fluidsynth
A) The first problem is, that there is an additional pulseaudio spawned
for the fluidsynth user which collides with the user's pulseaudio and
thus sometimes midi works and the other audio doesn't or vice versa
depending who got the audio device.
Should I run fluidsynth for the current user?
Is there any other way to install fluidsynth to the background?
why doesn't it connect to the user's pulsaudio?
B) the next problem is that sometimes (no idea about the likeliness)
after boot-up these two processes consume 100% of a single core each.
manually restarting the service solved it.
find below my config.
ps. did not allow real-time priority that's why there are error messages.