From: Ryan Pavlik <rpav@nwlink.com>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: MTP/AV / Sequencer MIDI problem... design issue?
Date: Sat, 11 Jan 2003 20:37:09 -0800 [thread overview]
Message-ID: <20030111203709.20df5ff0.rpav@nwlink.com> (raw)
In-Reply-To: <200301120151.h0C1p3X8029477@spider.tela.com>
On Sat, 11 Jan 2003 20:50:49 -0500
Paul Davis <paul@linuxaudiosystems.com> wrote:
>
> i would have thought that the mtpav driver should do the same
> thing. if you want to access all 8 ports, you should have 8 access
> points (whether this is via the sequencer or the rawmidi interface),
> and write to each one of them. the use of the "Dn" byte(s?) to switch
> output ports shouldn't be exported to user space.
It does, and you do... except the driver has the problems with parallel
access of ports I mentioned in the original message. When you access
them with the sequencer API, the driver/library doesn't seem to properly
send entire messages. Thus the problem arises.
--
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
next prev parent reply other threads:[~2003-01-12 4:37 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 [this message]
2003-01-12 9:57 ` Jaroslav Kysela
2003-01-11 14:46 ` Jaroslav Kysela
2003-01-12 1:02 ` Ryan Pavlik
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=20030111203709.20df5ff0.rpav@nwlink.com \
--to=rpav@nwlink.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.com \
/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.