From: "Denis de Leeuw Duarte" <denis@cyozlab.com>
To: alsa-devel@lists.sourceforge.net
Subject: Which API for MIDI?
Date: Wed, 10 Dec 2003 10:29:44 +0100 (CET) [thread overview]
Message-ID: <20031210092944.0F1A05543@slik.org> (raw)
Hello folks,
I'm starting work on a new midi sequencing app, but I'm a bit confused by
the different API options ALSA offers. I've been reading whatever snippets
I can find on the web, mostly mailing list archives, and if I understand
correctly my options are basically the rawmidi API and the alsa sequencer
API. With the former I must handle all timing myself in user space and
with the latter this is all done by ALSA, is that a correct description or
am I mistaken?
My question is: if my first priority is to have stable, reliable timing
and performance, which API should I choose, taking the current state of
the alsa sequencer code into consideration?
Many thanks in advance to anyone who can shed some light on this.
Regards,
Denis
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next reply other threads:[~2003-12-10 9:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 9:29 Denis de Leeuw Duarte [this message]
2003-12-10 10:35 ` Which API for MIDI? Clemens Ladisch
2003-12-10 11:06 ` Tim Goetze
2003-12-10 11:42 ` Patrick Shirkey
2003-12-10 14:26 ` Clemens Ladisch
2003-12-10 14:50 ` Paul Davis
2003-12-11 11:14 ` Clemens Ladisch
2003-12-10 19:50 ` Tim Goetze
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=20031210092944.0F1A05543@slik.org \
--to=denis@cyozlab.com \
--cc=alsa-devel@lists.sourceforge.net \
/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.