On Sun, 30 Mar 2014, Kaj Ailomaa wrote:
Apparently jack1 will autostart a2jmidid, but not jack2. We should look at making that a reality, as far upstream as possible. Preferably in jack2 itself. If not possible, then in Debian.
If jack1 only starts a2j, but does not incorperate the code (as is the intent so far as I know) then I don't see a huge gain. Jack1 is normally started from the command line and so having jack start a2j is nice, jack2 is normally started by a tool like qjackctl (that is certainly not the only one) which can also start a2j. In qjackctl, the user has to set this up but in falktx tool it is just a setting. we could probably change the defaults on qjackctl as well to make this more automatic. But the real answer is to use the a2j code to replace what jack has now. In my case, when jackdbus starts, so does a2jmidid. If the plan is to have a control application that starts jack as part of it's functions, then a2j hsould be optionally started by the same controler. I am guessing that the jack dev mail lists should go on my watch list :P more stuff to wade through.
-- Len Ovens www.ovenwerks.net -- ubuntu-studio-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
