Re: [OT] ALSA userspace API complexity



On Wed, 4 Jan 2006, Jaroslav Kysela wrote:

On Wed, 4 Jan 2006, Pete Zaitcev wrote:

On Wed, 4 Jan 2006 09:37:55 +0000, Alistair John Strachan <s0348365@xxxxxxxxxxxx> wrote:

2) ALSA API is to complicated: most applications opens single sound
   stream.

FUD and nonsense. [] http://devzero.co.uk/~alistair/alsa/

That's the kicker, isn't it? Once you get used to it, it's a workable API, if kinky and verbose. I have a real life example, too: http://people.redhat.com/zaitcev/linux/mpg123-0.59r-p3.diff But arriving on the solution costed a lot of torn hair. Look at this bald head here! And who is going to pay my medical bills when ALSA causes me ulcers, Jaroslav?

Well, the ALSA primary goal is to be the complete HAL not hidding the extra hardware capabilities to applications. So API might look a bit complicated for the first glance, but the ALSA interface code for simple applications is not so big, isn't?

Sorry Jaroslav byt this not unix way. Wny applications myst know anything about hardware layer ? In unix way all this details are rolled on kernel layer.

Also, note that app developers are not forced to use ALSA directly - there
is a lot of "portable" sound API libraries having an ALSA backend doing
this job quite effectively. We can add a simple (like OSS) API layer
into alsa-lib, but I'm not sure, if it's worth to do it. Perhaps, adding
some support functions for the easy PCM device initialization might be
a good idea.

If we have so many "portable" sound API libraries .. look most of them uses the same way for handle sound on kernel interaction. Is this complicated ALSA way is realy neccessary ?
For example .. jackd can use OSS API for handle sound device.


kloczek
--
-----------------------------------------------------------
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
-----------------------------------------------------------
Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@xxxxxxxxxxxxxxxxxx*

Allow me translate sentence from my signature to english
"People do not have problems they create them themselves"
and ALSA case matches in 100%.


Relevant Pages

  • Re: Is it time for remove (crap) ALSA from kernel tree ?
    ... What I indicated was that if someone wants to use multiple applications that work together bringing you The One Integrated Sound Experience it might make sense to use applications... ... Don't go blame ALSA for either the fact that aRTs isn't actually useful nor KDE's decision to stick with it for way too long. ... So that leaves that "bad" that you prefixed API with but keep in mind that ALSA is designed as an audio system suitable for advanced/professional use while also still filling the needs of consumer users and that it does in fact do so is obvious from the fact that everyone's using it. ... The ideal situation is that anyone in userspace is using a single API _such_ as Phonon since userspace has to synchronise things itself as well -- it might for example want to provide you with the option to automatically mute your music when you get an incoming call and this is not something which alsa-lib can do by itself. ...
    (Linux-Kernel)
  • Re: Is it time for remove (crap) ALSA from kernel tree ?
    ... We dropped OSS for ALSA for technical reasons. ... interleaved sound, one for non-interleaved sound, in addition to ... There is bad documentation, bad API, and a config file ...
    (Linux-Kernel)
  • Re: [2.6 patch] schedule obsolete OSS drivers for removal
    ... > recommend to use ALSA API directly with apps. ... At the same time the kernel API itself should be suitable to ... > I, at least, have never thought that the OSS _API_ would die. ...
    (Linux-Kernel)
  • Re: [2.6 patch] schedule obsolete OSS drivers for removal
    ... the ALSA kernel API can go public and documented (altough I ... libraries over it. ...
    (Linux-Kernel)
  • Re: [OT] ALSA userspace API complexity
    ... So API might look a bit ... >> complicated for the first glance, but the ALSA interface code for simple ... It means that you are saying that kernel should be bigger and bigger. ... ever have such problems with the OSS API redirection to another API. ...
    (Linux-Kernel)

Quantcast