Re: jack MIDI and qjackctl

Hello,

Thanks for the heads up, I now understand what's happening here. It does not matter too much for now. I will
try to latest dev version of qjackctl though.

Cheers!
J.

--- On Sun, 11/2/08, Rui Nuno Capela <rncbc <at> rncbc.org> wrote:

> From: Rui Nuno Capela <rncbc <at> rncbc.org>
> Subject: Re: [Jack-Devel] jack MIDI and qjackctl
> To: warjamy <at> yahoo.com
> Cc: jack-devel <at> lists.jackaudio.org
> Date: Sunday, November 2, 2008, 5:51 AM
> James Warden wrote:
> > Hey,
> > 
> > I just updated jack to svn <at> 3066. It works as good as I
> can expect. I
> > just have a question to the author of qjackctl. When I
> use jackd with
> > -X seq, I enable the jack MIDI capability. I wonder
> why the MIDI tab
> > displays "alsa_pcm" as the port folder name.
> When I start a MIDI
> > client, its name is recognizable (that's a good
> thing from a user's
> > point of view) but it ends up in this
> "alsa_pcm" port folder. This is
> > different from the audio tab : when you start an audio
> client, it has
> > its own port folder. Is this difference intentional ?
> I am using
> > qjackctl 0.3.2.
> > 
> 
> yes, it seems intentional but it's a jack alsa-seq
> backend issue afaics.
> 
> qjackctl just shows what libjack gives it to show, no more
> nor less.
> 
> however, i could swear it was named "system"
> before, instead of
> "alsa_pcm" (which has been the first alias name,
> anyway). there must
> have been changes wrt. jack-midi alsa-seq client/port names
> aliases that
> i've oversought somehow...
> 
> btw, current qjackctl cvs head (0.3.3.11+) let's you
> choose client/ports
> aliases and there you can see the difference (or not:)
> 
> cheers
> -- 
> rncbc aka Rui Nuno Capela
> rncbc <at> rncbc.org