Re: [LAD] Linux-audio-dev Digest, Vol 51, Issue 5 - Linux-audio-dev

5 May 2011

...

 Message: 14
 Date: Wed, 4 May 2011 15:10:55 +0000
 From: Fons Adriaensen &lt;fons(a)linuxaudio.org&gt;
 Subject: Re: [LAD] Looping audio to oneself via Jack
 To: linux-audio-dev(a)lists.linuxaudio.org
 Message-ID: &lt;20110504151055.GE10034(a)linuxaudio.org&gt;
 Content-Type: text/plain; charset=us-ascii

 On Wed, May 04, 2011 at 04:04:37PM +0100, Rui Nuno Capela wrote:

  2. client3 loopbacks to itself and then it all
applies as "the bug".  
 question is: is it jack's bug? maybe not. the other half/part of the  
 problem still aplies, as it depends on the client3's process code  
 flow--which buffer port is read/written first? ins or outs? and in what  
 order? hmm...  
 If one signal (the looped back one) cas disappears because you
 disconnect _another_ one, I'd call that a bug. 100%.

 Note that fixing this does not imply you can't get your own
 undelayed output anymore. That just depends on the order of
 your computations and jack_port_get_buffer() calls.

 Ciao,

 -- 
 FA

I suggest three things :

- move this discussion on jack-dev list...

- write a test client to show the problem.

- test it with jack1 and jack2 to see what happens.

Stéphane 