All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@attbi.com>
To: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: HDSP 9652 MIDI IN - stuck notes
Date: 26 Feb 2003 20:47:41 -0800	[thread overview]
Message-ID: <1046321261.2626.28.camel@Godzilla> (raw)

[-- Attachment #1: Type: text/plain, Size: 2562 bytes --]

Hi,
   I've had a miserable stuck note problem with Alsa MIDI for a while,
so I finally sat down this evening to try and determine where the
problem was coming from, and it appears to be the HDSP 9652 MIDI input.

   My system has two 2-port MIDI interfaces, the HDSP 9652 (Alsa MIDI
64:0 & 64:32) and a MidiSport 2x2 (Alsa MIDI 72:0 & 72:1) I am using
three external hardware synths on different ports (Alsa 64:0, 72:0 and
72:1) and additionally I ran a copy each of the Linux synths ZynAddSubFx
(Alsa 130:0) and amSynth (Alsa 128:0) at the same time. (I.e. - 5 synths
in parallel, all being driven by a single MIDI input.)

   To do the tests, I use kaconnect and aconnect to build routing in the
MIDI stack to connect a single input to all outputs, which looks like
the attachment when I attach all outputs to the MidiSport Port A input.
In this configuration I can play continually, basically overdriving the
whole system with lots of MIDI events, including controllers and sustain
pedal, and I have no problems. I can do this for at least 15 minutes
with no problem on any of the synths.

   If I then change my keyboard to drive the HDSP 9652 input 1 (Alsa
64:0) and change the connections internally to drive all of outputs, I
get stuck notes pretty much immediately. It seems a bit worse with the
sustain pedal, but does not seem to be effected at all by controllers.
It is heavily effected by the MIDI note density. If I hit only one or
two notes, I'm not likely to get it, but using the sustain pedal I can
create the problem in under a minute.

   To be sure it's the input and not the outputs (as much as I can be) I
have external synths attached to the Alsa outputs on 64:0, 72:0 and
72:1. When I get a stuck note, I seem to get it on both internal soft
synths and all three external hardware synths at the same time. For this
reason I deduce that it is the HDSP input that is not clearing out
whatever event queue that holds this stuff and somehow the note never
shuts off.

   I'll be happy to try any other tests anyone wants me to look into.

   I'd be curious to know if this is a problem on any of the other RME
products that have MIDI or whether it's specifically a HDSP 9652 issue.
Also, have any other HDSP 9652 owners seen this?

   Please let me know what I might be able to do to help further get
this solved. Knowing now that the MidiSport doesn't have a problem, I
can just use it and for me that's fine. However, for others that might
be depending on the HDSP 9652 as a primary interface this would not be
acceptable.

Thanks,
Mark



[-- Attachment #2: snapshot1.png --]
[-- Type: image/png, Size: 6449 bytes --]

             reply	other threads:[~2003-02-27  4:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27  4:47 Mark Knecht [this message]
2003-02-28 12:14 ` HDSP 9652 MIDI IN - stuck notes Takashi Iwai
2003-02-28 12:56   ` Mark Knecht
2003-02-28 13:09     ` Mark Knecht
2003-03-06 19:50       ` Mark Knecht

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=1046321261.2626.28.camel@Godzilla \
    --to=markknecht@attbi.com \
    --cc=alsa-devel@lists.sourceforge.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 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.