From: Ryan Pavlik <rpav@nwlink.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: MTP/AV / Sequencer MIDI problem... design issue?
Date: Sat, 11 Jan 2003 17:02:41 -0800 [thread overview]
Message-ID: <20030111170241.2975b352.rpav@nwlink.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0301111543330.613-100000@pnote.perex-int.cz>
On Sat, 11 Jan 2003 15:46:15 +0100 (CET)
Jaroslav Kysela <perex@perex.cz> wrote:
<snip>
> ALSA driver should handle this correctly (at least current CVS code).
> The write sequence is locked.
Hrm, I'll check through the code---after playing with it, it doesn't
appear things are 100% yet. I had decent luck at first, with messages
not trampling each other, but as I added new sequences (using seq24 to
test), odd problems developed.
The first was port 1 acting like broadcast, which I haven't seen before;
this would be fixed temporarily by reloading the driver. Then voices
started losing notes and messages, much as before.
I will look at the (new?) write locking and see if I can figure
something out.
Thanks,
--
Ryan Pavlik <rpav@users.sf.net>
"Nautical, schmautical. Give me one hour and I'll know
enough to sail us into orbit!
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
prev parent reply other threads:[~2003-01-12 1:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 19:37 MTP/AV / Sequencer MIDI problem... design issue? Ryan Pavlik
2003-01-11 13:55 ` Paul Davis
2003-01-11 18:30 ` Ryan Pavlik
2003-01-11 23:31 ` Paul Davis
2003-01-12 0:59 ` Ryan Pavlik
2003-01-12 1:50 ` Paul Davis
2003-01-12 4:37 ` Ryan Pavlik
2003-01-12 9:57 ` Jaroslav Kysela
2003-01-11 14:46 ` Jaroslav Kysela
2003-01-12 1:02 ` Ryan Pavlik [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=20030111170241.2975b352.rpav@nwlink.com \
--to=rpav@nwlink.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@perex.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 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.