All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Ingo Müller" <alsa@ingomueller.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Ideas for the softvol plugin
Date: Thu, 11 Jan 2007 10:05:55 -0500	[thread overview]
Message-ID: <20070111150555.GA17015@nevyn.them.org> (raw)
In-Reply-To: <45A64FBF.5070503@ingomueller.net>

On Thu, Jan 11, 2007 at 03:54:55PM +0100, Ingo Müller wrote:
> Hi!
> 
> I have some ideas about features that could be added to the softvol
> plugin, that I want to discuss with you.
> 
> 1) A mute/unmute function. I think this is the most easy job.

I've got code for this lying around somewhere, though I'm not sure
where.  But...

> All the three suggestions aim to solve one frequent problem (it occured
> with EVERY sound card I ever had (~5) and forums are full of them): The
> volume control elements don't control the volume like they are supposed
> to. E.g. I've seen so many people whose Master control only affects the
> volume of the front channels. With the above changes, one could just
> rebuild a software based volume control system without having to worry
> whether the hardware controls are supported or not.

Take a look at the "ganged volume" patch I posted to this list, at the
beginning of the month.  In general, when the kernel master volume
only controls the front channels, that's because it's how the card's
control registers work; ganged volume lets you add a kernel control
that moves things up and down in sync.  It's a bit better than using
softvol, because you don't have to do any processing of the samples
as they pass through.

It's to solve exactly what you're describing.

You have to adjust the kernel drivers to set it up properly, but
after messing around with softvol for a while, I think that's best.
It's not hard to do.

-- 
Daniel Jacobowitz
CodeSourcery

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2007-01-11 15:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-10  4:48 usbmidi reconnect -> kernel oops Dmitry Baikov
2007-01-10 22:06 ` Dmitry Baikov
2007-01-11 14:54   ` Ideas for the softvol plugin Ingo Müller
2007-01-11 15:05     ` Daniel Jacobowitz [this message]
2007-01-11 22:45       ` Ingo Müller
2007-01-11 23:03     ` Tom Horsley
2007-01-12 16:11       ` Ingo Müller
2007-01-12 18:18     ` Takashi Iwai
2007-01-12 18:31       ` Ingo Müller

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=20070111150555.GA17015@nevyn.them.org \
    --to=drow@false.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa@ingomueller.net \
    /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.