mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-10-29 05:40:27 -04:00
acp: add api.alsa.disable-mixer-path
Don't use the api.alsa.soft-mixer option to disable the path selection but make a new api.alsa.disable-mixer-path. Disabling the path selection might leave cards unusable after suspend, so a separate option is a better idea. See #4311
This commit is contained in:
parent
e9c5ca5978
commit
99c23d5b0e
3 changed files with 20 additions and 6 deletions
|
|
@ -668,8 +668,19 @@ This option does nothing if `api.alsa.use-acp` is set to `false`.
|
|||
@PAR@ device-prop api.alsa.soft-mixer = false # boolean
|
||||
Setting this option to `true` will disable the hardware mixer for volume
|
||||
control and mute. All volume handling will then use software volume and mute,
|
||||
leaving the hardware mixer untouched. The hardware mixer will still be used
|
||||
to mute unused audio paths in the device.
|
||||
leaving the hardware mixer untouched. This can be interesting to work around
|
||||
bugs in the mixer detection or decibel reporting. The hardware mixer will still
|
||||
be used to mute unused audio paths in the device. Use `api.alsa.disable-mixer-path`
|
||||
to also disable mixer path selection.
|
||||
|
||||
@PAR@ device-prop api.alsa.disable-mixer-path = false # boolean
|
||||
Setting this option to `true` will disable the hardware mixer path selection.
|
||||
The hardware mixer path is the configuration of the mixer depending on the
|
||||
jacks that are inserted in the card. If this is disabled, you will have to
|
||||
manually enable and disable mixer controls but it can be used to work around
|
||||
bugs in the mixer. The hardware mixer will still be used for
|
||||
volume and mute. Use `api.alsa.soft-mixer` to also disable hardware volume
|
||||
and mute.
|
||||
|
||||
@PAR@ device-prop api.alsa.ignore-dB = false # boolean
|
||||
Setting this option to `true` will ignore the decibel setting configured by
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue