Re: [ubuntu-studio-users] Keyboard is seen but won't connect solved (I think!)

[David Sumbler]

I seem to have solved this problem.

In the Settings dialogue of qjackctl I changed MIDI driver from "raw"
to "seq", and now I can connect the keyboard to tractor etc.  It seems
to work, although I have not done very much with it yet.

I confess I hadn't tried messing about with this setting before,
because I don't remember ever having altered it, yet the keyboard used
to work OK with the computer.  But logically, I suppose it must have
been changed at some point.

Anyway, thanks for all the help you have given.  And I'm sorry to have
made an issue out of something that was, apparently, so simple to fix.

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

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

[David Sumbler]

On Tue, 2016-12-27 at 17:57 +0100, Ralf Mardorf wrote:
> An example seems to work on my machine:
> 
>   $ amidi -l
>   Dir DeviceName
>   IO  hw:0,0HDSPMx579bcc MIDI 1
>   IO  hw:3,0,0  nanoKONTROL MIDI 1
> 
>   $ pkill -9 jack; pkill a2j
> 
>   $ jackd -Xalsarawmidi -dalsa -r48000 -p256 & a2jmidid -e‬ &
> qjackctl
> 
> In QjackCtl's ALSA tab the device names are the same as displayed by
> the above amidi command, but in the MIDI tab the names are
> 
>   system  system
> midi_capture_1  midi_playback_1
> midi_capture_2  midi_playback_2
> 
> Qtractor only appears in the ALSA tab. While connecting HDSPM and
> nanoKONTROL doesn't work directly in the ALSA tab, connecting MIDI
> Through with Qtractor works. It requires some trail and error, I
> don't
> remember how to use it at the moment. It's a long time ago I used
> Linux
> for MIDI. However, IIRC a2j... is only needed if
> 
> - you are using jack2 with external synth and you want to reduce MIDI
>   jitter by using -Xalsarawmidi
> 
> - you are not necessarily using -Xalsarawmidi, but you are using
> Linux
>   apps, that only support jack MIDI and not ALSA MIDI, while other
> apps
>   only support ALSA MIDI and you want to connect jack and ALSA MIDI
> apps
> 
> If you only want to use ALSA MIDI, no -Xalsarawmidi and no jack MIDI
> apps, simply run
> 
>   $ pkill -9 jack; pkill a2j
>   $ jackd -dalsa -r48000 -p256 & qjackctl
> 
> then you should be able to connect everything by the ALSA tab without
> issues.

I get:

david@eros:~$ jackd -Xalsarawmidi -dalsa -r48000 -p256 & a2jmidid -e‬ &
qjackctl
[1] 6201
[2] 6202
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
a2jmidid: invalid option -- '�'
Usage: a2jmidid [-j jack-server] [-e | --export-hw] [-u]
Defaults:
-j default
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|256|2|48000|0|0|nomon|swmeter|-
|32bit
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to
capture-only mode
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server

and similar results with the

jackd -dalsa -r48000 -p256 & qjackctl

command.

Nothing appears in the MIDI tab of qjackctl: as ever, the keyboard
appears as both an input and output device in the ALSA tab, but can't
acrually be connected to anything else.

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

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

[Ralf Mardorf]

An example seems to work on my machine:

  $ amidi -l
  Dir DeviceName
  IO  hw:0,0HDSPMx579bcc MIDI 1
  IO  hw:3,0,0  nanoKONTROL MIDI 1

  $ pkill -9 jack; pkill a2j

  $ jackd -Xalsarawmidi -dalsa -r48000 -p256 & a2jmidid -e‬ & qjackctl

In QjackCtl's ALSA tab the device names are the same as displayed by
the above amidi command, but in the MIDI tab the names are

  system  system
midi_capture_1  midi_playback_1
midi_capture_2  midi_playback_2

Qtractor only appears in the ALSA tab. While connecting HDSPM and
nanoKONTROL doesn't work directly in the ALSA tab, connecting MIDI
Through with Qtractor works. It requires some trail and error, I don't
remember how to use it at the moment. It's a long time ago I used Linux
for MIDI. However, IIRC a2j... is only needed if

- you are using jack2 with external synth and you want to reduce MIDI
  jitter by using -Xalsarawmidi

- you are not necessarily using -Xalsarawmidi, but you are using Linux
  apps, that only support jack MIDI and not ALSA MIDI, while other apps
  only support ALSA MIDI and you want to connect jack and ALSA MIDI apps

If you only want to use ALSA MIDI, no -Xalsarawmidi and no jack MIDI
apps, simply run

  $ pkill -9 jack; pkill a2j
  $ jackd -dalsa -r48000 -p256 & qjackctl

then you should be able to connect everything by the ALSA tab without
issues.

I'm sorry, I even don't understand it at the meoment, by takiong a look
at old ja-snapshot files.

[rocketmouse@archlinux ~]$ grep -i MIDI -B8 -A8 
/home/music/arch2014.1/.tmp.03.01.ajs 


  


  
  

  
  

  
  

  
  
  

  
  
  


  
--
  








  


  
  

  
  

  

  
  

[rocketmouse@archlinux ~]$ grep -i MIDI -B8 -A8 /home/music/arch2014.1/.tmp.0
.tmp.01.05.ajs  .tmp.02.00.ajs  .tmp.02.01.ajs  .tmp.02.02.ajs  .tmp.02.03.ajs  
.tmp.03.00.ajs  .tmp.03.01.ajs
[rocketmouse@archlinux ~]$ grep -i MIDI -B8 -A8 
/home/music/arch2014.1/.tmp.01.05.ajs 


  


  
  

  
  

  
  

  
  
  

  
  
  


  
--
  









  
  

  
  


  
  

  
[rocketmouse@archlinux ~]$

-- 
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

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

[David Sumbler]

On Tue, 2016-12-27 at 16:20 +0100, Ralf Mardorf wrote:
> On Tue, 27 Dec 2016 15:06:03 +, David Sumbler wrote:
> > 
> > As for audio related auto-starts, do you mean items in /etc/rcS.d ?
> >  The only relevant item there is alsa-utils, which I assume I need.
> I'm thinking of pulseaudio, jackdbus and what ever else could be
> auto-started. I guess those auto-starts happen for the user, when
> starting a user session. Apropos /etc/rcS.d., what release are you
> using?
> 
>   lsb_release -d
> 
> Regards,
> Ralf

> david@eros:~$ lsb_release -d
> Description:  Ubuntu 16.04.1 LTS

This is UbuntuStudio, of course.

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

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

[Ralf Mardorf]

On Tue, 27 Dec 2016 15:06:03 +, David Sumbler wrote:
>As for audio related auto-starts, do you mean items in /etc/rcS.d ?
> The only relevant item there is alsa-utils, which I assume I need.

I'm thinking of pulseaudio, jackdbus and what ever else could be
auto-started. I guess those auto-starts happen for the user, when
starting a user session. Apropos /etc/rcS.d., what release are you
using?

  lsb_release -d

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

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

[David Sumbler]

On Tue, 2016-12-27 at 15:01 +0100, Ralf Mardorf wrote:
> On Tue, 27 Dec 2016 13:40:15 +, David Sumbler wrote:
> > 
> > david@eros:~$ killall -9 jackd a2jmidid qjackctl
> > jackd: no process found
> > a2jmidid: no process found
> > qjackctl: no process found
> This kill command doesn't terminate what already might be running on
> your install ;).
> 
> > 
> > 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
> I suspect something already grabbed the device, but a short test
> on my machine showed that it's unlikely an a2j vs a2jmidid issue.
> 
> Did you unplug the keyboard, reboot and then plugged in the keyboard?
> 
> Did you disable all audio related auto-starts?
> 
> Regards,
> Ralf

I just tried your first suggestion (reboot etc.) and then ran you
commands again.  Slightly different output, but the same result: the
keyboard appears in the ALSA tab but can't be connected to anything
else.

david@eros:~$ killall -9 jackd a2jmidid qjackctljackd: no process found
a2jmidid: no process found
qjackctl: no process found
david@eros:~$ jackd --sync -Xalsarawmidi -dalsa -r48000 -p256 &
a2jmidid -e & qjackctl
[1] 2416
[2] 2417
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.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for
4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for
4294967295, skipping unlock
ERROR: a2j_jack_client_create: Cannot create jack client
ERROR: a2j_start: a2j_new() failed.
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|256|2|48000|0|0|nomon|swmeter|-
|32bit
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to
capture-only mode
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server


As for audio related auto-starts, do you mean items in /etc/rcS.d ?
 The only relevant item there is alsa-utils, which I assume I need.

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

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

[Ralf Mardorf]

On Tue, 27 Dec 2016 13:40:15 +, David Sumbler wrote:
>david@eros:~$ killall -9 jackd a2jmidid qjackctl
>jackd: no process found
>a2jmidid: no process found
>qjackctl: no process found

This kill command doesn't terminate what already might be running on
your install ;).

>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

I suspect something already grabbed the device, but a short test
on my machine showed that it's unlikely an a2j vs a2jmidid issue.

Did you unplug the keyboard, reboot and then plugged in the keyboard?

Did you disable all audio related auto-starts?

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

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

[David Sumbler]

On Mon, 2016-12-26 at 20:33 +0100, Ralf Mardorf wrote:
> On Mon, 26 Dec 2016 19:07:41 +, 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

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

[Ralf Mardorf]

On Mon, 26 Dec 2016 19:07:41 +, 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

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

[David Sumbler]

On Mon, 2016-12-26 at 19:26 +0100, Ralf Mardorf wrote:
> Is there anything useful in the log file?
> 
> Please run
> 
>   grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail -50
> 
> and post the output.

Here goes - not sure that there's anything helpful there.  The whole
section represents repeated attempts to connect things, switching
keyboard off and on, rebooting computer etc.

david@eros:~$ grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail -50
Mon Dec 26 14:51:31 2016: graph reorder: new port 'system:playback_1'
Mon Dec 26 14:51:31 2016: graph reorder: new port 'system:playback_2'
Mon Dec 26 14:51:31 2016: graph reorder: new port
'system:midi_capture_1'
Mon Dec 26 14:51:31 2016: graph reorder: new port
'system:midi_playback_1'
Mon Dec 26 14:51:33 2016: Saving settings to
"/home/david/.config/jack/conf.xml" ...
Mon Dec 26 14:51:34 2016: New client 'qjackctl' with PID 2400
Mon Dec 26 14:51:54 2016: New client 'Qtractor' with PID 2453
Mon Dec 26 14:51:54 2016: Connecting 'system:capture_1' to
'Qtractor:Master/in_1'
Mon Dec 26 14:51:54 2016: Connecting 'system:capture_2' to
'Qtractor:Master/in_2'
Mon Dec 26 14:51:54 2016: Connecting 'Qtractor:Master/out_1' to
'system:playback_1'
Mon Dec 26 14:51:54 2016: Connecting 'Qtractor:Master/out_2' to
'system:playback_2'
Mon Dec 26 15:17:16 2016: scan: deleted port hw:2,0,0 in-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 15:17:16 2016: scan: deleted port hw:2,0,0 out-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 15:17:32 2016: scan: added port hw:2,0,0 in-hw-2-0-0-CASIO-
USB-MIDI-MIDI-1
Mon Dec 26 15:17:32 2016: scan: added port hw:2,0,0 out-hw-2-0-0-CASIO-
USB-MIDI-MIDI-1
Mon Dec 26 15:17:32 2016: scan: opened port hw:2,0,0 in-hw-2-0-0-CASIO-
USB-MIDI-MIDI-1
Mon Dec 26 15:17:32 2016: scan: opened port hw:2,0,0 out-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 15:53:13 2016: scan: deleted port hw:2,0,0 in-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 15:53:13 2016: scan: deleted port hw:2,0,0 out-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 15:53:25 2016: Disconnecting 'system:capture_1' from
'Qtractor:Master/in_1'
Mon Dec 26 15:53:25 2016: Disconnecting 'system:capture_2' from
'Qtractor:Master/in_2'
Mon Dec 26 15:53:25 2016: Disconnecting 'Qtractor:Master/out_1' from
'system:playback_1'
Mon Dec 26 15:53:25 2016: Disconnecting 'Qtractor:Master/out_2' from
'system:playback_2'
Mon Dec 26 15:53:25 2016: Client 'Qtractor' with PID 2453 is out
Mon Dec 26 15:53:39 2016: scan: added port hw:2,0,0 in-hw-2-0-0-CASIO-
USB-MIDI-MIDI-1
Mon Dec 26 15:53:39 2016: scan: added port hw:2,0,0 out-hw-2-0-0-CASIO-
USB-MIDI-MIDI-1
Mon Dec 26 15:53:39 2016: scan: opened port hw:2,0,0 in-hw-2-0-0-CASIO-
USB-MIDI-MIDI-1
Mon Dec 26 15:53:39 2016: scan: opened port hw:2,0,0 out-hw-2-0-0-
CASIO-USB-MIDI-MIDI-1
Mon Dec 26 15:54:27 2016: New client 'ardourprobe' with PID 4094
Mon Dec 26 15:54:27 2016: Client 'ardourprobe' with PID 4094 is out
Mon Dec 26 15:54:27 2016: New client 'ardourprobe' with PID 4094
Mon Dec 26 15:54:27 2016: Client 'ardourprobe' with PID 4094 is out
Mon Dec 26 15:57:38 2016: New client 'Qtractor' with PID 4328
Mon Dec 26 15:57:38 2016: Connecting 'system:capture_1' to
'Qtractor:Master/in_1'
Mon Dec 26 15:57:38 2016: Connecting 'system:capture_2' to
'Qtractor:Master/in_2'
Mon Dec 26 15:57:38 2016: Connecting 'Qtractor:Master/out_1' to
'system:playback_1'
Mon Dec 26 15:57:38 2016: Connecting 'Qtractor:Master/out_2' to
'system:playback_2'
Mon Dec 26 16:00:14 2016: Disconnecting 'system:capture_1' from
'Qtractor:Master/in_1'
Mon Dec 26 16:00:14 2016: Disconnecting 'system:capture_2' from
'Qtractor:Master/in_2'
Mon Dec 26 16:00:14 2016: Disconnecting 'Qtractor:Master/out_1' from
'system:playback_1'
Mon Dec 26 16:00:14 2016: Disconnecting 'Qtractor:Master/out_2' from
'system:playback_2'
Mon Dec 26 16:00:14 2016: Client 'Qtractor' with PID 4328 is out
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

Thanks for all your help.

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

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

[Ralf Mardorf]

On Mon, 26 Dec 2016 19:26:13 +0100, Ralf Mardorf wrote:
>Is there anything useful in the log file?
>
>Please run
>
>  grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail -50
>
>and post the output.

It might be that nothing ALSA MIDI related is part of a _jack_
log file ;).

-- 
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

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

[Ralf Mardorf]

Is there anything useful in the log file?

Please run

  grep "$(date "+%b %d")" ~/.log/jack/jackdbus.log|tail -50

and post the output.

-- 
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

Re: [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 +, David Sumbler wrote:
> > 
> > On Mon, 2016-12-26 at 17:01 +0100, Ralf Mardorf wrote:
> > > 
> > > On Mon, 26 Dec 2016 15:40:00 +, 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@eros:~$ amidi -l
> > Dir DeviceName
> > IO  hw:2,0,0  CASIO USB-MIDI MIDI 1
> > david@eros:~$   pgrep -a jack
> > 2324 /usr/bin/jackdbus auto
> > 2400 /usr/bin/qjackctl
> > david@eros:~$   pgrep -a a2j
> > david@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@archlinux ~]$ grep alsarawmidi ~/.config/jack/conf.xml
>   
> [rocketmouse@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

-- 
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

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

[Ralf Mardorf]

On Mon, 26 Dec 2016 17:05:08 +, David Sumbler wrote:
>On Mon, 2016-12-26 at 17:01 +0100, Ralf Mardorf wrote:
>> On Mon, 26 Dec 2016 15:40:00 +, 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@eros:~$ amidi -l
>Dir DeviceName
>IO  hw:2,0,0  CASIO USB-MIDI MIDI 1
>david@eros:~$   pgrep -a jack
>2324 /usr/bin/jackdbus auto
>2400 /usr/bin/qjackctl
>david@eros:~$   pgrep -a a2j
>david@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@archlinux ~]$ grep alsarawmidi ~/.config/jack/conf.xml
  
[rocketmouse@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

-- 
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

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

[Pietro Bergamo]

I've had a similar issue some time ago (trying to use midi in Pure Data) and my 
workaround was to make the connections through Patchage. It just worked, don't 
ask me why, and I've given it no thought ever since. But I think it would be 
nice to post the output and see if there is anything to be fixed.Best 
regards,Pietro
 

Em Segunda-feira, 26 de Dezembro de 2016 14:02, Ralf Mardorf 
 escreveu:
 

 On Mon, 26 Dec 2016 15:40:00 +, 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.

-- 
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


   -- 
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

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

[David Sumbler]

On Mon, 2016-12-26 at 17:01 +0100, Ralf Mardorf wrote:
> On Mon, 26 Dec 2016 15:40:00 +, 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@eros:~$ amidi -l
Dir DeviceName
IO  hw:2,0,0  CASIO USB-MIDI MIDI 1
david@eros:~$   pgrep -a jack
2324 /usr/bin/jackdbus auto
2400 /usr/bin/qjackctl
david@eros:~$   pgrep -a a2j
david@eros:~$

(No output from the 3rd command.)

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

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

[Ralf Mardorf]

On Mon, 26 Dec 2016 15:40:00 +, 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.

-- 
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