Add new comment

Hello Dan and AutoStatic!

I think your posts highlight two problems in QJackCtl.

1. When you select interface from interface menu, QJackCtl identifies it by hardware enumeration, not by Alsa device name.
2. Presets are a little bit hard to use

Solution to first problem is obvious: someone should change the code so that when you select an interface from Interface menu, it automatically gets identified by Alsa device name. I think this is possible, but requires some work. I haven't had time (yet) to check how QJackCtl really works in code level, so I don't know how big job this would be.

Second problem needs more pondering. How presets could be easier?
This is how the Pulse audio settings windows looks in Ubuntu: http://4.bp.blogspot.com/-GmHZ_m1U3MY/T5j5Yed7-VI/AAAAAAAACuU/Y0Biq495Yo...
Could there be a clearly visible area for different presets like there is area for different soundcards in Ubuntu sound settings window? Could there be Mac-like easy "+" and "-" -buttons for adding and removing presets? That way the whole clumsy saving process would be gone...

I've attached a quick mockup about this idea: http://postimage.org/image/vm60cspj3/

In the mockup I've also changed the Jack midi bridge -feature a little :) I know a2jmidid, but always when I try to use it, it crashes after few hours. jackd's own midi driver has always worked without problems for me. However, now the mockup includes a little text that tells you a2jmidid takes care of the midi bridging :D This is the way it should work in my opinion. a2jmidid has Dbus interface, so this could be possible.

I'm not familiar with QJackCtl codebase, but if I'm the only one interested implementing these, maybe I should find time some day to do this :D