Hi Ben,
>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: 1) Assuming one want to set MIDI channel x in monophonic mode. The simpler way to get this is to send a CC legato(68) On(127) to this channel: >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). To display current channel's legato mode: >legatomode To display current channel x's legato mode: >legatomode x To set legato mode 0 for channel x: >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 > Message du 26/09/18 09:41 > De : "Ben Gonzales" > A : fluid-dev@nongnu.org > Copie à : > 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 > set audio.realtime-prio 99 > > set midi.realtime-prio 99 > so I assume you set those numbers via the command-line now. > And your limits.conf sets a maximum realtime-prio of 95 for the audio group: > @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-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev > _______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
