From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Giuliano Pochini <pochini@shiny.it>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: future ALSA development
Date: Tue, 24 Jun 2003 19:12:56 +0200 [thread overview]
Message-ID: <s5hof0nmmav.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0306241501260.1838-100000@pnote.perex-int.cz>
At Tue, 24 Jun 2003 15:04:22 +0200 (CEST),
Jaroslav wrote:
>
> On Tue, 24 Jun 2003, Giuliano Pochini wrote:
>
> > Lisp should be fine, although it's not very user-friendly. But what the
> > interpreter is supposed to do ? Is it possible to create an ordinary
> > mixer control that the hw doesn't support ? For example: a card may not
> > have an hw master volume control, but the ordinary mixer has to provide
> > it. Is the lisp config file generic enough to provide a function to
> > emulate the master volume control it by changing the volume controls
> > of all single channels ? It's not trivial at all to do such a thing
> > with a "normal" config file, but it's possible with an interpreter. The
> > question is: is it worth the effort ? Or is it better to force all
> > lowlevel drivers to provide a minimal set of ordinary controls ?
>
> I think that it's worth to let define multiple virtual mixer devices for
> multichannel cards (if required) and I can find more examples in this
> area. You cannot do that in the kernel space without adding more code and
> this is exactly what we do not want.
yes, this way is also helpful to solve the problem of "different
speaker configurations", as posted in another thread.
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
next prev parent reply other threads:[~2003-06-24 17:12 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
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 [this message]
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=s5hof0nmmav.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=perex@suse.cz \
--cc=pochini@shiny.it \
/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