Re: [LAU] [LAD] like "qjackctl", but trimmed of all fat

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-user@...>
Cc: <linux-audio-dev@...>
Subject: Re: [LAU] [LAD] like "qjackctl", but trimmed of all fat
Date: Wednesday, June 9, 2010 - 2:08 am
--0016364c7eaf8b576304888f5f73

Content-Type: text/plain; charset=ISO-8859-1
Hi all,
Let me know how this newer version works out for you. I've hopefully made

the audio/MIDI distinction cleaner and bug-free, b/c now the script uses

'jack_lsp -t' to list the type. One can toggle between alsa-midi and

jack-midi with the 'm' key.
Not being a user of a2jackmidi bridge or whatever that program is, I cannot

vouch for how this works with it...does anyone want to try it out and let me

know?
http://www.akjmusic.com/software/jackctl20100604.py
Best,

AKJ
On Sat, May 29, 2010 at 11:42 AM, Aaron Krister Johnson

wrote:
> On 5/29/10, akjmicro@gmail.com  wrote:

quoted text> > Hey all,

> >

> > Yes, grepping for the port type which appears underneath with a 'jack_lsp

> > -t' will be more consistent and dependable. Or, using a python-jack lib

> > function and not depending on any system shell calls. The problem then

> > becomes, is the jack lib for python well documented? If so, I think

> that's

> > the real future of jackctl.py

> >

> > PS Qjackctl may be lightweight, but installing the entire QT toolkit just

> to

> > use it is not!

> >

> > AKJ

> >

> > Sent from my Verizon Wireless BlackBerry

> >

> > -----Original Message-----

> > From: Robin Gareus

> > Date: Sat, 29 May 2010 14:00:52

> > To: Julien Claassen

> > Cc: Aaron Krister Johnson;

> > ;

> >

> > Subject: Re: [LAD] [LAU] like "qjackctl", but trimmed of all fat

> >

> > Hi Julien, Hey Aaron,

> >

> > read 'jack_lsp --help'.

> >

> > '-t' does not take any arguments; it just makes jack_lsp print the type.

> > the filter-string only acts on the port-name (BTW, not only the

> > beginning of the port-name; but it's case-sensitive: strstr() )

> >

> > Anyway I can reproduce the problem, some jack-midi ports show up in the

> > audio-tab of jackctl20100528b.py.

> >

> > jackctl20100528b checks for lowercase 'midi' in the port-name instead of

> > looking up the port-type. So a2jmidi for example with an upper-case M

> > "Midi.." ends up in the audio-panel.

> >

> > Your suggestion to parse the output of 'jack_lsp -t -c' is spot on.

> > the (currently 2) possible return values are (indented by tab):

> >

> > #define JACK_DEFAULT_AUDIO_TYPE "32 bit float mono audio"

> > #define JACK_DEFAULT_MIDI_TYPE "8 bit raw midi"

> >

> > ..or as you suggest using the python-module for JACK may also simplify

> > things and make jackctl easier to maintain.

> >

> > Cheers!

> > robin

> >

> > PS. Oh, and which of qjackctl's features makes it 'fat'? it's not

> > bloated in any way. I'd rather put it the other way 'round and say that

> > jackctl is 'slim'. Sorry could not resist.

> >

> >

> > On 05/29/2010 12:23 PM, Julien Claassen wrote:

> >> Hello Aaron and Jack-Team!

> >>   There seems to be a bug in my jack_lsp. I just started a2jmidid and

> >> j2amidi_bridge. when I do a jack_lsp I get all the ports.

> >>   When I do: jack_lsp -t midi I only get one port from jack_midi_clock,

> >> but none of the other ones.

> >>   When I type: jack_lsp -t, I can't see a difference between the

> >> jack_midi_clock port and the others:

> >> jack_lsp -t

> >> [...]

> >> a2j:Virtual Raw MIDI 0-0 [16] (capture): VirMIDI 0-0

> >>         8 bit raw midi

> >> a2j:Virtual Raw MIDI 0-0 [16] (playback): VirMIDI 0-0

> >>         8 bit raw midi

> >> a2j:Virtual Raw MIDI 0-1 [17] (capture): VirMIDI 0-1

> >>         8 bit raw midi

> >> a2j:Virtual Raw MIDI 0-1 [17] (playback): VirMIDI 0-1

> >>         8 bit raw midi

> >> a2j:Virtual Raw MIDI 0-2 [18] (capture): VirMIDI 0-2

> >>         8 bit raw midi

> >> a2j:Virtual Raw MIDI 0-2 [18] (playback): VirMIDI 0-2

> >>         8 bit raw midi

> >> a2j:Virtual Raw MIDI 0-3 [19] (capture): VirMIDI 0-3

> >>         8 bit raw midi

> >> a2j:Virtual Raw MIDI 0-3 [19] (playback): VirMIDI 0-3

> >>         8 bit raw midi

> >> a2j:M Audio Delta 1010LT [20] (capture): M Audio Delta 1010LT MIDI

> >>         8 bit raw midi

> >> a2j:M Audio Delta 1010LT [20] (playback): M Audio Delta 1010LT MIDI

> >>         8 bit raw midi

> >> j2a_bridge:playback

> >>         8 bit raw midi

> >> a2j:j2a_bridge [129] (capture): capture

> >>         8 bit raw midi

> >> Jack MIDI Clock:midi_out

> >>         8 bit raw midi

> >>

> >>   Or is the argument "midi" only seen as the start of a port_name?

> >>   If so, Aaron, you must rewrite this part of jackctl (I guess you do

> >> what I described, because I get exactly your output). You should rewrite

> >> it using:

> >> jack_lsp -t

> >>   And then parse the type info underneath each name. I think a simple

> >> grabbing for "audio" or "midi" will do. But I guess, that in the long

> >> run, using the python module for jack, will be more efficient and easy

> >> to use.

> >>   Kindly yours

> >>           Julien

> >>

> >

>

>

> --

>

> Aaron Krister Johnson

> http://www.akjmusic.com

> http://www.untwelve.org

>
--

Best,
Aaron Krister Johnson

http://www.akjmusic.com

http://www.untwelve.org
--0016364c7eaf8b576304888f5f73

Content-Type: text/html; charset=ISO-8859-1

Content-Transfer-Encoding: quoted-printable
Hi all,Let me know how this newer version works out for you. I'=

ve hopefully made the audio/MIDI distinction cleaner and bug-free, b/c now =

the script uses 'jack_lsp -t' to list the type. One can toggle betw=

een alsa-midi and jack-midi with the 'm' key.

Not being a user of a2jackmidi bridge or whatever that program is, I ca=

nnot vouch for how this works with it...does anyone want to try it out and =

let me know?http://www.akjmusic.com/software/jackctl20100604.py

Best,AKJOn Sat, May 29, 2010 at =

11:42 AM, Aaron Krister Johnson <aaron@akjmusic.com> wrote:

On 5/29/10, akjmicr=

o@gmail.com <akjmicro@gmail.co=

m> wrote:

quoted text> Hey all,

>

> Yes, grepping for the port type which appears underneath with a 'j=

ack_lsp

quoted text> -t' will be more consistent and dependable. Or, using a python-jac=

k lib

quoted text> function and not depending on any system shell calls. The problem then=
> becomes, is the jack lib for python well documented? If so, I think th=

at's

quoted text> the real future of jackctl.py

>

> PS Qjackctl may be lightweight, but installing the entire QT toolkit j=

ust to

quoted text> use it is not!

>

> AKJ

>

> Sent from my Verizon Wireless BlackBerry

>

> -----Original Message-----

> From: Robin Gareus <robin@gareu=

s.org>

quoted text> Date: Sat, 29 May 2010 14:00:52

> To: Julien Claassen<julien@c-lab=

.de>

quoted text> Cc: Aaron Krister Johnson<aar=

on@akjmusic.com>;

quoted text> <linux-aud=

io-user@lists.linuxaudio.org>;

quoted text> <linux-audi=

o-dev@lists.linuxaudio.org>

quoted text> Subject: Re: [LAD] [LAU] like "qjackctl", but trimmed of all=

 fat

quoted text>

> Hi Julien, Hey Aaron,

>

> read 'jack_lsp --help'.

>

> '-t' does not take any arguments; it just makes jack_lsp print=

 the type.

quoted text> the filter-string only acts on the port-name (BTW, not only the

> beginning of the port-name; but it's case-sensitive: strstr() )

>

> Anyway I can reproduce the problem, some jack-midi ports show up in th=

e

quoted text> audio-tab of jackctl20100528b.py.

>

> jackctl20100528b checks for lowercase 'midi' in the port-name =

instead of

quoted text> looking up the port-type. So a2jmidi for example with an upper-case M<=

br>

quoted text> "Midi.." ends up in the audio-panel.

>

> Your suggestion to parse the output of 'jack_lsp -t -c' is spo=

t on.

quoted text> the (currently 2) possible return values are (indented by tab):

>

> #define JACK_DEFAULT_AUDIO_TYPE "32 bit float mono audio"

> #define JACK_DEFAULT_MIDI_TYPE "8 bit raw midi"

>

> ..or as you suggest using the python-module for JACK may also simplify=
> things and make jackctl easier to maintain.

quoted text>

> Cheers!

> robin

>

> PS. Oh, and which of qjackctl's features makes it 'fat'? i=

t's not

quoted text> bloated in any way. I'd rather put it the other way 'round and=

 say that

quoted text> jackctl is 'slim'. Sorry could not resist.

>

>

> On 05/29/2010 12:23 PM, Julien Claassen wrote:

>> Hello Aaron and Jack-Team!

>> =A0 There seems to be a bug in my jack_lsp. I just started a2jmidi=

d and

quoted text>> j2amidi_bridge. when I do a jack_lsp I get all the ports.

>> =A0 When I do: jack_lsp -t midi I only get one port from jack_midi=

_clock,

quoted text>> but none of the other ones.

>> =A0 When I type: jack_lsp -t, I can't see a difference between=

 the

quoted text>> jack_midi_clock port and the others:

>> jack_lsp -t

>> [...]

>> a2j:Virtual Raw MIDI 0-0 [16] (capture): VirMIDI 0-0

>> =A0 =A0 =A0 =A0 8 bit raw midi

>> a2j:Virtual Raw MIDI 0-0 [16] (playback): VirMIDI 0-0

>> =A0 =A0 =A0 =A0 8 bit raw midi

>> a2j:Virtual Raw MIDI 0-1 [17] (capture): VirMIDI 0-1

>> =A0 =A0 =A0 =A0 8 bit raw midi

>> a2j:Virtual Raw MIDI 0-1 [17] (playback): VirMIDI 0-1

>> =A0 =A0 =A0 =A0 8 bit raw midi

>> a2j:Virtual Raw MIDI 0-2 [18] (capture): VirMIDI 0-2

>> =A0 =A0 =A0 =A0 8 bit raw midi

>> a2j:Virtual Raw MIDI 0-2 [18] (playback): VirMIDI 0-2

>> =A0 =A0 =A0 =A0 8 bit raw midi

>> a2j:Virtual Raw MIDI 0-3 [19] (capture): VirMIDI 0-3

>> =A0 =A0 =A0 =A0 8 bit raw midi

>> a2j:Virtual Raw MIDI 0-3 [19] (playback): VirMIDI 0-3

>> =A0 =A0 =A0 =A0 8 bit raw midi

>> a2j:M Audio Delta 1010LT [20] (capture): M Audio Delta 1010LT MIDI=
>> =A0 =A0 =A0 =A0 8 bit raw midi

quoted text>> a2j:M Audio Delta 1010LT [20] (playback): M Audio Delta 1010LT MID=

I

quoted text>> =A0 =A0 =A0 =A0 8 bit raw midi

>> j2a_bridge:playback

>> =A0 =A0 =A0 =A0 8 bit raw midi

>> a2j:j2a_bridge [129] (capture): capture

>> =A0 =A0 =A0 =A0 8 bit raw midi

>> Jack MIDI Clock:midi_out

>> =A0 =A0 =A0 =A0 8 bit raw midi

>>

>> =A0 Or is the argument "midi" only seen as the start of =

a port_name?

quoted text>> =A0 If so, Aaron, you must rewrite this part of jackctl (I guess y=

ou do

quoted text>> what I described, because I get exactly your output). You should r=

ewrite

quoted text>> it using:

>> jack_lsp -t

>> =A0 And then parse the type info underneath each name. I think a s=

imple

quoted text>> grabbing for "audio" or "midi" will do. But I =

guess, that in the long

quoted text>> run, using the python module for jack, will be more efficient and =

easy

quoted text>> to use.

>> =A0 Kindly yours

>> =A0 =A0 =A0 =A0 =A0 Julien

>>

>
--
Aaron Krister Johnson

http://www.akjmusic.c=

om

http://www.untwelve.o=

rg

-- Best,Aaron Krister Johnsonhttp://www.a=

kjmusic.comhttp://www.untwelve.=

org
--0016364c7eaf8b576304888f5f73--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
Re: [LAU] [LAD] like "qjackctl", but trimmed of all fat, Aaron Krister Johnson, (Sat May 29, 4:42 pm)
Re: [LAU] [LAD] like "qjackctl", but trimmed of all fat, Aaron Krister Johnson, (Wed Jun 9, 2:08 am)