Re: [Jack-Devel] njconnect

PrevNext  Index
DateTue, 08 Jan 2013 18:34:07 +0100
From Pawel / Xj <[hidden] at wp dot pl>
Tojack-devel <[hidden] at lists dot jackaudio dot org>
In-Reply-Torev8 [Jack-Devel] njconnect
Hi,

All reported issues are now fixed in 1.1 release (excluding Jack1 graph callback which is beyond me).

* GUI fixes (scrolling list)
* Note about jslist.h in README (thanks for report from Clever Pereira)
* Expand port name to 128 (onace again thanks to Peter Nelson for report)
* Fix 4 getting connections (thanks for report and suggestion from Peter Nelson)

Pawel

Dnia 6-01-2013 o godz. 21:11 rev8 napisa³(a):
> Hello all,
> 
> Thanks a lot for all reports. You got me - I only tested it in Jack2, 
> but will try Jack1 later.
> Getting connections bug is just stupid typo, but this didn't defend me ;-)
> 
> About requirement of "process" callback, I leave things as-is and wait 
> for Jack1 devs (Paul ?) for state is bug or not, but IMHO it is.
> 
> Port/Connections lists should be also refreshed after 
> connection/disconnection and you can always manually hit "r".
> 
> Pawel
> 
> Dnia 6-01-2013 o godz. 19:04 Peter Nelson napisa³(a):
> > 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
> > > 
> > 
> > 
> > Jack-Devel mailing list
> > [hidden]
> > http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
> 
> 
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
PrevNext  Index

1357666457.12906_0.ltw:2,a <50ec588fb48d88.10385942 at wp dot pl>