is it possible to have multiple jack audio outputs (one per channel)?
- The multiple jack outputs in QSynth/Setup/Audio tab is a (kind of) esoteric fluidsynth option. The original design refers to having separate jack outputs for the dry signal and for the effects (reverb and chorus). As far as I can tell, it is not about separating audio outputs per MIDI channel (instrument) basis. That's a sensible feature that I'll beg you to ask on the fluidsynthfora, that is, to the libfludisynth upstream development.
is it possible to save qsynth configuration ?
Qsynth configuration is indeed saved and recalled as is on a single file (~/.config/rncbc.org/Qsynth.conf). What you are asking, I think, is having the possibility for this single configuration be eventually regarded as a named profile that you can store and manage at will. This is a very good question and, by chance, it can be answered soon. Positively that is. For that matter, it is on my (still procrastinated) plan to get LASH support into Qsynth and that should bring this request to the foreground, as sure as you can be ;) All I want is to get the grips with the new LASH API generation, which seems pretty awesome on all aspects, programmatically inclusive :) So, there's hope after all.
is it possible to have multiple jack audio outputs (one per channel)?
- The multiple jack outputs in QSynth/Setup/Audio tab is a (kind of) esoteric fluidsynth option. The original design refers to having separate jack outputs for the dry signal and for the effects (reverb and chorus). As far as I can tell, it is not about separating audio outputs per MIDI channel (instrument) basis. That's a sensible feature that I'll beg you to ask on the fluidsynth fora, that is, to the libfludisynth upstream development.
is it possible to save qsynth configuration ?
Qsynth configuration is indeed saved and recalled as is on a single file (~/.config/rncbc.org/Qsynth.conf). What you are asking, I think, is having the possibility for this single configuration be eventually regarded as a named profile that you can store and manage at will. This is a very good question and, by chance, it can be answered soon. Positively that is. For that matter, it is on my (still procrastinated) plan to get LASH support into Qsynth and that should bring this request to the foreground, as sure as you can be ;) All I want is to get the grips with the new LASH API generation, which seems pretty awesome on all aspects, programmatically inclusive :) So, there's hope after all.
Cheers