Add new comment

I guess you're doing it right however it might be that calf-fluidsynth doesn't cope with expectations :)

In general, a so called multi-timbral instrument plugin should be inserted on a MIDI output bus, so that each soundfont preset (aka. program) goes mapped to a separate MIDI channel address (1 to 16) -- you probably have to customize that channel map on the calf-fluidsynth GUI anyway -- then each MIDI track applies to one of th MIDI channels, so it conveys MIDI data (notes and stuff:)) to the designated instrument preset or program in particular. Note that the soundfont (.sf2) has to be designed for multiple presets or bank/programs otherwise this whole multi-timbral idea is completely moot.

MIDI track volume should work as intended as it sends MIDI CC#7 (GM 7-Volume) through the track's MIDI channel so it should affect the SF2 preset assigned to that same channel. OTOH, the MIDI output bus volume fader might not work at all, as it sends GM Master Volume (a GM standard sysex sequence) that calf-fluidsynth plugin might not recognize nor implement as such, at all. As a matter of fact, Ii don't think qsynth or fluidsynth standalone does it either, so you're not doing anything wrong there.

On your second question, re. the View > Instruments function, it's all about to select the SF2 instrument preset (via MIDI bank_select+program_change messages) for the proper MIDI track and channel. Again, I don't really know whether calf-fluidsynth plugin complies with this MIDI program selection scenario, maybe because it's not quite applicable to LV2 plugins (unless the unofficial lv2_programs extension is supported, which I doubt), but is instead designed for external standalone and outboard MIDI instruments (and full-blown SF2 compliant players, eg. qsynth, fluidsynth, etc.);

cheers