On Sat, August 26, 2017 16:20, Ralf Mardorf wrote:
On Sat, 26 Aug 2017 10:33:42 +0000, John Rigg wrote:
On 08/25/17 10:10, Ralf Mardorf wrote:
Repeating my own comments, I don't experience
this issue with jack
2
Possibly OT, but I have experienced similar behaviour with jack2.
Hi, i'm sure i missed a lot of this discussion but i wondered if there can
be a single jack client c file that can trigger the issue. Such a client
will allow the specialists to accurately trace the problem with their
tools. I'm sure this will get (more) attention, and if the issue is
understood the chances it gets fixed are good.
Best regards
Tom