7 Jul
2011
7 Jul
'11
12:23 a.m.
On 07/07/2011 12:10 AM, Rui Nuno Capela wrote:
On 07/06/2011 10:09 PM, rosea grammostola wrote:
and the JACK connections. I can imagine that if Qsynth or app X has its
place between other JACK apps (which have JackSession support) in a
session, it would be quite cumbersome for making the JACK connections,
if that app X hasn't JackSession support (you could use it as infra
client maybe).
adding full
On 07/06/2011 11:06 PM, fred wrote:
nope. qsynth has no jack-session support atm.
theres a couple of reasons that sets it back in that regard: qsynth
state is stored on a global user configuration file that doesn't depend
nor change across sessions whatsoever. the other reason is that qsynth
is a singleton. you can only have one instance running at anyone given
time. starting a second instance just activates the first one. been like
that for ages now, way before jack-session was ever the talk of the town ;)
anyway, imo, the only advantage i can see to qsynth participate on a
jack-session would be its automatic launch on session load. Oups !
I probably have to say sorry for the noise, cause Specimen is not from
svn here, and Qsynth is
not in the list at
http://trac.jackaudio.org/wiki/WalkThrough/User/jack_session
Qsynth not in the list?
jack-session support to qsynth is planned, way back on
the backlog
though :)
cheers