All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Fletcher <colin.m.fletcher@googlemail.com>
To: alsa-devel@alsa-project.org
Subject: Can't connect to MIDI output of Edirol UA-1000
Date: Tue, 18 Sep 2012 15:05:10 +0100	[thread overview]
Message-ID: <50587F96.8080005@googlemail.com> (raw)


Hello all,

I hope this is the right place to report this and ask for help: if
not, I'd be glad of a pointers to any more appropriate forum.

I've just recently noticed that connections to the MIDI output of my
Edirol UA-1000 fail when using the snd_ua101 driver in recent kernels.

Although the port is listed, connections to it fail from all the
software I've tried: qjackctl, a2jmidid and aconnect all fail to connect.

aconnect simply reports "Connection failed (Input/output error)";
a2jmidid -e says "ERROR: a2j_port_create: snd_seq_connect_to() for
20:0 failed with error -5"; and qjackctl reports no error but refuses
to make the connection.

I've observed the problem in stable kernels 3.0.39 and 3.4.11; it
works as expected when booted into a 2.6.32 kernel, where the
snd_usb_audio driver is used for the UA-1000. Other USB MIDI devices
appear to work fine with the newer kernels.

Incidentally, I also noticed that the 'Control' MIDI in & out of the
UA-1000 no longer appear when using snd_ua101, but I don't think this
is related, since changing the values of midi_ep.out_cables and
midi_ep.in_cables to 3 in the ua101_probe() function in
sound/usb/misc/ua101.c brings the control in & out back, but I'm still
unable to connect the outputs.

Any help, suggestions, patches or requests for more details gratefully
received!

Thank you,

Colin Fletcher.

             reply	other threads:[~2012-09-18 14:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 14:05 Colin Fletcher [this message]
2012-09-18 14:23 ` Can't connect to MIDI output of Edirol UA-1000 Clemens Ladisch
2012-09-18 14:47   ` Colin Fletcher
2012-09-18 15:14     ` Colin Fletcher
2012-11-15 13:15       ` Colin Fletcher
2012-11-15 14:14         ` Clemens Ladisch
2012-11-15 19:34           ` Colin Fletcher
2012-09-24 10:23 ` Jannis Achstetter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50587F96.8080005@googlemail.com \
    --to=colin.m.fletcher@googlemail.com \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.