All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Problem with multiopen on SB Audigy 2
Date: Thu, 09 Oct 2003 02:14:10 +0100	[thread overview]
Message-ID: <3F84B662.4080502@superbug.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.53.0310081819520.1357@pnote.perex-int.cz>

Jaroslav Kysela wrote:
>>
>>the template i meant above is the basic designs of control naming, and
>>i don't mean that this is the kernel issue.  (well, in the case of
>>"master" volume, we cannot handle it simply by abstraction but need a
>>new control, though.)
>>
>>i believe it's just a question which is easier to implement.
>>i agree that almost all cases can be solved by a higher abstraction,
>>and i prefer that, too.
> 
> 
> Yes, I think that we might use the kernel to create the "user defined"
> controls which can be created from the user space. In this case, we can
> nicely do all kinds of abstractions in the user space.
> 
> 						Jaroslav
> 

I agree, that the less work done in kernel space the better.
I also think it is a good idea to have user space creating virtual 
controls (abstractions), but of course, the values/state given to these 
virtual controls has to be stored somewhere, and kernel space will 
probably have to store them, otherwise their state will not survive 
across application stop/start.

How would one start supporting some of the multichannel features 
availiable on some cards. E.g. surround sound 7.1 (8 channels)

I think we should take the names for the speakers from the AC3 or DTS 
specifications.
AC3 names: -
Left
Center
Right
Left Surround
Right Surround
Low Frequency Effects.

DTS names: -
Left
Center Left
Center
Center Right
Right
Surround Left1
Surround Right1
Surround Left2
Surround Right2
Rear Left
Rear Center
Rear Right
Overhead
Low Frequency Effects.

We would also need to add: -
Headphones

So, I conclude from this, that maybe we should add to the config files a 
way for the user to say what is plugged into what, and name it themselves.

Cheers
James




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

  reply	other threads:[~2003-10-09  1:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 17:00 Problem with multiopen on SB Audigy 2 James Courtier-Dutton
2003-10-07 17:08 ` Takashi Iwai
2003-10-07 22:16   ` James Courtier-Dutton
2003-10-08 11:08     ` Jaroslav Kysela
2003-10-08 13:42       ` Takashi Iwai
2003-10-08 13:49         ` Jaroslav Kysela
2003-10-08 14:05           ` Takashi Iwai
2003-10-08 14:24             ` Jaroslav Kysela
2003-10-08 14:39               ` Takashi Iwai
2003-10-08 14:44                 ` Jaroslav Kysela
2003-10-08 15:00                   ` Takashi Iwai
2003-10-08 15:44                     ` Jaroslav Kysela
2003-10-08 15:58                       ` Takashi Iwai
2003-10-08 16:27                         ` Jaroslav Kysela
2003-10-09  1:14                           ` James Courtier-Dutton [this message]
2003-10-09 13:13                             ` Jaroslav Kysela
2003-10-08 22:36           ` Problem with multiopen on SB Audigy 2 / Mixer setting James Courtier-Dutton
2003-10-07 18:02 ` Problem with multiopen on SB Audigy 2 Jaroslav Kysela
2003-10-09  6:52 p z oooo
2003-10-09 13:26 ` 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=3F84B662.4080502@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=perex@suse.cz \
    --cc=tiwai@suse.de \
    /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.