A sizable issue I'm finding with this implementation of FluidSynth is a general lack of means to control the FluidSettings.
Programs that use FluidSynth, like Qsynth, allow direct access to the FluidSettings on a per-engine basis, at any time.
Here is a proper page on the FluidSynth wiki:
https://www.fluidsynth.org/wiki/settings/
Currently, the implementation only allows setting a small selection of these through fluidEngine, which cannot be altered on the fly.
I wish for an opcode, something like:
fluidSettingNum iEngineNumber, SSetting, kValue (For Integer, Float and Boolean types)
fluidSettingString iEngineNumber, SSetting, SValue (For String types)
A sizable issue I'm finding with this implementation of FluidSynth is a general lack of means to control the FluidSettings.
Programs that use FluidSynth, like Qsynth, allow direct access to the FluidSettings on a per-engine basis, at any time.
Here is a proper page on the FluidSynth wiki:
https://www.fluidsynth.org/wiki/settings/
Currently, the implementation only allows setting a small selection of these through fluidEngine, which cannot be altered on the fly.
I wish for an opcode, something like:
fluidSettingNum iEngineNumber, SSetting, kValue (For Integer, Float and Boolean types)
fluidSettingString iEngineNumber, SSetting, SValue (For String types)