From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: The state of Linux audio
Date: Mon, 25 Aug 2008 09:07:54 +0100 [thread overview]
Message-ID: <g8tp8q$c4b$1@ger.gmane.org> (raw)
In-Reply-To: <f188924b0808240837nfb54b9aq6330d9994df291ba@mail.gmail.com>
Fred . wrote:
> What is the state of audio in Linux?
> How does it compare against other operating systems?
>
> Is the Linux audio functionality good or bad?
> What could be better?
> What is planned for the future?
Rather open ended questions! Is there a reason why you are asking or
just curious?
It depends what you are looking for really (desktop, pro etc.) but Linux
audio is arguably a bit of a mess with lots of APIs and abstractions
layers/libraries and a lack of a single common, agreed structure.
On the desktop, most distributions and people are pinning their hopes on
PulseAudio.
I'd advise you look at the following presentation:
http://foss.in/2007/register/speakers/talkdetailspub.php?talkid=353
This is by the PulseAudio author Lennart Pottering and has a small
section on the state of linux audio and what PulseAudio is trying to do
to consolidate this work and provide a common platform to move forward
in the desktop space.
HTHs
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mandriva Linux Contributor [http://www.mandriva.com/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
next prev parent reply other threads:[~2008-08-25 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 15:37 The state of Linux audio Fred .
2008-08-25 8:07 ` Colin Guthrie [this message]
2008-08-26 0:10 ` Sean McNamara
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='g8tp8q$c4b$1@ger.gmane.org' \
--to=gmane@colin.guthr.ie \
--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.