Alexander,<br><br>I will in near-future versions add alsa-MIDI port functionality. For now, from the command line there's 'aconnect', which is extremely simple and easy. My script would provide a front-end to that, perhaps making it even easier.<br>
<br>AKJ<br><br><div class="gmail_quote">On Wed, May 26, 2010 at 7:08 AM, alexander <span dir="ltr"><<a href="mailto:axeldenstore@gmail.com">axeldenstore@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">On 05/26/2010 02:23 PM, Aaron Krister Johnson wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi linux-audio peoples,<br>
<br>
I want to announce my new and fun and useful python script -- I call it 'jackctl' -- it basically is a frontend to the jack tools 'jack_lsp' and 'jack_connect'. It's like 'qjackctl' , but since it's command line, no 'q' !!!<br>
<br>
get it here:<br>
<a href="http://www.akjmusic.com/software/jackctl20100526.py" target="_blank">http://www.akjmusic.com/software/jackctl20100526.py</a><br>
<br>
Why would I embark on writing such a script? Who would want to use this?<br>
<br>
You'll want to try this if one or any of the the following apply:<br>
<br>
1) You don't want to have to install the entire QT toolkit for a single program.<br>
2) If you like the command line, use a console, but still use jack often enough<br>
3) You've used jack and 'jack_connect' through the command line before, but hated having to type the full name of the jack ports.<br>
4) You've noticed that 'qjackctl' introduces CPU overhead and xruns you don't have when you use command-line jack, i.e. you are obsessed with the lowest possible latency<br>
5) You want a fast, simple interface to connect jack ports that is even faster than a GUI---no need to point the mouse, just type two numbers and go!<br>
<br>
It's very simple. All you need is Python (and who doesn't have that on their machine). You put the script in your PATH, or link it/rename it, making sure it's exectuable. When you run it, you'll see a list of current numbered jack ports, and you can connect them by typing two numbers separated by a space. You can disconnect them by typing 'd' then the two numbers separated by a space. No hassles, and a nice feature is that it will protect you from making ear-blasting feedback connections. It's even quicker than qjackctl, b/c it takes more time to point your mouse at the ports in the GUI and then click 'connect' than it does to type two single-digit numbers and then hit return, yes?<br>
<br>
Let me know how you like it...I'm interested in reasonable feature requests. One potential TODO would be to make this script have a user-friendly way to start the jack daemon, but for now, I do that manually....<br>
<br>
Enjoy, comments welcome!<br>
<br>
</blockquote></div></div>
Quite cool, seems simple enough. However, my usb keyboard doesn't show up, or anything else that normally shows up under the "alsa" tab in qjackctl<br>
<br>
_______________________________________________<br>
Linux-audio-user mailing list<div class="im"><br>
<a href="mailto:Linux-audio-user@lists.linuxaudio.org" target="_blank">Linux-audio-user@lists.linuxaudio.org</a><br>
</div><a href="http://lists.linuxaudio.org/listinfo/linux-audio-user" target="_blank">http://lists.linuxaudio.org/listinfo/linux-audio-user</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><br>Aaron Krister Johnson<br><a href="http://www.akjmusic.com">http://www.akjmusic.com</a><br><a href="http://www.untwelve.org">http://www.untwelve.org</a><br><br>