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

Le 9 oct. 2014 à 13:49, Paul Davis <[hidden]> a écrit :

> 
> 
> 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?

No, I'm not saying that… just saying the client is "deactivated"...

> 
> i thought jack2 delivered all non-process callbacks in a separate thread?
>  
Yep…

So maybe we should go back to the initial question; what is the client supposed to do when the process callback does not return 0?

Stéphane 

1412858298.21941_0.ltw:2, <CEF34400-F7C9-4367-B9FC-97AF76021E89 at grame dot fr>