On Mon, 26 Dec 2016 19:07:41 +0000, David Sumbler wrote: >david@eros:~$ grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail -50 >[snip] >Mon Dec 26 17:09:43 2016: New client 'a2j' with PID 5142 >Mon Dec 26 17:10:23 2016: Client 'a2j' with PID 5142 is out >Mon Dec 26 17:58:42 2016: Client 'qjackctl' with PID 2400 is out >Mon Dec 26 17:58:42 2016: Stopping jack server... >Mon Dec 26 17:58:42 2016: Client 'system' with PID 0 is out >Mon Dec 26 17:58:42 2016: scan: deleted port hw:2,0,0 in-hw-2-0-0- >CASIO-USB-MIDI-MIDI-1 >Mon Dec 26 17:58:42 2016: scan: deleted port hw:2,0,0 out-hw-2-0-0- >CASIO-USB-MIDI-MIDI-1 >Mon Dec 26 17:58:42 2016: Released audio card Audio1
You are welcome! $ apropos a2j a2j (1) - Wrapper script to simulate a2jmidid's non-DBUS behaviour though a2jmidid actually being... a2j_control (1) - utility to control a2jmidid daemon a2jmidi_bridge (1) - static bridge with one ALSA playback port and one JACK MIDI input port a2jmidid (1) - JACK MIDI daemon for ALSA MIDI I'm usually running something similar to $ killall -9 jackd a2jmidid qjackctl $ jackd --sync -Xalsarawmidi -dalsa -r48000 -p256 & a2jmidid -e & qjackctl so, again, I don't know jackdbus. However, I suspect that you try to use QjackCtl's ALSA tab to connect MIDI I/Os. Most likely you need to connect MIDI I/Os by QjackCtl's MIDI tab. Oops, indeed, running "pgrep -a a2j" is useless to see if something "a2j" related is active. However, the combination of "-Xalsarawmidi" and "a2jmidid -e" on my machine enforces to migrate from the ALSA tab to the MIDI tab. The connections aren't done by ALSA MIDI anymore, but instead by Jack MIDI. Perhaps you're using a similar setup. Regards, Ralf -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users