please note that qsynth is currently a singleton application, which means there can only be one instance running, with one single global configuration (state) at any given one time; this only makes it ugly unsuitable for being a first class jack session participant. you can use ladish or probably a jack session wrapper (eg. js_wrap) for the rescue.
one other reason is that qsynth is not a native jack client per se. it is (lib)fluidsynth instead that deals with jack, when and only when you set one of qsynth's engines audio driver to it, among other possible options (eg. alsa, oss, etc.). yes you can have several engines not necessarily all on top of jack, remember? nb. when setup like so, each qsynth engine determines an independent jack client.
re: jack_session ?
yes there are plans, very long term though :)
please note that qsynth is currently a singleton application, which means there can only be one instance running, with one single global configuration (state) at any given one time; this only makes it ugly unsuitable for being a first class jack session participant. you can use ladish or probably a jack session wrapper (eg. js_wrap) for the rescue.
one other reason is that qsynth is not a native jack client per se. it is (lib)fluidsynth instead that deals with jack, when and only when you set one of qsynth's engines audio driver to it, among other possible options (eg. alsa, oss, etc.). yes you can have several engines not necessarily all on top of jack, remember? nb. when setup like so, each qsynth engine determines an independent jack client.
cheers
ok, fair enough thanks for
ok, fair enough
thanks for the feedback !
grtz
Thijs
Add new comment