7 Jun
2008
7 Jun
'08
12:35 p.m.
Howdy!
I am pleased to announce this new and long due release of QjackCtl, the
Qt GUI for the awesome JACK Audio Connection Kit.
Release highlights are mainly about final JACK-MIDI support for the
"evil" Patchbay, new Messages file logging and the most intriguing
application window instance uniqueness which will make X11 desktop life
easier for everyone (ie. no more duplicates as JACK server gets
auto-started as candy bonus:)
You can grab it from the project source as usual:
http://qjackctl.sourceforge.net
http://sourceforge.net/projects/qjackctl
In case you need an upstream hug, you're free to visit my own forum:
http://www.rncbc.org
The change-log doesn't say much but... here it goes:
- Attempt to load Qt's own translation support and get rid of the ever
warning startup message, unless built in debug mode (transaction by
Guido Scholz, while on qsynth-devel, thanks).
- Messages file logging makes its first long overdue appearance, with
user configurable settings in Setup/Options/Logging.
- Only one application instance is now allowed to be up and running,
with immediate but graceful termination upon startup iif an already
running instance is detected, which will see its main widget shown up
and the server started automatically (Qt/X11 platform only).
- Finally, full JACK MIDI support sneaks into the patchbay; socket types
now differ in Audio, MIDI and ALSA, following the very same nomenclature
as found on the Connections widget tabs.
- Sun driver support (by Jacob Meuser).
- Delay window positioning at startup option is now being disabled, on
the Setup/Misc tab, when Minimize to system tray is enabled.
- Cosmetic fix: Setup/Settings tab, 'Input Device' text label was using
a slightly smaller font than the rest of the application (bug#1872545,
reported by Jouni Rinne).
Cheers && Enjoy
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
7 Jun
7 Jun
2:23 p.m.
On Sat, Jun 07, 2008 at 03:35:05PM +0100, Rui Nuno Capela wrote:
Howdy!
Buona sera !
- Only one application instance is now allowed to be
up and running,
with immediate but graceful termination upon startup iif an already
running instance is detected, which will see its main widget shown up
and the server started automatically (Qt/X11 platform only).
And what if *want* two of them (two sound cards, two jack servers) ??
--
FA
Laboratorio di Acustica ed Elettroacustica
Parma, Italia
Lascia la spina, cogli la rosa.
3:56 p.m.
Fons Adriaensen wrote:
On Sat, Jun 07, 2008 at 03:35:05PM +0100, Rui Nuno
Capela wrote:
i'm afriad qjackctl is, as ever was, only of use for one single server
running at any given time, and that server being named as the "default" one.
how did you, assuming that you have some solution of your own, come to
have several qjackctl instances each one running against its own jackd
server, beyond the default that is?
cyaa
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Howdy!
Buona sera !
- Only one application instance is now allowed to
be up and running,
with immediate but graceful termination upon startup iif an already
running instance is detected, which will see its main widget shown up
and the server started automatically (Qt/X11 platform only).
And what if *want* two of them (two sound cards, two jack servers) ??
6:38 p.m.
On Sat, Jun 07, 2008 at 06:56:15PM +0100, Rui Nuno Capela wrote:
how did you, assuming that you have some solution of
your own, come to have
several qjackctl instances each one running against its own jackd server,
beyond the default that is?
I have no solution - qjackctl doesn't accept a server name option.
But I'd expect an upgrade to solve this problem rather than confirm
it. Would adding the code to accept a server name have been more
difficult than whatever was necessary to make it detect another
instance and quit ?
Ciao,
--
FA
Laboratorio di Acustica ed Elettroacustica
Parma, Italia
Lascia la spina, cogli la rosa.
8:21 p.m.
Fons Adriaensen wrote:
On Sat, Jun 07, 2008 at 06:56:15PM +0100, Rui Nuno
Capela wrote:
i guess the question is not about whether it's been difficult, but more
like it has never been thought out in the first place. qjackctl was
never meant to control more than the "default" server and that's the
bare truth i'm afraid ;)
and now that you ask, i admit this is probably the first time i consider
having multi server support in qjackctl :)
ah, maybe in a near future, when the current legacy design ashes get
buried and a new one raises from the emerging jack control interface,
which is already making strides in the jack2 svn underground, i presume :P
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
how did you, assuming that you have some solution
of your own, come to have
several qjackctl instances each one running against its own jackd server,
beyond the default that is?
I have no solution - qjackctl doesn't accept a server name option.
But I'd expect an upgrade to solve this problem rather than confirm
it. Would adding the code to accept a server name have been more
difficult than whatever was necessary to make it detect another
instance and quit ?
6015
days inactive
6015
days old
linux-audio-user@lists.linuxaudio.org
4 comments
2 participants
participants (2)
-
Fons Adriaensen -
Rui Nuno Capela