All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Lorn Potter <lpotter@trolltech.com>, alsa-devel@lists.sourceforge.net
Subject: Re: Moving from OSS to ALSA
Date: Mon, 12 Jan 2004 14:56:24 +0100	[thread overview]
Message-ID: <s5hd69pgtiv.wl@alsa2.suse.de> (raw)
In-Reply-To: <200401121254.i0CCscqt026891@dhin.linuxaudiosystems.com>

At Mon, 12 Jan 2004 07:54:37 -0500,
Paul Davis wrote:
> 
> >Yes, we're aware that our APIs are rather too much complicated for simple 
> >applications. We are designing the very simple (current name ordinary) 
> >APIs to let more developers join us. But as Kai noticed, these APIs will 
> >be a bit limited, so they won't be intended for more complex applications.
> 
> Jaroslav, please don't spend much time on this. There are no
> indications that ALSA is going to be picked as a native API by
> freedesktop.org, nor any of the incarnations of various X
> organizations as a network-transparent API. Simple applications are
> just not going to use ALSA, they will be using some API approved by
> GNOME/KDE/freedesktop, which will sit happily on top of the more
> complex API that alsa-lib currently provides.
> 
> There are much more important things that ALSA needs to fix, like the
> asoundrc syntax/handling/setup.

i agree also about the PCM.  there are many other PCM abstractions
like PortAudio.  of course, it'd be nice to have one in ALSA itself,
though.

but remember that the mixer is a different story.
there is no other abstraction.  the current mixer representation is
too copmlex and the abstraction itself is not complete.


Takashi


-------------------------------------------------------
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 13:56 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
2004-01-12  8:42       ` Jaroslav Kysela
2004-01-12 12:54         ` Paul Davis
2004-01-12 13:56           ` Takashi Iwai [this message]

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=s5hd69pgtiv.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=lpotter@trolltech.com \
    --cc=paul@linuxaudiosystems.com \
    /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.