[ubuntu-studio-users] Keyboard is seen but won't connect

[David Sumbler]

On Mon, 2016-12-26 at 18:32 +0100, Ralf Mardorf wrote:
> On Mon, 26 Dec 2016 17:05:08 +0000, David Sumbler wrote:
> > 
> > On Mon, 2016-12-26 at 17:01 +0100, Ralf Mardorf wrote:
> > > 
> > > On Mon, 26 Dec 2016 15:40:00 +0000, David Sumbler wrote:  
> > > > 
> > > > 
> > > > I click to connect the keyboard input (or output) to qTractor
> > > > or
> > > > something else, and the Messages window in qJackCtl shows an
> > > > ALSA
> > > > connection change.
> > > > 
> > > > But no change is shown in the Connections window, and it seems
> > > > that
> > > > the connection is not made because nothing gets through to
> > > > qTractor.  
> > > Please copy and post the message window output, also run
> > > 
> > >   amidi -l
> > >   pgrep -a jack
> > >   pgrep -a a2j
> > > 
> > > and post it.  
> > I get:
> > 
> > david at eros:~$ amidi -l
> > Dir Device    Name
> > IO  hw:2,0,0  CASIO USB-MIDI MIDI 1
> > david at eros:~$   pgrep -a jack
> > 2324 /usr/bin/jackdbus auto
> > 2400 /usr/bin/qjackctl
> > david at eros:~$   pgrep -a a2j
> > david at eros:~$
> > 
> > (No output from the 3rd command.)
> That's ok, I only wanted to ensure that you do or don't run a command
> containing "a2j".
> 
> You have forgotten to post the output from the message window.
> 
> I can't help you with jackdbus. IMO dbus is a PITA and shouldn't be
> used
> with jack. I'm only running jackd.
> 
> I even don't understand why on my machine alsarawmidi is part of what
> seems to be the jackdbus config, but the log doesn't mention it [1].
> 
> However, assuming you would launch jackdbus with xalsarawmidi, it
> could
> be the culprit. Btw. xalsarawmidi is very good to reduce MIDI jitter,
> but using it is tricky.
> 
> Regards,
> Ralf
> 
> [1]
> [rocketmouse at archlinux ~]$ grep alsarawmidi ~/.config/jack/conf.xml
>   <driver name="alsarawmidi">
> [rocketmouse at archlinux ~]$ grep Dec\ 26 ~/.log/jack/jackdbus.log
> Mon Dec 26 18:16:43 2016: ------------------
> Mon Dec 26 18:16:43 2016: Controller activated. Version 1.9.11
> (0+f2ece2418c875eb7e7ac3d25fbb484ddda47ab46) built on Thu Jan  1
> 01:00:00 1970
> Mon Dec 26 18:16:43 2016: Loading settings from
> "/home/rocketmouse/.config/jack/conf.xml" using expat_2.2.0 ...
> Mon Dec 26 18:16:43 2016: setting parameter
> 'engine':'driver':'(null)' to value "alsa"
> Mon Dec 26 18:16:43 2016: setting parameter
> 'engine':'realtime':'(null)' to value "true"
> Mon Dec 26 18:16:43 2016: setting parameter 'drivers':'alsa':'device'
> to value "hw:0"
> Mon Dec 26 18:16:43 2016: setting parameter 'drivers':'alsa':'rate'
> to value "48000"
> Mon Dec 26 18:16:43 2016: setting parameter 'drivers':'alsa':'period'
> to value "256"
> Mon Dec 26 18:16:43 2016: setting parameter
> 'drivers':'alsa':'nperiods' to value "2"
> Mon Dec 26 18:16:43 2016: Listening for D-Bus messages
> 

Sorry I forgot the message window, but it isn't very informative!

17:59:04.754 ALSA connection graph change.
17:59:04.939 ALSA connection change.
17:59:37.698 ALSA connection graph change.
17:59:37.857 ALSA connection change.
18:00:04.185 ALSA connection change.

The first 2 lines appeared when I switched on the keyboard.  The next 2
were when I started qtractor.  And the last line is when I attempted to
connect the keyboard output to qtractor's input in the connections
window.  But it wouldn't connect, of course, despite the fact that
there is no error printed.  Weird.

Not sure where to go from here.

David