-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When setting volume on one player in multi-mpd setup, others apply the change for the next song #2113
Comments
Your MPD version is too old and unsupported. |
I'm sorry, does that mean that only 23.15 is supported, or is there an even newer version? Would you mind pointing out if you expect the reported behaviour to be fixed in 23.15, which isn't even packaged in the latest major Linux distributions? |
Only 0.23.15 and git master is supported. I will not even look further if I see an older version in a support request, because it's not worth anybody's time. |
Fair enough. I've downloaded https://www.musicpd.org/download/mpd/0.23/mpd-0.23.15.tar.xz and built it per the user guide. The issue remains the same. Cloned and built git master, this is
Issue remains. Is it fine to reopen, or do you prefer a new issue report? |
Tell me how you believe MPD applies the volume, and then convince me that this isn't PulseAudio interfering. |
When scanning the code some time back, I've seen mpd reading back the current volume of the mixer in some of the control paths, might have been the hardware mixer control path, which might be passed at the time of "play" command if I understood the code correctly. I don't recall the code location for this. I've suspected pulseaudio interfering, too, extended my test setup:
That said, I can't convince you :) - it seems pulseaudio interfering. Issue remains for all mixer parameters (software, hardware, null, none). Do you understand what's happening and can you give a hint about it? Any chance to address this behaviour in mpd? If anybody launches two mpd instances on two soundcards on pulseaudio on a Desktop PC, they'd both interfere there, too, so it's not a nonsense usecase imho... |
Bug report
Describe the bug
I'm running multiple mpd instances in a Ubuntu Jammy (22.04) docker container environment (mpd 0.23.5) under a single user ID:
Each satellite instance has one own pulseaudio null sink and one own HTTP vorbis steam audio output.
When setting volume on one satellite instance (ex.
mpc -p 6601 volume 20
) while another instance is playing a playlist, the other instances applies the changed volume when switching to the next track (either when reaching end of a song in the queue, or withmpc -p 6604 next
).Expected Behavior
Volume settings are not interfering: Each player instance keeps own volume setting.
Actual Behavior
When setting volume on one satellite instance (ex.
mpc -p 6601 volume 20
), other instances apply the changed volume when switching to the next track (either when reaching end of a song in the queue, or withmpc -p 6604 next
).The issue has been reproduced in an isolated environment with the local mpc command line client only, no external client (smartphone etc.) could interfere. Test with mpd 23.14 on Ubuntu Noble (24.04) shows the same behaviour.
Version
Configuration
Four satellites with below configuration (increase suffix 1 up to 4):
Two proxy instances on port 7601 for two separate music databases:
Log
There are no related logs in mpd instances that apply volume unintentionally. If special logs required, kindly advise on how to get them.
The text was updated successfully, but these errors were encountered: