From: Werner Schweer <ws@seh.de>
To: Martin Langer <martin-langer@gmx.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: bugs in usb midi alsa code?
Date: Sat, 9 Nov 2002 13:45:05 +0100 [thread overview]
Message-ID: <200211091345.05395.ws@seh.de> (raw)
In-Reply-To: <Pine.HPX.4.33n.0211070857080.1450-100000@studcom.urz.uni-halle.de>
On Thursday 07 November 2002 09:10, Clemens Ladisch wrote:
> Fernando Pablo Lopez-Lezcano wrote:
> > OSS emulation (raw midi interface):
> > Midi input and output works fine on the first port,
> > ALSA:
> > input does not seem to work at all.
>
> Werner Schweer wrote:
> > same on my Roland/Edirol UA100 (audio + 2 midi ports).
>
> Martin Langer wrote:
> > last but not least: same on my Evolution MK-249C keyboard
>
> I don't think the bug is in the snd-usb-audio driver because OSS input
> seems to be working.
>
> Please try the following with the rawmidi program in alsa-lib/test:
> OSS: rawmidi -v -I /dev/midix
> ALSA direct: rawmidi -v -I /dev/snd/midiCxD0
> ALSA Lib: rawmidi -v -i hw:x,0
> ALSA Lib: rawmidi -v -i hw:x,0,0
>
> Did you update alsa-lib together with alsa-kernel? Are you sure you have
> the correct version of libasound installed, and your programs are using
> it?
My System: Roland UA100 usb audio/midi device; ALSA cvs from today (saturday)
(driver + lib), new compiled app
I'm using devfs and when i switch on the ua100 i get the following
messages:
hub.c: new USB device 00:1d.0-2, assigned address 4
snd-usb-midi: created 3 output and 3 input ports
devfs_register(unknown): could not append to parent, err: -17
devfs_register(unknown): could not append to parent, err: -17
devfs_register(unknown): could not append to parent, err: -17
devfs_register(unknown): could not append to parent, err: -17
err -17 -> file exists
And really there is a /dev/sound/unknown (major/minor 14/18).
Recording from /dev/snd/midiC1D0 ("cat /dev/snd/midiC1D0") --> works.
(Only one midi port is visible).
ALSA Lib: rawmidi -v -i hw:x,0 --> works
ALSA Lib: rawmidi -v -i hw:x,0,0 --> works
Recording from alsa sequencer ports of UA100 did not work.
With older version of ALSA i got the midi ports on the UA100 working but
not the audio part.
What my app does is:
snd_seq_port_subscribe_t* subs;
snd_seq_port_subscribe_alloca(&subs);
snd_seq_port_subscribe_set_dest(subs, &musePort);
snd_seq_port_subscribe_set_sender(subs, &adr);
int error = snd_seq_subscribe_port(alsaSeq, subs);
But no events are arriving from subscribed input port. This worked for previous
ALSA versions.
cat /proc/asound/seq/clients says:
Client info
cur clients : 4
peak clients : 4
max clients : 192
Client 0 : "System" [Kernel]
Port 0 : "Timer" (Rwe-)
Port 1 : "Announce" (R-e-)
Connecting To: 128:0
Client 72 : "External MIDI 1" [Kernel]
Port 0 : "UA-100 Port 0" (RWeX)
Connecting To: 128:0
Connected From: 128:0
Port 1 : "UA-100 Port 1" (RWeX)
Connecting To: 128:0
Connected From: 128:0
Port 2 : "UA-100 Port 2" (RWeX)
Connecting To: 128:0
Connected From: 128:0
Client 128 : "MusE Sequencer" [User]
Port 0 : "MusE Port 0" (RWe-)
Connecting To: 72:0, 72:1, 72:2
Connected From: 0:1, 72:0, 72:1, 72:2
Output pool :
Pool size : 500
Cells in use : 0
Peak cells in use : 0
Alloc success : 0
Alloc failures : 0
Input pool :
Pool size : 200
Cells in use : 0
Peak cells in use : 9
Alloc success : 9
Alloc failures : 0
Client 129 : "organ" [User]
Port 0 : "organ-1" (-We-)
Input pool :
Pool size : 200
Cells in use : 0
Peak cells in use : 1
Alloc success : 68
Alloc failures : 0
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2002-11-09 12:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 20:22 bugs in usb midi alsa code? Fernando Pablo Lopez-Lezcano
2002-11-06 9:46 ` Clemens Ladisch
2002-11-06 18:18 ` bugs in usb midi alsa code Fernando Pablo Lopez-Lezcano
2002-11-06 20:32 ` usb audio sound quality Patrick Shirkey
2002-11-07 22:23 ` Patrick Shirkey
2002-11-08 9:18 ` Patrick Shirkey
2002-11-08 10:17 ` Patrick Shirkey
2002-11-09 21:44 ` snd-usb-midi vs ohci Patrick Shirkey
2002-11-11 9:23 ` Clemens Ladisch
2002-11-06 21:04 ` bugs in usb midi alsa code Fernando Pablo Lopez-Lezcano
2002-11-06 21:53 ` Paul Davis
2002-11-06 22:43 ` Jaroslav Kysela
2002-11-07 2:10 ` Fernando Pablo Lopez-Lezcano
2002-11-07 9:17 ` Clemens Ladisch
2002-11-07 8:02 ` CS4205 SPDIF Matias Alejo Garcia
2002-11-06 10:52 ` bugs in usb midi alsa code? Werner Schweer
2002-11-06 11:43 ` Martin Langer
2002-11-07 8:10 ` Clemens Ladisch
2002-11-07 9:37 ` Martin Langer
2002-11-07 10:09 ` Clemens Ladisch
2002-11-07 10:21 ` Martin Langer
2002-11-07 10:34 ` Martin Langer
2002-11-07 12:22 ` Martin Langer
2002-11-07 12:50 ` Clemens Ladisch
2002-11-07 14:20 ` Martin Langer
2002-11-07 15:15 ` Clemens Ladisch
2002-11-07 16:02 ` Martin Langer
2002-11-07 16:35 ` Clemens Ladisch
2002-11-07 17:56 ` Martin Langer
2002-11-07 18:54 ` Fernando Pablo Lopez-Lezcano
2002-11-07 23:11 ` Martin Langer
2002-11-08 8:17 ` Clemens Ladisch
2002-11-08 10:04 ` Martin Langer
2002-11-11 8:15 ` [PATCH] USB MIDI bugs Clemens Ladisch
2002-11-11 8:53 ` Martin Langer
2002-11-12 0:46 ` Fernando Pablo Lopez-Lezcano
2002-11-12 1:24 ` Fernando Pablo Lopez-Lezcano
2002-11-12 9:55 ` Clemens Ladisch
2002-11-08 8:39 ` bugs in usb midi alsa code? Clemens Ladisch
2002-11-09 12:45 ` Werner Schweer [this message]
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=200211091345.05395.ws@seh.de \
--to=ws@seh.de \
--cc=alsa-devel@alsa-project.org \
--cc=martin-langer@gmx.de \
/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.