Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lorn Potter <lpotter@trolltech.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Moving from OSS to ALSA
Date: Mon, 12 Jan 2004 11:15:05 +1000	[thread overview]
Message-ID: <200401121115.05195.lpotter@trolltech.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0401120053050.22195-100000@vaino.wakkanet.fi>

On Monday 12 January 2004 9:11 am, Kai Vehmanen wrote:

> Now the commercial OSS (www.opensound.com) is a different thing. It too
> (like ALSA) provides coherent behaviour across different drivers.

I guess this is what I am talking about, really.


> > _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?
>
> Believe me, I agree with you 100% with regards to importance of
> simplicity. ALSA still has some complex edges, but is has come a long way.
> More documentation, tutorials and example code are still needed, but it
> takes time (and volunteers) to create them. I'm sure help is appreciated.

The problem here is, the people writing docs/tutorials need in depth knowledge 
of how this all works. And unfortunately, the best people to do this are the 
developers themselves. 


> But that's just one example. ALSA needs to support much more complex mixer
> configurations than OSS, and this of course comes with a price.
>
> It is very difficult to try to hide all this complexity from the developer
> without in the end limiting what the developer can do. So it's a question
> of finding out a good balance between what can be done and how easy it is.
> I guess currently ALSA is still too much on the complex side, but slowly
> the correct balance will be found... So your input is very much
> appreciated, but at the same time, please don't lose hope just yet. :)

Oh, I havent lost hope at all. I am very excited about ALSA nearing version 1.

I don't want to limit what alsa can do, only have access to a simple-ized part 
of the API, that's fast and easy for developers to write.  Which is what I 
view the OSS compat. to be.

I work with embedded devices, and so I am always thinking of ways to optimize 
the code and make apps smaller, which also means writing more app with less 
code.



> --
>  http://www.eca.cx
>  Audio software for Linux!

-- 
Lorn 'ljp' Potter
Qtopia Community Manager
lpotter at trolltech.com



-------------------------------------------------------
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

  reply	other threads:[~2004-01-12  1:15 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
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 [this message]
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=200401121115.05195.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox