From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Ove Kaaven <ovek@transgaming.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: PCM hw mixing with volume
Date: Wed, 10 Mar 2004 18:47:13 +0000 [thread overview]
Message-ID: <404F62B1.30206@superbug.demon.co.uk> (raw)
In-Reply-To: <1078928193.18054.247.camel@renegade>
Ove Kaaven wrote:
>
>
> Well, the requirements that raised this thread should be fairly clear.
> For example,
>
> ALTERNATIVE 1
>
> snd_pcm_set_volume(snd_pcm_t* pcm, int volume)
>
> and
>
> snd_pcm_set_pan(snd_pcm_t* pcm, int pan)
>
> using whatever value range makes the most sense, and perhaps some query
> on whether these controls are available from the pcm info. It's
> acceptable to have to explicitly ask for these controls using hw_params.
> The plug plugin could insert the route/volume plugin if these controls
> are asked for.
>
> ALTERNATIVE 2
>
> snd_pcm_set_volume(snd_pcm_t* pcm, int vol_left, int vol_right)
>
> but I don't expect this to be useful, since there are probably some
> oddball devices out there that aren't able to control left and right
> volume independently like this.
>
> ALTERNATIVE 3
>
> Let each PCM channel have its own mixer control, like the EMU10K1
> currently do. That is, use snd_pcm_info_get_subdevice() to get the
> index, then look up a volume control with a well-known name and the
> given index using the snd_ctl API to control the volume of that PCM
> stream. The name and semantics of that mixer control would have to be
> standardized and be the same on all devices that are capable of this
> feature.
>
What about 7.1 surround sound channels. All your suggestions only assume
2 PCM channels.
Although it might seem nice to add this to alsa, it is not exactly a
difficult task for the application to do itself.
I suggested exactly what you suggested some time ago (see alsa-devel
archives), but recently I have realised that there is little or no point.
The application will contain a user interface control for the volume, so
one might as well adjust the volume in software as well. It is not even
very CPU intensive.
Cheers
James
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-10 18:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 14:51 PCM hw mixing with volume Ove Kaaven
2004-03-07 16:36 ` Manuel Jander
2004-03-07 16:41 ` Jaroslav Kysela
2004-03-08 16:20 ` Paul Davis
2004-03-08 21:29 ` Ove Kaaven
2004-03-09 14:26 ` Paul Davis
2004-03-09 14:59 ` Takashi Iwai
2004-03-09 17:31 ` USB audio devices Jaroslav Kysela
2004-03-10 8:26 ` Clemens Ladisch
2004-03-10 9:08 ` Jaroslav Kysela
2004-03-10 9:41 ` Takashi Iwai
2004-03-10 20:04 ` Karsten Wiese
2004-03-11 0:13 ` Patrick Shirkey
2004-03-11 8:09 ` Clemens Ladisch
2004-03-10 9:41 ` Clemens Ladisch
2004-03-10 16:34 ` Takashi Iwai
2004-03-10 17:46 ` Clemens Ladisch
2004-03-11 8:14 ` Clemens Ladisch
2004-03-09 17:25 ` PCM hw mixing with volume Ove Kaaven
2004-03-09 20:24 ` Manuel Jander
2004-03-10 9:46 ` Giuliano Pochini
2004-03-10 14:16 ` Ove Kaaven
2004-03-10 14:40 ` Ove Kaaven
2004-03-10 14:53 ` Paul Davis
2004-03-10 15:08 ` Takashi Iwai
2004-03-10 16:05 ` Ove Kaaven
2004-03-10 15:55 ` Giuliano Pochini
2004-03-10 16:56 ` Ove Kaaven
2004-03-11 9:24 ` Giuliano Pochini
2004-03-10 17:28 ` Takashi Iwai
2004-03-10 18:47 ` James Courtier-Dutton [this message]
2004-03-11 5:15 ` Manuel Jander
2004-03-11 7:13 ` snd_intel8x0 fails after ACPI sleep gte654n
2004-03-13 18:13 ` Christoph Lukas
2004-03-11 5:00 ` PCM hw mixing with volume Manuel Jander
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=404F62B1.30206@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ovek@transgaming.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