[Bug 995169] Re: master output volume doesn't affect actual volume

2020-05-05 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 995169] Re: master output volume doesn't affect actual volume

2020-03-05 Thread Marcus Tomlinson
This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu

[Bug 995169] Re: master output volume doesn't affect actual volume

2013-01-05 Thread Andrew Comminos
Thanks for the fix Jim. Works quite well. I have a Intel Corporation 82801JI (ICH10 Family) HD Audio Controller for the record, and have been experiencing this since Precise. On Quantal now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 995169] Re: master output volume doesn't affect actual volume

2013-01-05 Thread Raymond
does it help if spec-vmaster_nid is changed from DAC1 to DAC0 ? #ifdef CONFIG_SND_HDA_POWER_SAVE spec-loopback.amplist = ad1988_loopbacks; #endif -spec-vmaster_nid = 0x04; +spec-vmaster_nid = 0x03; codec- = 1; codec-no_sticky_stream = 1; -- You

[Bug 995169] Re: master output volume doesn't affect actual volume

2012-07-07 Thread Raymond
may be pulseaudio should not merge/use the virtual master by differientate the virtual master volume/switch control of snd-hda-intel driver from the master volume/switch of ac97 codec (e.g. mono control vs stereo control) -- You received this bug notification because you are a member of Ubuntu

[Bug 995169] Re: master output volume doesn't affect actual volume

2012-07-06 Thread Jim Braux-Zin
Raymond's fix did not work for me. What worked was commenting the sections in /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf and /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf: #[Element Master] #switch = mute #volume = merge #override-map.1 = all

[Bug 995169] Re: master output volume doesn't affect actual volume

2012-07-06 Thread Raymond
does ad1989b need a separte hdmi device 3 instead of sharing device2 with spdif ? (hdmi use 0x0b and spdif use0x02, hp use 0x03 and front use 0x04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 995169] Re: master output volume doesn't affect actual volume

2012-07-05 Thread Raymond
use 6stack or 6stack-dig if you want vmaster include headphone In /etc/modprobe.d/alsa-base.conf options snd-hda-intel model=6stack-dig http://www.intel.com/support/motherboards/desktop/sb/cs-020642.htm#multistream ad1988 and x1989 is a HDA codec with 10 channels DAC which support 7.1 + 2

[Bug 995169] Re: master output volume doesn't affect actual volume

2012-07-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995169 Title:

[Bug 995169] Re: master output volume doesn't affect actual volume

2012-05-13 Thread Harry Skelton
Same problem. No fix seems to help link the Master output to my Headphones or PCM Can control via volume control app, but my volume wheel, which controls the Master volume, does nothing for my headphone output. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 995169] Re: master output volume doesn't affect actual volume

2012-05-05 Thread Greg
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995169 Title: master output volume doesn't affect actual volume To manage notifications about this bug go to: