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

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 <robin(a)gareus.org> Date: Sat, 29 May 2010 14:00:52 To: Julien Claassen<julien(a)c-lab.de> Cc: Aaron Krister Johnson<aaron(a)akjmusic.com>om>; <linux-audio-user(a)lists.linuxaudio.org>rg>; <linux-audio-dev(a)lists.linuxaudio.org> 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: