Re: [Jack-Devel] port disconnection callbacks (JackPortConnectCallback)

PrevNext  Index
DateThu, 09 Oct 2014 07:49:51 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToMatt Flax <[hidden] at flatmax dot org>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToMatt Flax Re: [Jack-Devel] port disconnection callbacks (JackPortConnectCallback)
Follow-UpStéphane Letz Re: [Jack-Devel] port disconnection callbacks (JackPortConnectCallback)
On Thu, Oct 9, 2014 at 2:55 AM, Matt Flax <[hidden]> wrote:


> I understand what you are saying - the grey zone !
> Something is disconnecting the ports. How would any object which is
> monitoring ports, such as qjackctl or JackPortMonitor know that the
> connection status has changed ?
> Is there an alternative way to get notifications when  ports are
> disconnected ?
>

they don't use a process callback.

stephane, this behaviour seems clearly wrong to me. given that a client
without a process callback can receive the connect/disconnect callbacks, it
doesn't seem right that a client which has just returned non-zero from its
process callback would simply stop receiving them. does that seem right to
you?

i thought jack2 delivered all non-process callbacks in a separate thread?
PrevNext  Index

1412855479.18993_0.ltw:2, <CAFa_cKmyFtQ=Mpy3CURS=p_TL=66x3HpaG0BGg_JFWBcxdPc1A at mail dot gmail dot com>