alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Damon Chaplin <damon@karuna.eclipse.co.uk>
To: Clemens Ladisch <cladisch@fastmail.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: Problem with CME UF5 MIDI keyboard master volume	slider
Date: Tue, 07 Aug 2007 17:18:07 +0100	[thread overview]
Message-ID: <1186503487.3160.26.camel@localhost.localdomain> (raw)
In-Reply-To: <1186396868.28794.1203930879@webmail.messagingengine.com>

On Mon, 2007-08-06 at 12:41 +0200, Clemens Ladisch wrote:
> Damon Chaplin wrote:
> > I have a CME UF5 MIDI keyboard (USB), which mostly works fine with ALSA.
> > 
> > However if I move the Master Volume slider I stop getting MIDI events -
> > I have to disconnect the snd_seq port and reconnect it to get MIDI
> > events working again.
> 
> Is there any error message in the system log when this happens?

No, I don't think so. You mean /var/log/messages?


> > Also, I wanted to try the rawmidi test app, but what would the device ID
> > be?
> 
> Have a look at the output of "amidi -l".

Thanks. I've got rawmidi working, and it doesn't seem to have a problem
with the master volume slider. So I guess it is an alsa-seq issue.

If I move the slider I get this in rawmidi (4 lines for each increment):

read f0
read 01
read 7f
read 7e

read f0
read 01
read 7f
read 7d


Are they valid MIDI messages?

Damon

  reply	other threads:[~2007-08-07 16:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-04 10:34 Problem with CME UF5 MIDI keyboard master volume slider Damon Chaplin
2007-08-06 10:41 ` Clemens Ladisch
2007-08-07 16:18   ` Damon Chaplin [this message]
2007-08-08  8:11     ` Clemens Ladisch
2007-08-08 13:53       ` Damon Chaplin
2007-08-08 14:44         ` Clemens Ladisch
2007-08-08 16:36           ` Damon Chaplin
2007-08-09  8:27             ` Clemens Ladisch
2007-08-10 14:55               ` Clemens Ladisch
2007-08-13 15:38                 ` Damon Chaplin

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=1186503487.3160.26.camel@localhost.localdomain \
    --to=damon@karuna.eclipse.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=cladisch@fastmail.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).