* Low volume with chtmax98090 (Toshiba Chromebook 2/Swanky)
[not found] <1597033583603136063-webhooks-bot@alsa-project.org>
@ 2020-08-10 4:26 ` GitHub issues - opened
0 siblings, 0 replies; 2+ messages in thread
From: GitHub issues - opened @ 2020-08-10 4:26 UTC (permalink / raw)
To: alsa-devel
alsa-project/alsa-ucm-conf issue #45 was opened from reanimus:
It looks like the UCM configuration for this board is the Chromebook Asus C300 one, but the volume levels set by default are far too low. It looks like when Pulseaudio loads on my system, it follows the initialization steps and results in a really low volume, as the Speaker is set to 27/100 and one must manually set the alsamixer levels to fix it. I could have a periodic task reload the volume state, but I find it better to override the UCM configuration manually and tell my package manager to ignore changes to that file during upgrade.
Naturally, this is a bit of a nasty solution. It'd be nice to have an upstream fix in case other stuff is changed for this.
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/45
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
^ permalink raw reply [flat|nested] 2+ messages in thread
* Low volume with chtmax98090 (Toshiba Chromebook 2/Swanky)
[not found] <1597034008999078035-webhooks-bot@alsa-project.org>
@ 2020-08-10 4:33 ` GitHub issues - edited
0 siblings, 0 replies; 2+ messages in thread
From: GitHub issues - edited @ 2020-08-10 4:33 UTC (permalink / raw)
To: alsa-devel
alsa-project/alsa-ucm-conf issue #45 was edited from reanimus:
It looks like the UCM configuration for this board is the Chromebook Asus C300 one, but the volume levels set by default are far too low. It looks like when Pulseaudio loads on my system, it follows the initialization steps and results in a really low volume, as the Speaker is set to 27/100 and one must manually set the alsamixer levels to fix it. I could have a periodic task reload the volume state, but I find it better to override the UCM configuration manually and tell my package manager to ignore changes to that file during upgrade.
FWIW, my fix is to modify ucm2/codecs/max98090/EnableSeq.conf and change
```
cset "name='Headphone Volume' 10"
cset "name='Speaker Volume' 10"
```
to
```
cset "name='Headphone Volume' 80%"
cset "name='Speaker Volume' 80%"
```
Naturally, this is a bit of a nasty solution. It'd be nice to have an upstream fix in case other stuff is changed for this.
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/45
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-08-10 4:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <1597033583603136063-webhooks-bot@alsa-project.org>
2020-08-10 4:26 ` Low volume with chtmax98090 (Toshiba Chromebook 2/Swanky) GitHub issues - opened
[not found] <1597034008999078035-webhooks-bot@alsa-project.org>
2020-08-10 4:33 ` GitHub issues - edited
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).