Bug 483746 - max volume is really low
Summary: max volume is really low
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-lib
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jaroslav Kysela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 484592 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-03 14:01 UTC by jeremy boyd
Modified: 2010-06-28 11:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 11:11:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jeremy boyd 2009-02-03 14:01:50 UTC
Description of problem: when listening to music or watching video the maximum volume available through the pulse audio mixer is very low. in previous releases there was a pcm option that could be boosted to raise the global volume but that option is missing. i don't think that that option is necessary but it should be boosted by default.


Version-Release number of selected component (if applicable): rawhide ?


How reproducible:always


Steps to Reproduce:
1. open volume control
2.boost volume to 100%
3.
  
Actual results: not much volume


Expected results:


Additional info:

Comment 1 Lennart Poettering 2009-02-12 23:06:51 UTC
Sounds like a mixer initialization issue. Play around with "alsamixer -c0".

Comment 2 Lennart Poettering 2009-02-12 23:07:12 UTC
*** Bug 484592 has been marked as a duplicate of this bug. ***

Comment 3 Lennart Poettering 2009-02-25 03:02:08 UTC
Which hardware is this?

Reassigning to alsa-lib since this is most likely just another iteration of the default mixer initialization issue.

Comment 4 Hedayat Vatankhah 2009-05-03 18:23:53 UTC
I've the same problem with:
│ Card: HDA Intel                                                              │
│ Chip: Analog Devices AD1984

The PCM volume is in the middle.

Comment 5 Bug Zapper 2009-06-09 11:03:00 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Nicolas Troncoso Carrere 2009-06-20 14:47:11 UTC
check https://bugzilla.redhat.com/show_bug.cgi?id=502326 see if it solves your problem

Comment 7 Hedayat Vatankhah 2010-01-07 16:42:15 UTC
For me, it is fixed in Fedora 12. Thanks! :)

Comment 8 Bug Zapper 2010-04-27 12:51:20 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Bug Zapper 2010-06-28 11:11:30 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.