All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Ole Juul Kolding <dacobi@juvul.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Listing raw midi devices "The Right Way"?
Date: Wed, 18 Jun 2008 17:43:45 +0200	[thread overview]
Message-ID: <1213803825.3771.25.camel@nixbox> (raw)
In-Reply-To: <48591B5A.9070808@ladisch.de>

On Wed, 2008-06-18 at 16:27 +0200, Clemens Ladisch wrote:
> Jacob Ole Juul Kolding wrote:
> > I already found a code example that reads raw midi packages form a
> > specified device but I need to have a complete list of ALL raw midi
> > capable devices and ports on the system.
> >
> > What is the "Right Way" for an app to build such a list?
> 
> See the source code of amidi.
> 
> You probably should be using the sequencer instead of the raw MIDI
> interface, in which case look at the source code of arecordmidi.
> 

I'm not sure if sequencer is to high level, 
all i need is a way to capture all incoming midi events
which then will be placed in an existing database system.

Currently in OS X and in windows I have a callback that reads each 
midi event for each port as a list of 3 bytes which are then added to a 
C++ STL vector for later processing.

How could something similar be done with alsa?

/Jacob Kolding
> HTH
> Clemens
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2008-06-18 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 14:27 Listing raw midi devices "The Right Way"? Clemens Ladisch
2008-06-18 15:43 ` Jacob Ole Juul Kolding [this message]
2008-06-18 15:51   ` Clemens Ladisch
  -- strict thread matches above, loose matches on Subject: below --
2008-06-18 13:05 Jacob Ole Juul Kolding

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=1213803825.3771.25.camel@nixbox \
    --to=dacobi@juvul.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    /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.