31 Mar
2007
31 Mar
'07
11:51 a.m.
Long overdue but better late than never:
QjackCtl, the good old Qt GUI interface to JACK Audio Connection Kit is
back on a new latest dot releasse.
As read from the changelog:
- Fixed default settings for the freebob backend (JACK >= 0.103.0).
- CPU Load status label now says correctly DSP Load.
- The most recently used patchbay definitions can now be correctly
selected in round-robin fashion from its drop-down list widget.
- Avoid mixing JACK MIDI ports with regular audio ports on the
Connections and Patchbay widgets; strictly list only audio ports.
- Added 192k sample rate to setup settings drop down list (as kindly
reminded by Klaus Zimmermann, thanks).
- Most top-level widgets were missing the normal-widget flag, which were
causing some sticky size behavior on some window managers.
Enjoy.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
31 Mar
31 Mar
12:06 p.m.
On Sat, 2007-03-31 at 14:45 +0100, Rui Nuno Capela wrote:
Long overdue but better late than never:
QjackCtl, the good old Qt GUI interface to JACK Audio Connection Kit is
back on a new latest dot releasse.
...
- Avoid mixing JACK MIDI ports with regular audio ports on the
Connections and Patchbay widgets; strictly list only audio ports.
Eh? So it's impossible to connect JACK MIDI ports using QjackCtl 0.2.22?
If so, that makes it rather useless to me.
--ll
12:11 p.m.
Though it's not clear by the wording, I interpreted it as them being in
the MIDI tab.
Lars Luthman wrote:
On Sat, 2007-03-31 at 14:45 +0100, Rui Nuno Capela
wrote:
Long overdue but better late than never:
QjackCtl, the good old Qt GUI interface to JACK Audio Connection Kit is
back on a new latest dot releasse.
...
- Avoid mixing JACK MIDI ports with regular audio ports on the
Connections and Patchbay widgets; strictly list only audio ports.
Eh? So it's impossible to connect JACK MIDI ports using QjackCtl 0.2.22?
If so, that makes it rather useless to me.
--ll 
12:19 p.m.
On 3/31/07, Petter Sundlöf <petter.sundlof(a)gmail.com> wrote:
Though it's not clear by the wording, I
interpreted it as them being in
the MIDI tab.
Lars Luthman wrote:
> On Sat, 2007-03-31 at 14:45 +0100, Rui Nuno Capela wrote:
>> Long overdue but better late than never:
>>
>> QjackCtl, the good old Qt GUI interface to JACK Audio Connection Kit is
>> back on a new latest dot releasse.
>> ...
>> - Avoid mixing JACK MIDI ports with regular audio ports on the
>> Connections and Patchbay widgets; strictly list only audio ports.
>
> Eh? So it's impossible to connect JACK MIDI ports using QjackCtl 0.2.22?
> If so, that makes it rather useless to me.
AFAIR, qjackctl did not know how to connect jack midi ports yet. I
assume Rui only hid the ports wrongly showing up in the audio port
list. That does not imply he added jack midi support. Rui ? still
there ? are jack midi ports supported or only hidden ?
__________________
Marc-Olivier Barre,
Markinoko.
12:30 p.m.
On Sat, 2007-03-31 at 16:15 +0200, Marc-Olivier Barre wrote:
On 3/31/07, Petter Sundlöf
<petter.sundlof(a)gmail.com> wrote:
It did (before 0.2.22). Connecting MIDI ports is identical, API-wise, to
connecting audio ports. Since QJackCtl didn't know about MIDI ports and
didn't check the port type, it had no problems with connecting MIDI
ports.
--ll
Though it's not clear by the wording, I
interpreted it as them being in
the MIDI tab.
Lars Luthman wrote:
> On Sat, 2007-03-31 at 14:45 +0100, Rui Nuno Capela wrote:
>> Long overdue but better late than never:
>>
>> QjackCtl, the good old Qt GUI interface to JACK Audio Connection Kit is
>> back on a new latest dot releasse.
>> ...
>> - Avoid mixing JACK MIDI ports with regular audio ports on the
>> Connections and Patchbay widgets; strictly list only audio ports.
>
> Eh? So it's impossible to connect JACK MIDI ports using QjackCtl 0.2.22?
> If so, that makes it rather useless to me.
AFAIR, qjackctl did not know how to connect jack midi ports yet. I
assume Rui only hid the ports wrongly showing up in the audio port
list. That does not imply he added jack midi support. Rui ? still
there ? are jack midi ports supported or only hidden ? 
2:26 p.m.
Lars Luthman <lars.luthman(a)gmail.com> writes:
On Sat, 2007-03-31 at 16:15 +0200, Marc-Olivier Barre
wrote:
This silly, new qjackctl release disabling jack midi? With versions
before user could at least connect (non intuitive, yes, but useable
workaround). Why the hell should you remove functionality?!? This does
not promote JACK MIDI, it is against it. Do we want 18 months+ for users
to start using JACK MIDI?
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
On 3/31/07, Petter Sundlöf
<petter.sundlof(a)gmail.com> wrote:
It did (before 0.2.22). Connecting MIDI ports is identical, API-wise, to
connecting audio ports. Since QJackCtl didn't know about MIDI ports and
didn't check the port type, it had no problems with connecting MIDI
ports. Though it's not clear by the wording, I
interpreted it as them being in
the MIDI tab.
Lars Luthman wrote:
> On Sat, 2007-03-31 at 14:45 +0100, Rui Nuno Capela wrote:
>> Long overdue but better late than never:
>>
>> QjackCtl, the good old Qt GUI interface to JACK Audio Connection Kit is
>> back on a new latest dot releasse.
>> ...
>> - Avoid mixing JACK MIDI ports with regular audio ports on the
>> Connections and Patchbay widgets; strictly list only audio ports.
>
> Eh? So it's impossible to connect JACK MIDI ports using QjackCtl 0.2.22?
> If so, that makes it rather useless to me.
AFAIR, qjackctl did not know how to connect jack midi ports yet. I
assume Rui only hid the ports wrongly showing up in the audio port
list. That does not imply he added jack midi support. Rui ? still
there ? are jack midi ports supported or only hidden ?
3:16 p.m.
Nedko Arnaudov wrote:
This silly, new qjackctl release disabling jack midi?
With versions
before user could at least connect (non intuitive, yes, but useable
workaround). Why the hell should you remove functionality?!? This does
not promote JACK MIDI, it is against it. Do we want 18 months+ for users
to start using JACK MIDI?
Where did this magic 18+ number come around?
QjackCtl _never_ had any JACK-MIDI functionality built on it. So quite
frankly I did not remove a damn thing. I just fixed an inconsistency, a
bug that was lurking trough sloppy JACK API interpretation and being
there since long before the pre-JACK-MIDI days. In fact, the fix will be
actually needed for going through coming changes which will be done for
JACK-MIDI support in future QjackCtl (BTW that happening will bump
version tagging to 0.3.x, is that's any relevant).
If you're not happy with it, and if you find connecting JACK-MIDI
applications paramount to your daily use, please don't upgrade. Stay
with 0.2.21 or older. Actually, the upgrade is only really recommended
if you're doing the firewire/freebob stance. All else is nitpicking.
OTOH, which JACK MIDI client application is already generally available
and productive? At least for 18 months already? Tell me please. I'd
really like to know.
JACK-MIDI is still under work. Although some infrastructure is already
there, I'm pretty sure it is not quite in general use, let alone promotion.
As I said, the JACK-MIDI functionality will be handled properly in
coming QjackCtl releases, as it should be, like when proper JACK MIDI
backend drivers interface gets in place. Then you can start telling
users the prospect you have some real JACK-MIDI functionality. Then
you'll probably get some real client applications too.
Once again, if you are a developer of some JACK-MIDI client application
you probably know what to do. And you should be prepared to change your
code too, as the JACK-MIDI API is still not frozen still.
Bye now.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
1:15 p.m.
Marc-Olivier Barre wrote:
On 3/31/07, Petter Sundlöf
<petter.sundlof(a)gmail.com> wrote:
Todays 0.2.22 release does not support JACK MIDI ports.
Until 0.2.21, inclusive, JACK MIDI ports were being listed on the Audio
Connections tab but you could only connect the right ones if you know
those are of the correct type, which I believe is counter-intuitive,
inconsistent, or just plain wrong.
As I said, the coming changes to QjackCtl will have this straight, and
there will be three tabs con the connections window: JACK Audio ports,
JACK MIDI ports and ALSA MIDI ports.
But again, that will most probably happen _after_ proper JACK MIDI
backend drivers get real in the JACK source tree.
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Though it's not clear by the wording, I
interpreted it as them being in
the MIDI tab.
Lars Luthman wrote:
0.2.22?
> If so, that makes it rather useless to me.
AFAIR, qjackctl did not know how to connect jack midi ports yet. I
assume Rui only hid the ports wrongly showing up in the audio port
list. That does not imply he added jack midi support. Rui ? still
there ? are jack midi ports supported or only hidden ?
On Sat, 2007-03-31 at 14:45 +0100, Rui Nuno
Capela wrote:
> Long overdue but better late than never:
>
> QjackCtl, the good old Qt GUI interface to JACK Audio Connection
Kit is
back on a
new latest dot releasse.
...
- Avoid mixing JACK MIDI ports with regular audio ports on the
Connections and Patchbay widgets; strictly list only audio ports.
Eh? So it's impossible to connect JACK MIDI ports using QjackCtl
12:19 p.m.
On Sat, 2007-03-31 at 16:11 +0200, Petter Sundlöf wrote:
Lars Luthman wrote:
They are not, I just tried it.
--ll
On Sat, 2007-03-31 at 14:45 +0100, Rui Nuno
Capela wrote:
Though it's not clear by the wording, I interpreted it as them
being the MIDI tab. Long overdue but better late than never:
QjackCtl, the good old Qt GUI interface to JACK Audio Connection Kit is
back on a new latest dot releasse.
...
- Avoid mixing JACK MIDI ports with regular audio ports on the
Connections and Patchbay widgets; strictly list only audio ports.
Eh? So it's impossible to connect JACK MIDI ports using QjackCtl 0.2.22?
If so, that makes it rather useless to me.
12:19 p.m.
Lars Luthman wrote:
On Sat, 2007-03-31 at 14:45 +0100, Rui Nuno Capela
wrote:
That is correct. JACK MIDI support on QjackCtl will be featured only on
future incarnations, following the coming midi driver/backend
stabilization on the jack tree i.e. after Dimitry's ;)
Until then, if you rely on the current broken mess and mixup of MIDI
ports in the Audio connections pane, feel free to avoid and skipping the
upgrade. :)
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Long overdue but better late than never:
QjackCtl, the good old Qt GUI interface to JACK Audio Connection Kit is
back on a new latest dot releasse.
...
- Avoid mixing JACK MIDI ports with regular audio ports on the
Connections and Patchbay widgets; strictly list only audio ports.
Eh? So it's impossible to connect JACK MIDI ports using QjackCtl 0.2.22?
If so, that makes it rather useless to me.
6246
days inactive
6246
days old
linux-audio-user@lists.linuxaudio.org
9 comments
5 participants
participants (5)
-
Lars Luthman -
Marc-Olivier Barre -
Nedko Arnaudov -
Petter Sundlöf -
Rui Nuno Capela