From: "Ingo Müller" <alsa@ingomueller.net>
To: alsa-devel@lists.sourceforge.net
Subject: Ideas for the softvol plugin
Date: Thu, 11 Jan 2007 15:54:55 +0100 [thread overview]
Message-ID: <45A64FBF.5070503@ingomueller.net> (raw)
In-Reply-To: <70a871c80701101406y3f8293e9sd57b1d4c5ba9b166@mail.gmail.com>
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.
2) Ability to replace an existing control. I have no idea whether it is
possible to realize this, but this would be very usefull (see below).
3) Multi channel capabilities. This is just a vague idea. The aim is to
be able to control e.g. front, rear and center/lfe channels seperately
from each other. Maybe like this:
pcm.softvol {
type softvol
slave {
pcm "hw:0,1"
}
controls [
{
name "SoftFront"
affects [ 0 1 ]
}
{
name "SoftRear"
affects [ 2 3 ]
}
{
name "SoftCenterLfe"
affects [ 4 5 ]
}
]
}
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.
Right now, one can create a softvol device, create a control named
"Softmaster" and make every application use this device. AFAIK, there's
is no mute function. I don't need to explain why this would be usefull.
What can't be done is name this control "Master" (unless this control
doesn't exist yet). Many media applications have a function to control
the volume, but most of them just control the master volume, so ones
"Softmaster" would not be touched by them.
Well the multichannel capabilities are not that important. It's just an
idea, like I said. With some cards, I was able to realize the same
functionality with softvol in combination with the multi plugin, on
other I wasn't. I just think that this would be the cleanest way to do it.
Finally, I wanted to mention, that I am not a developper of any sort,
but as I user, I am always trying to improve things (see my work on the
alsa wiki). I hope some of you think about my suggestions anyway!
Greets, Ingo
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-01-11 14:54 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 ` Ingo Müller [this message]
2007-01-11 15:05 ` Ideas for the softvol plugin Daniel Jacobowitz
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=45A64FBF.5070503@ingomueller.net \
--to=alsa@ingomueller.net \
--cc=alsa-devel@lists.sourceforge.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.