From: Paul Barton-Davis <pbd@Op.Net>
To: linux-sound@vger.kernel.org
Subject: Re: [alsa-devel] Re: Bad MIDI performance : 10ms latency instead of the expected 1-1.5ms
Date: Sat, 18 Sep 1999 22:44:05 +0000 [thread overview]
Message-ID: <marc-linux-sound-93769443822861@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93571438020118@msgid-missing>
>Im the only one that have problems with perfomance while receiving
>midi data ? It is droping a lot of events. Oss don't drop so mush,
>but alsa is useless. Is it SMP problem ? Low irq responce times ? I
>have a SB PCI 128 and a hoontech and have the same problem with
>both. (The hoontech is only avalible with alsa driver)
I don't know if you're the only one, but certainly not all people with
the hoontech's have this problem, even with SMP systems. I have a
Hoontech 4D-NX and a Tropez+, and my MIDI response and functionality
is as good as any MIDI hardware makes possible. I lose no events, even
in the face of a lot of MIDI data transmission (e.g. a MIDI fader box
being actively manipulated at the same time as a MIDI h/w sequencer
and an external synth that sends active sense bytes every few msecs).
You may have a bigger potential problem right now in terms of quoting
irrelevant messages in their entirety and sending MIME-based mail to
various email lists which have a majority of members who don't like
it.
--p
prev parent reply other threads:[~1999-09-18 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-27 0:24 [alsa-devel] Re: Bad MIDI performance : 10ms latency instead of the expected 1-1.5ms Paul Barton-Davis
1999-08-27 9:59 ` Benno Senoner
1999-09-18 22:44 ` Paul Barton-Davis [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=marc-linux-sound-93769443822861@msgid-missing \
--to=pbd@op.net \
--cc=linux-sound@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox