You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I seem to be encountering a weird bug where spotify ads will crank my system and the spotify ad playback stream to 100%. However the stream where the music is coming from spotify and any other streams will stay at the same volume.
This is fairly serious as it could probably cause ear damage to anyone wearing headphones that go to some silly volume. It was incredibly uncomfortable for me.
It seems to be happening on both Nuvola Player 2 and the latest commit of Nuvola Player 3.
I'm using Arch Linux with Gnome-shell.
The text was updated successfully, but these errors were encountered:
Thanks for taking the time to report this issue. Note that Nuvola Player is not officially supported on Arch Linux, so my ability to help you with your issue may be limited. I need more information to investigate it further:
What volume is set in the Spotify web interface for the music stream?
The volume for the spotify interface is 100%
The pulseaudio volume is normally around 30%
And flat-volume is commented out in my daemon.conf, Going to uncomment it and see how it goes.
Thanks for the help 👍
Update: commented out flat-volume seems to have been the culprit here, I have had a couple of ads now and they have all stayed at the same volume that every other audio stream is at.
I seem to be encountering a weird bug where spotify ads will crank my system and the spotify ad playback stream to 100%. However the stream where the music is coming from spotify and any other streams will stay at the same volume.
This is fairly serious as it could probably cause ear damage to anyone wearing headphones that go to some silly volume. It was incredibly uncomfortable for me.
It seems to be happening on both Nuvola Player 2 and the latest commit of Nuvola Player 3.
I'm using Arch Linux with Gnome-shell.
The text was updated successfully, but these errors were encountered: