Hi Joel et al.,
On 03/08/2012 09:25 PM, Joel Roth wrote:
I think what Paul suggested there is more related to the client create
time (which might also be an issue also with jack1), but my timing
problem does not depend on the client creation, actually it takes about
the same time if I load ardour sessions with many connected ports, or if
I create my own application and connect ports; it is the jack2 library
which takes so long. What I did not try is to connect many ports in
parallel (e.g., create 100 threads, let each of them make a port
connection, and wait until all of them finished). But I will try...
Actually I did not want to complain about jack :-) I know that jack2
needs the time (or at least parts of it) to create a glitch-free
connection while jack1 does not care about glitches. Just that the jack2
behaviour may explain some problems, observed also by others, especially
with large ardour sessions.
Linux-audio-user mailing list