Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: future ALSA development
Date: Mon, 23 Jun 2003 15:51:30 +0200	[thread overview]
Message-ID: <s5hhe6g3nrx.wl@alsa2.suse.de> (raw)
In-Reply-To: <200306231335.PAA10806@alsa.alsa-project.org>

At Mon, 23 Jun 2003 09:41:32 -0400,
Paul Davis wrote:
> 
> >my afraid is that the more control flows like conditionals may lead to
> >a difficulty for a parser utility.  i.e. the parser itself would be
> >like an interprerter.  but it's true that an extesion is needed
> >anyway...
> 
> with a smile, i seem to recall noting that we'd end up with
> lisp. quasimodo had gone through the same song and dance with a custom
> configuration parser only to eventually find that guile made more
> sense in almost every way. there is some adage about reinventing lisp
> that i forget.
 
oh yeah.

btw, what was the biggest reason to change to XML in ardour?
it used guile once upon a time.


> >IMO, the current simple-mixer API is still too complicated and not a
> >good abstraction.  as you mentioned, there is a big gap between the
> >low-level expressions (control API) and the reasonable mixer
> >appearance.  the extra information for the mixer would be needed to
> >fill this gap, too.
> 
> i'd like to put in a plug for a API that includes the one basic 
> operation that JACK cannot implement on "generic" hardware:
> 
> 	  "make the signal coming to the current capture input
> 	   appear at the output".
> 
> i.e. hardware monitoring. this is a really major flaw in JACK when run
> on all consumer audio interfaces: they are quite capable of doing 
> analog-level h/w monitoring, but JACK can't use it.
> 
> i know that the semantics need to be better defined than in my
> sentence above.

this can be implemented better once when we have an ordinary-mixer
API.  the problem was that the action to do is different for each
card, and it's not abstracted (nor unified) so far.
the higher abstraction will absorb such a difference.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

  reply	other threads:[~2003-06-23 13:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 19:10 future ALSA development Jaroslav Kysela
2003-06-23 11:14 ` Takashi Iwai
2003-06-23 12:01   ` Jaroslav Kysela
2003-06-23 13:13     ` Takashi Iwai
2003-06-23 13:41       ` Paul Davis
2003-06-23 13:51         ` Takashi Iwai [this message]
2003-06-23 14:18           ` Paul Davis
2003-06-23 22:22     ` Joern Nettingsmeier
2003-06-24  7:51       ` mru
2003-06-24  8:14       ` Jaroslav Kysela
2003-06-24 11:19         ` Abramo Bagnara
2003-06-24 11:43         ` Paul Davis
2003-06-24 11:56           ` Jaroslav Kysela
2003-06-24 12:16             ` Paul Davis
2003-06-24 17:11               ` Takashi Iwai
2003-06-24 18:28                 ` Jaroslav Kysela
2003-06-25 17:49                   ` PCMCIA In Kernel Or In ALSA Driver? Len Moskowitz
2003-06-25 18:51                     ` Jaroslav Kysela
2003-06-30 10:17                   ` future ALSA development Takashi Iwai
2003-06-24  8:28       ` iriXx
2003-07-03 13:39       ` Kai Vehmanen
2003-07-07 11:26         ` Takashi Iwai
2003-10-01  9:37           ` ALSA in embedded use (was: Re: future ALSA development) Kai Vehmanen
2003-10-01 13:13             ` Takashi Iwai
2003-06-24 12:52   ` future ALSA development Giuliano Pochini
2003-06-24 13:04     ` Jaroslav Kysela
2003-06-24 17:12       ` Takashi Iwai
2003-07-03 14:21 ` Kai Vehmanen
2003-07-03 14:36   ` Kai Vehmanen
2003-07-03 16:05 ` Thomas Charbonnel
2003-07-07 11:37   ` 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=s5hhe6g3nrx.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox