-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Labels
Description
mpv Information
mpv v0.40.0-dirty Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
built on Oct 4 2025 16:40:45
libplacebo version: v7.351.0
FFmpeg version: n8.0
FFmpeg library versions:
libavcodec 62.11.100
libavdevice 62.1.100
libavfilter 11.4.100
libavformat 62.3.100
libavutil 60.8.100
libswresample 6.1.100
libswscale 9.1.100Other Information
- Linux version: Arch Linux
- Kernel Version: Linux loq15iax9 6.17.5-arch1-1.1 #1 SMP PREEMPT_DYNAMIC Sat, 25 Oct 2025 04:05:25 +0000 x86_64 GNU/Linux
- GPU Model:
00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-S [UHD Graphics] [8086:468b] (rev 0c)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / Mobile] [10de:28e1] (rev a1)
- Mesa/GPU Driver Version: `OpenGL version string: 4.6.0 NVIDIA 580.95.05`
- Window Manager and Version: Hyprland 0.51.1
- Source of mpv: form Arch's repo `sudo pacman -S mpv`
- Latest known working version: N/A
- Issue started after the following happened: N/A
Reproduction Steps
- Have a spotify package from arch official repo:
spotify-launcher 0.6.3-2.1 - Change the volume level via spotify's volume knob or pavucontrol (let's say set it to 40%)
- Open an audio file (not a video) with mpv
Expected Behavior
mpv should have an independent volume from spotify (spotify at 40%, mpv at 100%).
Actual Behavior
mpv's volume is lowered to 40%
If you change it back to 100% through pavucontrol, it stays that way until you adjust spotify’s volume again and reopen the mpv audio file.
Log File
Sample Files
I have a video demonstration
mpv_spotify_issue.mp4
I carefully read all instruction and confirm that I did the following:
- I tested with the latest mpv version to validate that the issue is not already fixed.
- I provided all required information including system and mpv version.
- I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of
--log-file=output.txt. - I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
- I attached the full, untruncated log file.
- I attached the backtrace in the case of a crash.