[linux-audio-user] [ANN] QjackCtl 0.2.22 released!

[Nedko Arnaudov]

Lars Luthman <lars.luthman at gmail.com> writes:

> On Sat, 2007-03-31 at 16:15 +0200, Marc-Olivier Barre wrote:
>> On 3/31/07, Petter Sundlöf <petter.sundlof at 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 ?
>
> 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. 

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>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
Url : http://lists.linuxaudio.org/pipermail/linux-audio-user/attachments/20070331/737d4beb/attachment.pgp