<br><div class="gmail_quote">2012/3/8 thijs van severen <span dir="ltr"><<a href="mailto:thijsvanseveren@gmail.com">thijsvanseveren@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div><div class="h5">2012/3/8 Rui Nuno Capela <span dir="ltr"><<a href="mailto:rncbc@rncbc.org" target="_blank">rncbc@rncbc.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 03/07/2012 09:42 PM, Fons Adriaensen wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello all,<br>
<br>
I wonder if I'm the only one experiencing this problem with<br>
Qjackctl. Anyway I haven't seen any other reports of it.<br>
The problem is so obvious that I myself never bothered to<br>
report it - it's the thing you exect fixed in the next<br>
release. But apprently it never gets fixed.<br>
<br>
To the facts now: almost every day when I use it, and for<br>
the last years, Qjackctl get into some cramp in which it<br>
either<br>
<br>
- refuses to make some connections,<br>
- or refuses to show them,<br>
- or makes them and then disconnects them immediately.<br>
<br>
I don't know what triggers this, but it could be related to apps<br>
making lots of ports connections in a short time and Qjackctl's<br>
idea of current connections getting out of sync with reality.<br>
Given Jack's APi for this that is no big surprise, but what really<br>
messes up things is that Qjackctl apparently has no means to recover<br>
and refresh its connections database from scratch. The only option<br>
is to terminate it (which takes Jack and all apps with it, unless<br>
Jack was started separately).<br>
<br>
</blockquote>
<br></div>
i had never seen this kind of trouble, but again i seldom run hundreds of port (dis|re)connections in probably short time<br>
<br>
don't the "connections "refresh" button is of any help here, perhaps? i mean, instead of a proverbial stop/start?<br>
<br>
since last qjackctl released version (>= 0.3.8) the "refresh" button does a complete rebuild of all connection listings instead of using some or any previously cached items which i think is the culprit of potential race conditions, specially if you're disconnecting and/or reconnecting (a lot of) ports with same literal names on so short notice<br>
<br>
byee<span><font color="#888888"><br>
-- </font></span></blockquote><div><br></div></div></div><div>in my case the number of connections is very limited, and the refresh button is not enough, it needs a restart Qjack to update the connections correctly (that is only Qjack, not jackd)</div>
<div>i'll see if i can find a simple way to reproduce </div><div><br></div><div>grtz</div><span class="HOEnZb"><font color="#888888"><div>Thijs</div></font></span></div>
</blockquote></div><br>important remark : i'm running 0.3.7 (havent tested 0.3.8 yet)<br><br>