Re: [Jack-Devel] njconnect

It is already activated. I added a dummy process handler and now the
graph order callback is handled.

However, there is now another issue:

In jack 1, jack_port_get_connections() can only be used for the client's
own ports.

        Parameters:
        	port	locally owned jack_port_t pointer.

Documentation for jack_port_get_all_connections() states:

        This differs from jack_port_get_connections() in two important
        respects:

        2) You need not be the owner of the port to get information
        about its connections.

So the method of getting all port connections is wrong, sadly.

-- 
Peter Nelson <[hidden]>

> Jack1 has one thread on client side that does RT audio and event handling (notification received form the server). This thread is started when the client calls jack_activate.
> 
> So probably calling jack_activate should be enough?
> 
> Stéphane
> 
> Le 6 janv. 2013 à 18:21, Peter Nelson a écrit :
> 
> > 0.122.0.
> > 
> > This is tested in jackd/engine.c:3215 in git head, assuming I'm followed
> > the code path correctly.
> > -- 
> > Peter Nelson <[hidden]>
> > 
> > On Sun, 2013-01-06 at 18:24 +0200, Nedko Arnaudov wrote:
> >> Peter Nelson <[hidden]> writes:
> >> 
> >>>     2. Jack 1 doesn't call the graph order handler because the client
> >>>        does not have a process handler, so no connections are shown.
> >> 
> >> What version of jack you are using?
> >> 
> > 
> > 
> > Jack-Devel mailing list
> > [hidden]
> > http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
> 

1357495508.24503_0.ltw:2,Sa <1357495476.10835.7.camel at atropos dot lan dot fuzzle dot org>