On Mon, 2016-12-26 at 20:33 +0100, Ralf Mardorf wrote: > 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
I tried the commands you mentioned. This is what I got: david@eros:~$ killall -9 jackd a2jmidid qjackctl jackd: no process found a2jmidid: no process found qjackctl: no process found david@eros:~$ jackd --sync -Xalsarawmidi -dalsa -r48000 -p256 & a2jmidid -e & qjackctl [1] 4820 [2] 4821 jackdmp 1.9.11 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK MIDI <-> ALSA sequencer MIDI bridge, version 8 (7383d268c4bfe85df9f10df6351677659211d1ca) built on Thu Jan 1 01:00:00 1970 Copyright 2006,2007 Dmitry S. Baikov Copyright 2007,2008,2009,2011,2012 Nedko Arnaudov Bridge starting... Using JACK server 'default' Hardware ports will be exported. no message buffer overruns no message buffer overruns Bridge started Press ctrl-c to stop the bridge port created: Midi Through [14] (capture): Midi Through Port-0 port created: Midi Through [14] (playback): Midi Through Port-0 ERROR: a2j_alsa_connect_from: can't subscribe to 24:0 - Resource temporarily unavailable port skipped: CASIO USB-MIDI [24] (capture): CASIO USB-MIDI MIDI 1 ERROR: a2j_port_create: snd_seq_connect_to() for 24:0 failed with error -11 port skipped: CASIO USB-MIDI [24] (playback): CASIO USB-MIDI MIDI 1 no message buffer overruns `default' server already active Failed to open server The keyboard still appears on the ALSA tab and is unconnectable, and does not appear on the MIDI tab - hardly surprising since the commands failed. All very frustrating! David -- 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
