Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@attbi.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: RE: Further info: Bug: ALSA Sequencer or MTPAV - easy to reproduce
Date: 12 Feb 2003 17:20:12 -0800	[thread overview]
Message-ID: <1045099213.1982.4.camel@Godzilla> (raw)
In-Reply-To: <Pine.LNX.4.44.0302122223430.30420-100000@pnote.perex-int.cz>

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

On Wed, 2003-02-12 at 13:25, Jaroslav Kysela wrote:
> On Wed, 12 Feb 2003, Mark Knecht wrote:
> 
> > Jaroslav,
> >    Hi. Actually, I had been looking around for where to report this sort of
> > problem. I'm using an HDSP 9652 for MIDI input and getting stuck notes on
> > all soft synths I'm using. (amSynth, ZynAddSubFx and iiwusynth) I'm at a bit
> > of a loss as to how to debug this, but I do see the problem.
> > 
> >    I have found that it is independent of MIDI applications, as I see the
> > problem if I just use kaconnect to hook MIDI input to the soft synth and
> > qjackconnect to hook analog output to my speakers.
> 
> Could you try the command 'dd if=/dev/snd/midiC0D0 of=abcd bs=1' and play
> some notes on connected keyboard? In the file abcd will be the raw context
> of midi input, so we can determine, if it's driver or sequencer problem.
> 
> 						Jaroslav

Hi,
   OK, as requested, here's a few chords and some notes. However, I
cannot hear the soft synth when doing this, and I normally only get a
stuck note once every 5-10 minutes, so there's no guarantee that there's
anything interesting in here.

   Maybe I could record something, using Rosegarden, until I get a stuck
note, and give you a MIDI file? Don't know if that would be of much help
as this problem is not terribly repeatable yet.

   Is there any way I can pipe this input to my soft synth so I can hear
what I'm doing?

Cheers,
Mark

[-- Attachment #2: midi_notes --]
[-- Type: application/octet-stream, Size: 138 bytes --]

  parent reply	other threads:[~2003-02-13  1:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 19:28 Bug: ALSA Sequencer or MTPAV - easy to reproduce Ryan Pavlik
2003-02-12 20:30 ` Further info: " Ryan Pavlik
2003-02-12 20:41   ` Jaroslav Kysela
2003-02-12 20:59     ` Mark Knecht
2003-02-12 21:25       ` Jaroslav Kysela
2003-02-12 21:32         ` Mark Knecht
2003-02-13  1:20         ` Mark Knecht [this message]
2003-02-12 21:44     ` YES! :-) Was: " Ryan Pavlik
2003-02-12 23:33       ` Paul Davis
2003-02-13 11:54       ` Immanuel Litzroth
2003-02-13 12:13         ` Takashi Iwai
2003-02-12 22:35     ` [PATCH]: " Ryan Pavlik
2003-02-13  9:18       ` Takashi Iwai
2003-02-13 16:27         ` Jaroslav Kysela
2003-02-13 18:57           ` Ryan Pavlik
2003-02-13 20:23             ` Jaroslav Kysela

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=1045099213.1982.4.camel@Godzilla \
    --to=markknecht@attbi.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=perex@suse.cz \
    /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