From: "Tim E. Real" <termtech@rogers.com>
To: alsa-devel@alsa-project.org
Subject: Single vs. multiple seq client ports
Date: Tue, 03 Feb 2015 19:44:26 -0500 [thread overview]
Message-ID: <11961012.AHGMH1UnbJ@col-desktop> (raw)
Hi. Our app currently uses a single alsa midi seq client port
to address all external midi ports.
I have an opportunity now to change this to allow as many
client ports as desired, for example one client port for each
external port found.
If I proceed, it is possible the user may have many client ports
if desired.
What are the advantages and disadvantages if any, in terms
of speed and resources, of having a single client port versus
multiple client ports?
Thanks.
Tim.
next reply other threads:[~2015-02-04 0:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 0:44 Tim E. Real [this message]
2015-02-04 7:52 ` Single vs. multiple seq client ports Clemens Ladisch
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=11961012.AHGMH1UnbJ@col-desktop \
--to=termtech@rogers.com \
--cc=alsa-devel@alsa-project.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 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.