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 _______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@email-addr-hidden http://lists.linuxaudio.org/listinfo/linux-audio-devReceived on Wed May 4 20:15:05 2011
This archive was generated by hypermail 2.1.8 : Wed May 04 2011 - 20:15:05 EEST