[ANN] QjackCtl 0.3.5 slipped away!

View: New views
5 Messages — Rating Filter:   Alert me  

[ANN] QjackCtl 0.3.5 slipped away!

by Rui Nuno Capela :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

A classic needs no introduction.

  QjackCtl 0.3.5 slipped away!

Website:

  http://qjackctl.sourceforge.net

Project page:

  http://sourceforge.net/projects/qjackctl

Downloads:

- source tarball:
  http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.5.tar.gz

- source package (openSUSE 11.1):

http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.5-1.rncbc.suse111.src.rpm

- binary packages (openSUSE 11.1):

http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.5-1.rncbc.suse111.i586.rpm

http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.5-1.rncbc.suse111.x86_64.rpm

- binary packages (Ubuntu 8.04 LTS):

http://downloads.sourceforge.net/qjackctl/qjackctl_0.3.5-1.rncbc.ubuntu804_i386.deb

http://downloads.sourceforge.net/qjackctl/qjackctl_0.3.5-1.rncbc.ubuntu804_amd64.deb

- binary packages (Ubuntu 9.04):

http://downloads.sourceforge.net/qjackctl/qjackctl_0.3.5-1.rncbc.ubuntu904_i386.deb

http://downloads.sourceforge.net/qjackctl/qjackctl_0.3.5-1.rncbc.ubuntu904_amd64.deb

Weblog (upstream support):

  http://www.rncbc.org

License:

  QjackCtl is free, open-source software, distributed under the terms of
the GNU General Public License (GPL) version 2 or later.

Change-log:

- Late support for UTF-8 encoded client/port names.

- Allow only one single patchbay connection to or from an exclusive
socket (mitigating bug #2859119).

- Automatic crash-dump reports, debugger stack-traces (gdb),
back-traces, whatever, are being introduced as a brand new configure
option (--enable-stacktrace) and default enabled on debug build targets
(--enable-debug).

- Probable fix on the audio connections with regard to client/port
(re)name changes (an ancient bug reported by Fons Adriaensen).

- Portaudio device selector is now available (after a patch handed by
Torben Hohn and Stephane Letz).

- A couple of primitive D-Bus interface slots have been introduced,
giving the option to start/stop the jackd server from the system bus eg.
via dbus-send --system / org.rncbc.qjackctl.start (.stop), (a nice
addition supplied by Robin Gareus, thanks).

- New command line option (-a, --active-patchbay=[path]) to specify and
activate a given patchbay definition file (a simple patch sent by John
Schneiderman, thanks).

- Added one significant digit to DSP Load percentage status display.

- Tentative support for netjack (slave) by adding the "net" driver to
the existing backend driver options on the Setup/Settings section.

- Converted obsolete QMessageBox forms to standard buttons.

- New patchbay snapshot now raises the dirty flag and allows for the
immediate salvage of patchbay definition profile.

- Conditional build for JACK port aliases support (JACK >= 0.109.2).

- Alternate icon sizes other than default 16x16, are now effective to
the Connections widget (Setup/Dislay/Connections Window/Icon size).


Enjoy,
--
rncbc aka Rui Nuno Capela
rncbc at rncbc dot org
http://www.rncbc.org

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Re: [ANN] QjackCtl 0.3.5 slipped away!

by torbenh :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Sep 30, 2009 at 07:57:00PM +0100, Rui Nuno Capela wrote:
> - Tentative support for netjack (slave) by adding the "net" driver to
> the existing backend driver options on the Setup/Settings section.

hi rui...

this is not really working.

a) the rate and period size are preferably autodetected and should be
   greyed. they are only useful for the no autodetect feature.

b) on jack2 -d net means netjack2 which doesnt even accept -r and -p

c) hopefully netone will get included into jack2 soon, so it makes a bit
   of sense to consider checking jack version, and provide the right
   options. (or just add netone or whatever)

d) it would be cool, if -c<compress_period_to_n_bytes> would be
   supported. (there are some more options, but -c would be really cool,
   for the others the defaults are ok)

e) netjack1 is a bit wary about clients connecting too early. dont have
   jack1 installed currently... is the connection from qjackctl
   uncritical ?


--
torben Hohn
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Re: [ANN] QjackCtl 0.3.5 slipped away!

by Rui Nuno Capela :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

hi torben

On Mon, 26 Oct 2009 23:24:43 +0100, torbenh@... wrote:
> On Wed, Sep 30, 2009 at 07:57:00PM +0100, Rui Nuno Capela wrote:
>> - Tentative support for netjack (slave) by adding the "net" driver to
>> the existing backend driver options on the Setup/Settings section.
>
> hi rui...
>
> this is not really working.
>

well, i guess you know best ;)


> a) the rate and period size are preferably autodetected and should be
>    greyed. they are only useful for the no autodetect feature.
>
> b) on jack2 -d net means netjack2 which doesnt even accept -r and -p
>

ok. sample-rate and frames per buffer settings will be disbled on net*
driver backends, no matter which version of jackd you're about to run. btw,
qjackctl does not check whether you're about to start jack1 or jack2 so all
server settings are all of the "common denominator" kind.


> c) hopefully netone will get included into jack2 soon, so it makes a bit
>    of sense to consider checking jack version, and provide the right
>    options. (or just add netone or whatever)
>

ok. new "netone" driver/backend option coming up.


> d) it would be cool, if -c<compress_period_to_n_bytes> would be
>    supported. (there are some more options, but -c would be really cool,
>    for the others the defaults are ok)
>

atm. the setup/settings page is already pretty bloated. adding another
option is not that welcome, unless that option is critical to proper
function. is it?


> e) netjack1 is a bit wary about clients connecting too early. dont have
>    jack1 installed currently... is the connection from qjackctl
>    uncritical ?

afaics, qjackctl support for netjack only deals with -dnet client slaves,
not master. at least last time i've checked ;) or am i missing something?


the above said changes will get easily committed to svn later today
(qjackctl 0.3.5.4+).


cheers
--
rncbc aka Rui Nuno Capela
rncbc@...
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Re: [ANN] QjackCtl 0.3.5 slipped away!

by torbenh :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Tue, Oct 27, 2009 at 08:38:51AM +0000, Rui Nuno Capela wrote:

> hi torben
>
> On Mon, 26 Oct 2009 23:24:43 +0100, torbenh@... wrote:
> > On Wed, Sep 30, 2009 at 07:57:00PM +0100, Rui Nuno Capela wrote:
> >> - Tentative support for netjack (slave) by adding the "net" driver to
> >> the existing backend driver options on the Setup/Settings section.
> >
> > hi rui...
> >
> > this is not really working.
> >
>
> well, i guess you know best ;)

i hope so :)

>
>
> > a) the rate and period size are preferably autodetected and should be
> >    greyed. they are only useful for the no autodetect feature.
> >
> > b) on jack2 -d net means netjack2 which doesnt even accept -r and -p
> >
>
> ok. sample-rate and frames per buffer settings will be disbled on net*
> driver backends, no matter which version of jackd you're about to run. btw,
> qjackctl does not check whether you're about to start jack1 or jack2 so all
> server settings are all of the "common denominator" kind.

fine with me.
>
>
> > c) hopefully netone will get included into jack2 soon, so it makes a bit
> >    of sense to consider checking jack version, and provide the right
> >    options. (or just add netone or whatever)
> >
>
> ok. new "netone" driver/backend option coming up.

perfect.

>
>
> > d) it would be cool, if -c<compress_period_to_n_bytes> would be
> >    supported. (there are some more options, but -c would be really cool,
> >    for the others the defaults are ok)
> >
>
> atm. the setup/settings page is already pretty bloated. adding another
> option is not that welcome, unless that option is critical to proper
> function. is it?

when using a celt compressed link (WAN operation) its necessary to
provide the -c parameter on both ends. and it must match.
so unless qjackctl is able to set this in any way, its useless for
setting up a WAN link.


>
>
> > e) netjack1 is a bit wary about clients connecting too early. dont have
> >    jack1 installed currently... is the connection from qjackctl
> >    uncritical ?
>
> afaics, qjackctl support for netjack only deals with -dnet client slaves,
> not master. at least last time i've checked ;) or am i missing something?

i am talking about the slave here.
the problem i am talking about is, that on jack1 netjack will stop
during driver_init and wait for a packet from the master, in order to
autodetect connection parameters.
during this phase jackd is already up and accepting clients, but due to
driver not running jack is in an undefined state.
i know that this does not work for real clients (with process_cb)

maybe we are lucky and it works for qjackctl.
i am going to test this soon.

this problem does not exist for netone on jack2.
which is the better implementation anyways.
and should be preferred.


>
>
> the above said changes will get easily committed to svn later today
> (qjackctl 0.3.5.4+).
>
>
> cheers

cheers to you :)

> --
> rncbc aka Rui Nuno Capela
> rncbc@...

--
torben Hohn
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Re: [ANN] QjackCtl 0.3.5 slipped away!

by torbenh :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Tue, Oct 27, 2009 at 10:03:13AM +0100, torbenh@... wrote:

> >
> >
> > > e) netjack1 is a bit wary about clients connecting too early. dont have
> > >    jack1 installed currently... is the connection from qjackctl
> > >    uncritical ?
> >
> > afaics, qjackctl support for netjack only deals with -dnet client slaves,
> > not master. at least last time i've checked ;) or am i missing something?
>
> i am talking about the slave here.
> the problem i am talking about is, that on jack1 netjack will stop
> during driver_init and wait for a packet from the master, in order to
> autodetect connection parameters.
> during this phase jackd is already up and accepting clients, but due to
> driver not running jack is in an undefined state.
> i know that this does not work for real clients (with process_cb)
>
> maybe we are lucky and it works for qjackctl.
> i am going to test this soon.

ok... it seems to work fine. good job :)

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org