Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ivica Bukvic" <ico@fuse.net>
To: alsa-devel@lists.sourceforge.net
Cc: alsa-user@lists.sourceforge.net, linux-audio-dev@music.columbia.edu
Subject: Alsa /dev/sequencer stuff
Date: Tue, 20 May 2003 00:15:19 -0400	[thread overview]
Message-ID: <000201c31e86$6cacf0f0$ac1f830a@ICO> (raw)

Hi all, I was wondering the following:

In my app (RTMix) I will be soon implementing multiple midi-input device
opens, so that the app can be controlled from as many of the midi
controllers simultaneously as possible. One way of devising this was to
design a separate thread for every open device (using raw midi /dev/midi
etc., although I will be re-implementing that to use ALSA devices
directly). However, this might not be the most elegant way of doing
this, so what I was wondering is how does the /dev/sequencer correspond
to this issue? I mean, does it work the same way like addressing the raw
midi ports, are the message formats the same, and most importantly does
one SINGULAR /dev/sequencer encompass all of the midi ports that are
currently available?

I would greatly appreciate any help on this issue, as well as some code
examples. Thank you! Sincerely,

Ivica Ico Bukvic, composer & multimedia sculptor
http://meowing.ccm.uc.edu/~ico




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

             reply	other threads:[~2003-05-20  4:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20  4:15 Ivica Bukvic [this message]
2003-05-20  4:47 ` [linux-audio-dev] Alsa /dev/sequencer stuff Paul Davis

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='000201c31e86$6cacf0f0$ac1f830a@ICO' \
    --to=ico@fuse.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=linux-audio-dev@music.columbia.edu \
    /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