From: Lorn Potter <lpotter@trolltech.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Moving from OSS to ALSA
Date: Mon, 12 Jan 2004 08:29:54 +1000 [thread overview]
Message-ID: <200401120829.54299.lpotter@trolltech.com> (raw)
In-Reply-To: <20040111181311.7726a5b5.james@jigsawdezign.com>
On Monday 12 January 2004 4:13 am, James Wright wrote:
> I am currently looking into rewriting our current OSS sound routines to
> native ALSA, as it seems OSS will invariably be phased out now that the
> ALSA driver is distrubuted with the Linux kernel, plus ALSA seems to have a
> great number of benefits for us.
Personally, I hope OSS compat will never be phased out. Why? OSS is simple,
and concise. If I am writing a simple audio recording/playing app, I can get
the job done using OSS code in _much_ less lines of code.
_Dont get me wrong_, ALSA is great and a lot more powerful than OSS, but it is
lacking a simple API.
Ever try to write an In/Out volume control mixer in OSS? Ever try to port that
same mixer to ALSA? From what I can gather (alsa seems to be lacking mixer
docs/tutorial) , the only way to change the mic input level (alsa), I have to
enumerate over every mixer gizmo and check to see if its the mic, and then
change it if I think it appears to be the Mic.
Using OSS, I can do that in one line.
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
next prev parent reply other threads:[~2004-01-11 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 18:13 Moving from OSS to ALSA James Wright
2004-01-11 18:28 ` Paul Davis
2004-01-11 21:39 ` James Wright
2004-01-11 22:29 ` Lorn Potter [this message]
2004-01-11 22:48 ` Måns Rullgård
2004-01-11 22:49 ` James Wright
2004-01-11 23:11 ` Kai Vehmanen
2004-01-12 1:15 ` Lorn Potter
2004-01-12 8:42 ` Jaroslav Kysela
2004-01-12 12:54 ` Paul Davis
2004-01-12 13:56 ` 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=200401120829.54299.lpotter@trolltech.com \
--to=lpotter@trolltech.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.