Re: [qsynth-devel] Best way to manage presets?
A fluidsynth Qt GUI Interface
Brought to you by:
rncbc
|
From: Lorenzo S. <lor...@gm...> - 2022-09-10 11:18:01
|
Thanks both for the quick answers :-) On 10/09/2022 13:08, ped...@gm... wrote: > On s?bado, 10 de septiembre de 2022 12:50:50 (CEST) Rui Nuno Capela via > qsynth-devel wrote: >>> My idea would be to have a number of engines each with an assigned >>> soundfont an settings, e.g. Engine 1 = Soundfont 1, Engine 2 = >>> soundfont >>> 2, etc. and be able to 'snapshot' and re-load them. Would this be >>> possible in some way? >> >> if more than one sf2 is loaded, you may have a bank offset on the 2nd >> sf2 and 3rd. etc. so their instrument presets be addressable by the >> original bank no. plus respective offset. OK thanks, now it's clearer. Can a MIDI client (e.g. sequencer), change the preset instrument e.g. on a channel? In that case an idea would be to set-up a preset which has 'placeholder' instruments from sf1 on channels 1-16, from sf2 on channels 17-32, etc. > > The soundfont offset is relevant when more than one soundfont is loaded > within the same engine (fluidsynth instance). But Lorenzo's use case is > about loading different soundfonts in different engines/instances, so no > need to set offsets in this case. yes, that's what I was thinking of. Also because there are some soundfonts which are constructed as 1 instrument per soundfont (e.g. a drum soundfont) and it can be useful to have them on a separate engine and control certain parameters independently (poliphony, reverb, ...). The added value is also that each engine gets its midi input. > > The channel presets are stored in the program configuration, ( which in > Linux is located at ~/.config/rncbc.org/Qsynth.conf ). Each preset is > associated to its engine, so I see no problems with Lorenzo's scenario. So currently I could achieve this by setting up and configuring the needed engines and then making a copy of Qsynth.conf for potential later re-use. Not integrated but could e.g. be scripted. At the moment it seems this cpnfig file is hard-coded right (that's what the man page seems to suggest)? Lorenzo. |