All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lennart Poettering <mznyfn@0pointer.de>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Cc: PulseAudio Discussion List <pulseaudio-discuss@mail.0pointer.de>
Subject: Guide to Linux Sound APIs
Date: Thu, 25 Sep 2008 00:48:33 +0200	[thread overview]
Message-ID: <20080924224833.GA8280@tango.0pointer.de> (raw)

Heya!

At the audio microconf at the Linux plumbers conference one thing
became very clear: it is very difficult for programmers to figure out
which audio API to use for which purpose and which API not to use when
doing audio programming on Linux. Someone needed to sit down and write
up a small guide. And that's what I just finished doing.

I'd thus like to draw your attention to this new (long) blog story of
mine containing this guide:

http://0pointer.de/blog/projects/guide-to-sound-apis

I'd be very thankful for comments, especially from you Takashi and
Jaroslav since it contains quite some details about the "safe" subset
of the ALSA API!

I'm thankful for all kinds of input!

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net         ICQ# 11060553
http://0pointer.net/lennart/           GnuPG 0x1A015CC4

             reply	other threads:[~2008-09-24 22:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 22:48 Lennart Poettering [this message]
2008-09-24 23:05 ` Guide to Linux Sound APIs Ben Finney
2008-09-25  0:17   ` Aaron J. Grier
2008-09-25  0:23     ` Lennart Poettering
2008-09-25 10:15 ` Takashi Iwai
2008-09-25 19:40   ` Lennart Poettering
2008-09-26  9:44     ` Takashi Iwai

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=20080924224833.GA8280@tango.0pointer.de \
    --to=mznyfn@0pointer.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=pulseaudio-discuss@mail.0pointer.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.