Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: [RFC] virtual master control for HD-audio
Date: Sat, 22 Dec 2007 12:39:55 +0500	[thread overview]
Message-ID: <fkif0k$adr$1@ger.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0712212030470.8567@tm8103.perex-int.cz>

Jaroslav Kysela wrote:
> On Thu, 20 Dec 2007, Takashi Iwai wrote:
> 
>> Hi,
>>
>> another thing I'd like to push into the next kernel is the virtual
>> master volume control.  As I posted in earlier posts, it adds virtual
>> controls that have several slave controls with the same types,
>> e.g. Front, Surround, Center, LFE, etc.  Then these are adjusted
>> simultaneously via the master control.
>>
>> It'd be appreciated if some one can test the patches with HD-audio h/w
>> that has no master control yet (e.g. some STAC codecs).
>>
>> Note that this won't add the master volumes if there are no real
>> volume controls.  Some codecs have really no volume control, and this
>> won't help for such devices.
>>
>> Two (and one for driver) patches will follow after this.
> 
> NAK from my side. I am convinced that this code can be implemented in the 
> user space even without any daemon just in the mixer abstract layer using 
> standard control elements and using eventually new user controls to store 
> data for virtual mixer controls.

Aren't the patches supposed to be useful also for OSS-only apps, where userspace 
solutions can't work without LD_PRELOAD hacks? Currently, without the patch and 
the "aoss" wrapper, OSS apps sound too loud. I have not tested the patch, but I 
am too lazy to change each .desktop file for each OSS-only application provided 
by the distribution.

-- 
Alexander E. Patrakov

  reply	other threads:[~2007-12-22  7:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 15:38 [RFC] virtual master control for HD-audio Takashi Iwai
2007-12-20 15:45 ` [RFC] [Patch 1/2] Add virtual master control Takashi Iwai
2008-01-30 15:19   ` Daniel Jacobowitz
2008-01-30 15:27     ` Takashi Iwai
2008-03-21 19:08       ` Daniel Jacobowitz
2008-03-22  9:09         ` Takashi Iwai
2008-03-22 15:30           ` Daniel Jacobowitz
2008-03-22 16:31             ` Takashi Iwai
2008-03-22 19:15               ` Daniel Jacobowitz
2008-05-02 18:01                 ` Daniel Jacobowitz
2008-05-06 15:17                   ` Takashi Iwai
2008-05-06 15:45                     ` Daniel Jacobowitz
2007-12-20 15:46 ` [RFC] [Patch 2/2] Add virtual master to HD-audio Takashi Iwai
2008-01-12 20:21   ` Daniel Jacobowitz
2008-01-13 11:04     ` Takashi Iwai
2007-12-20 15:48 ` [RFC] [Patch] Add vmaster to alsa-driver Takashi Iwai
2007-12-20 15:50 ` [RFC] virtual master control for HD-audio Takashi Iwai
2007-12-21 19:37 ` Jaroslav Kysela
2007-12-22  7:39   ` Alexander E. Patrakov [this message]
2007-12-23  3:15     ` Lee Revell
2007-12-22 14:55   ` Takashi Iwai
2008-01-09 17:06     ` Takashi Iwai
2008-01-10 10:29     ` Jaroslav Kysela
2008-01-10 11:49       ` Takashi Iwai
2008-01-10 14:09         ` Jaroslav Kysela
2008-01-10 15:00           ` Takashi Iwai
2008-01-10 15:43             ` Jaroslav Kysela
2008-01-10 15:47               ` 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='fkif0k$adr$1@ger.gmane.org' \
    --to=patrakov@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /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