From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0000429]: Feature: Ability to cap the volume
Date: Mon, 2 Jan 2006 20:12:23 +0100 [thread overview]
Message-ID: <f2316dc714165a92c69ea9d9b01b4814@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=429>
======================================================================
Reported By: morgoth
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 429
Category: alsamixer
Reproducibility: always
Severity: feature
Priority: normal
Status: new
======================================================================
Date Submitted: 08-07-2004 23:39 CEST
Last Modified: 01-02-2006 20:12 CET
======================================================================
Summary: Feature: Ability to cap the volume
Description:
For my soundcard (SB Live! 1024) I can't have the PCM higher then 74%
before I get some werd noises. If there was a way to cap or lock the
volume so that _no_ programs (like xmms or mplayer) could turn it higher.
That would be great :)
I don't know why all programs try to adjust the PCM instead of Master or
any of the others. But a cap would be a start ;)
======================================================================
----------------------------------------------------------------------
pzad - 01-02-06 20:01
----------------------------------------------------------------------
Audigy 2 ZS has diffrent mixer and signal routing.
On sb live
PCM on 75 % should be 0 db
PCM on 100 % is +12 db
----------------------------------------------------------------------
rlrevell - 01-02-06 20:12
----------------------------------------------------------------------
Ah ok. Well jcdutton's work to make alsa mixer use DB values might help.
Then it would be up to the app to not do silly things like play back .wav
files with the gain to +12 DB.
pzad, what do you think the status of this bug should be?
Issue History
Date Modified Username Field Change
======================================================================
08-07-04 23:39 morgoth New Issue
08-08-04 19:41 afran Issue Monitored: afran
08-08-04 19:52 afran Note Added: 0001545
12-31-05 07:26 rlrevell Note Added: 0007350
01-02-06 19:36 afran Note Added: 0007377
01-02-06 20:01 pzad Note Added: 0007378
01-02-06 20:12 rlrevell Note Added: 0007379
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-02 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 19:12 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-02 19:40 [ALSA - utils 0000429]: Feature: Ability to cap the volume bugtrack
2006-01-02 19:01 bugtrack
2006-01-02 18:36 bugtrack
2005-12-31 6:26 bugtrack
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=f2316dc714165a92c69ea9d9b01b4814@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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