The proper solution is to use the soundfont loader API, as pointed out by jjc:
http://www.fluidsynth.org/api/sfont_8h.html
That way you are in full control of what preset, instruments... are contained
in your "virtual soundfont" and how they trigger a noteon. For a usage example,
see SWAMI:
ht
(),
fluid_synth_sfunload(), fluid_synth_sfreload() should be convenient.
Using a very small file should not produce a boring latency.
Regards.
jjc
> Message du 19/09/18 14:46
> De : "Davy Triponney"
> A : fluid-dev@nongnu.org
> Copie à :
> Objet : [fluid-dev]
Dear FluidSynth team,
I should have done this from the beginning but I'm now considering
integrating FluidSynth directly inside Polyphone, which will assure a
correct and complete rendering of the soundfonts. I have always considered
FluidSynth as the reference for playing a soundfont.
Loading a