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

This is not clear for me if this is suppose to happen…

Le 9 oct. 2014 à 02:53, Matt Flax <[hidden]> a écrit :

> Hi there,
> 
> I have registered a callback for port (dis)connections.
> 
> When my client connects its ports, the JackPortConnectCallback indicates this occurance with the 'connect' variable = 1
> 
> When my client finishes playing, it stops by returning a non-zero number from the audio processing function. If I stop the client in this manner, then my JackPortConnectCallback doesn't get called.
> 
> I can see that the port has been disconnected from the client's inputs and outputs.

What happens in the current jack2 implementation is that the RT thread is stopped, the client is marked "inactive", and this is probably what make the connecting begin inactive also.

> 
> I would expect that when the system disconnects those ports it calls the JackPortConnectCallback with the 'connect' variable = 0
> 
> Is this the expected behavior ?

Since this happens on in library side for now (RT thread is stopped…) there isn't anything in place to "signal" back the sever for what happens.
> 
> Here is the version info :
> jackdmp 1.9.10
> 
> thanks
> Matt

Probably we are in the "grey zone" here which means : something not completely well specified/designed/implemented.

Stéphane

1412830270.15449_0.ltw:2, <A0A6CBE0-88BE-4E98-ABFA-94B1D2BFDF29 at grame dot fr>