17 Feb
2015
17 Feb
'15
9:45 a.m.
On Tue, 17 Feb 2015 09:27:00 +0100, IOhannes m zmoelnig wrote:
On 2015-02-09 20:52, Fons Adriaensen wrote:
"it is possible for JACK clients (such as Ardour, but including many
other applications) to ask the JACK server to change its latency
settings "on the fly". The JACK->Latency menu in Ardour is one way to
do this" - https://community.ardour.org/node/3191
When using qjackctl you not only need to close a window, you need to
stop jackd and restart it, to change the latency.
It doesn't matter for an app like Qtractor, since the latency
compensation for audio tracks anyway won't get adjusted to the new
latency.
Using different audio applications the behaviour isn't consistent. IOW
the Linux approach to use several apps instead a one-in-all app doesn't
always work for Linux audio.
There is still (and always has been) a lot modal
behavior in
qjackctl - like being unable to do some things unless you first
close another window. It would be a good thing (TM) to get rid of
all of that.
do you have a (probably incomplete) list of "all that"?
it might help getting rid of it.