[fluid-dev] Config file warnings

[Ben Gonzales]

Hi All.

I have been running this config file for a while with no problems.

set synth.chorus.active off
set synth.reverb.active off
set audio.periods 2
set audio.period-size 64
set audio.realtime-prio 99
set midi.realtime-prio 99
set synth.sample-rate 44100.000
set synth.cpu-cores 2
set synth.gain 3.0
load /home/pi/synth/tenor_saxophone.sf2
prog 00 000


Now I'm using FS2, and I get these warnings in my log file:

Warning: 'audio.periods' is not a realtime setting, changes won't take
effect.
Warning: 'audio.period-size' is not a realtime setting, changes won't
take effect.
Warning: 'audio.realtime-prio' is not a realtime setting, changes won't
take effect.
Warning: 'midi.realtime-prio' is not a realtime setting, changes won't
take effect.
Warning: 'synth.cpu-cores' is not a realtime setting, changes won't take
effect.
loaded SoundFont has ID 1
fluidsynth: warning: No preset found on channel 9 [bank=128 prog=0]

Do these warnings mean I'm trying to change an already-running
fluidsynth instance?

Ben

[Ceresa Jean-Jacques]

Hi Ben

 

Post by Ben Gonzales
Warning: 'audio.periods' is not a realtime setting, changes won't take
effect..... etc

Some settings are just pointed as "not realtime" to advise the user that once the fluidsynth instance is created, those particulars settings cannot be changed anymore during the life time of this instance.

Note this was already the case with previous FS versions. The only difference that with previous versions, the user was not warned !.That means that in your config used in the past, the expected change about these settings was not taken account and you wasn't aware of this. With previous version, you can easily verify this using the command "setting" after trying to change these settings.

 

So, the only way (imo) to set these "not realtime" settings is to use "-o" options in command line. Even this leads in a very long command, it works.

Note also (imo) that fluidsynth console application cannot be invoked using a command file redirection to the standard input.

 

Post by Ben Gonzales
Do these warnings mean I'm trying to change an already-running fluidsynth instance?

Right. Please read first line above.

 

Have fun with your tenor sax.

regards

jjc.

 

 

 

Post by Ben Gonzales
Message du 25/09/18 11:54
De : "Ben Gonzales"
A : "FluidSynth mailing list"
Objet : [fluid-dev] Config file warnings
Hi All.
I have been running this config file for a while with no problems.
set synth.chorus.active off
set synth.reverb.active off
set audio.periods 2
set audio.period-size 64
set audio.realtime-prio 99
set midi.realtime-prio 99
set synth.sample-rate 44100.000
set synth.cpu-cores 2
set synth.gain 3.0
load /home/pi/synth/tenor_saxophone.sf2
prog 00 000
Warning: 'audio.periods' is not a realtime setting, changes won't take
effect.
Warning: 'audio.period-size' is not a realtime setting, changes won't
take effect.
Warning: 'audio.realtime-prio' is not a realtime setting, changes won't
take effect.
Warning: 'midi.realtime-prio' is not a realtime setting, changes won't
take effect.
Warning: 'synth.cpu-cores' is not a realtime setting, changes won't take
effect.
loaded SoundFont has ID 1
fluidsynth: warning: No preset found on channel 9 [bank=128 prog=0]
Do these warnings mean I'm trying to change an already-running
fluidsynth instance?
Ben
_______________________________________________
fluid-dev mailing list
https://lists.nongnu.org/mailman/listinfo/fluid-dev

[Ben Gonzales]

Thanks JJC

So, my config file was doing very little in the past! That's fixed now,
but I'm getting:

fluidsynth: warning: Failed to set thread to high priority

a few times. If I start FS via sudo then the warnings go away.

The user, pi, is a member of the audio group and the entries in the
/etc/security/limits.d/audio.conf are:

@audio   -  rtprio     95
@audio   -  memlock    unlimited
#@audio   -  nice      -19

What am I missing?

Ben

Post by Ceresa Jean-Jacques
Hi Ben

Post by Ben Gonzales
Warning: 'audio.periods' is not a realtime setting, changes won't take
effect..... etc

Some settings are just pointed as "not realtime" to advise the user
that once the fluidsynth instance is created, those particulars
settings cannot be changed anymore during the life time of this instance.
Note this was already the case with previous FS versions. The only
difference that with previous versions, the user was not warned !.That
means that in your config used in the past, the expected change about
these settings was not taken account and you wasn't aware of this.
With previous version, you can easily verify this using the command
"setting" after trying to change these settings.
So, the only way (imo) to set these "not realtime" settings is to use
"-o" options in command line. Even this leads in a very long command,
it works.
Note also (imo) that fluidsynth console application cannot be invoked
using a command file redirection to the standard input.

Post by Ben Gonzales
Do these warnings mean I'm trying to change an already-running

fluidsynth instance?
Right. Please read first line above.
Have fun with your tenor sax.
regards
jjc.

Post by Ben Gonzales
Message du 25/09/18 11:54
Objet : [fluid-dev] Config file warnings
Hi All.
I have been running this config file for a while with no problems.
set synth.chorus.active off
set synth.reverb.active off
set audio.periods 2
set audio.period-size 64
set audio.realtime-prio 99
set midi.realtime-prio 99
set synth.sample-rate 44100.000
set synth.cpu-cores 2
set synth.gain 3.0
load /home/pi/synth/tenor_saxophone.sf2
prog 00 000
Warning: 'audio.periods' is not a realtime setting, changes

won't take

Post by Ben Gonzales
effect.
Warning: 'audio.period-size' is not a realtime setting, changes

won't

Post by Ben Gonzales
take effect.
Warning: 'audio.realtime-prio' is not a realtime setting,

changes won't

Post by Ben Gonzales
take effect.
Warning: 'midi.realtime-prio' is not a realtime setting, changes

won't

Post by Ben Gonzales
take effect.
Warning: 'synth.cpu-cores' is not a realtime setting, changes

won't take

Post by Ben Gonzales
effect.
loaded SoundFont has ID 1
fluidsynth: warning: No preset found on channel 9 [bank=128 prog=0]
Do these warnings mean I'm trying to change an already-running
fluidsynth instance?
Ben
_______________________________________________
fluid-dev mailing list
https://lists.nongnu.org/mailman/listinfo/fluid-dev

_______________________________________________
fluid-dev mailing list
https://lists.nongnu.org/mailman/listinfo/fluid-dev

[Marcus Weseloh]

Hey Ben,

in your config file you had the following lines

Post by Ben Gonzales
set audio.realtime-prio 99
set midi.realtime-prio 99

so I assume you set those numbers via the command-line now.

Post by Ben Gonzales
@audio - rtprio 95

So you could either set Fluidsynth to a lower prio, or increase the rtprio
limit for the audio group.

Cheers,

Marcus

[Ben Gonzales]

Of course that fixed it. Thanks.

It's amazing how these things fall into the "bleedingly obvious"
category when you look at them the right way.

My next challenge with FS2 is to remember how to make the legato work...

Ben

Post by Marcus Weseloh
Hey Ben,
in your config file you had the following lines

Post by Ben Gonzales
set audio.realtime-prio 99
set midi.realtime-prio 99

so I assume you set those numbers via the command-line now.

Post by Ben Gonzales
@audio   -  rtprio     95

So you could either set Fluidsynth to a lower prio, or increase the
rtprio limit for the audio group.
Cheers,
   Marcus
_______________________________________________
fluid-dev mailing list
https://lists.nongnu.org/mailman/listinfo/fluid-dev

[Ceresa Jean-Jacques]

Hi Ben,

 

Post by Ben Gonzales
My next challenge with FS2 is to remember how to make the legato work...

 

Remembering 2 points: (1) monophonic mode and (2) legato mode should be sufficient:

 

Post by Ben Gonzales
CC x 68 127

Now playing noteOn/noteOff on MIDI Channel X, using an ewi or a MIDI keyboard will play monophonically. It means that if the musician plays legato, channel X reacts legato.

2)A MIDI channel X can react legato in one of 2 possible modes (0 or 1). Mode 1 is the default , in this mode the note following the first one of a legato passage will use the first note's voices of the passage as far the key range (specified by the soundfont designer) allows this. If the key range doesn't allow this , the channel will react (fleetingly)

as if it was in mode 0.

In mode 0, each new note always use new voices (i.e the previous note is released (automatically when playing legato) and the new note starts normally).

 

Post by Ben Gonzales
legatomode

 

Post by Ben Gonzales
legatomode x

 

Post by Ben Gonzales
setlegatomode x 0

 

Details about these legato modes are in /doc/polymono/FluidPolyMono-0004.pdf  chapter 3.6, 4.7. For advised persons reading isn't necessary, blowing in your favorite ewi or playing on a keyboard should be sufficient to hear how this works.

Regards.

jjc

 

 

 

 

 

Post by Ben Gonzales
Message du 26/09/18 09:41
De : "Ben Gonzales"
Objet : Re: [fluid-dev] Config file warnings
Of course that fixed it. Thanks.
It's amazing how these things fall into the "bleedingly obvious" category when you look at them the right way.
My next challenge with FS2 is to remember how to make the legato work...
Ben

On 26/09/18 16:57, Marcus Weseloh wrote:
Hey Ben,
in your config file you had the following lines

Post by Ben Gonzales
set audio.realtime-prio 99

set midi.realtime-prio 99 

so I assume you set those numbers via the command-line now.

Post by Ben Gonzales
@audio   -  rtprio     95 

So you could either set Fluidsynth to a lower prio, or increase the rtprio limit for the audio group.
Cheers,
   Marcus
_______________________________________________
fluid-dev mailing list
fluid-***@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev

[Ben Gonzales]

Thanks, JJC.

That was easy, and it works well! It's good to see your work "in
production".

Ben

Post by Ceresa Jean-Jacques
Hi Ben,

Post by Ben Gonzales
My next challenge with FS2 is to remember how to make the legato work...