Skip to content

With "ao=pipewire" changing ao-volume doesn't match mixer reported value #11065

@xkero

Description

@xkero

Important Information
mpv version: 0.35.0
Linux Distribution and Version: Archlinux
Source of the mpv binary: Archlinux community repo
pipewire version: 0.3.63

input.conf:

9 add ao-volume -2
0 add ao-volume +2
/ add ao-volume -2
* add ao-volume +2

So 0% and 100% match, but values in-between don't. So setting volume to 2% in mpv via ao-volume (using hotkeys defined in input.conf) results in the volume showing as 27% in both pavucontrol and kde's volume mixer, 12% in mpv is 50% in both mixers, 74% in mpv is 91% in both mixers, etc. Setting --ao=pulse fixes this, so e.g. 50% in mpv is 50% in the mixer. I looked through the man page for mpv thinking maybe there was some setting for how volume is scaled maybe, but couldn't find anything. If it isn't a bug I find it weird that pulseaudio is fine, but pipewire is different.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions