-
Notifications
You must be signed in to change notification settings - Fork 2
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
System master volume reset to 100% after track switch #2
Comments
Hello. Thanks for taking the time to report this issue. I'll take a look at it in August 2015 as funds for July 2015 have been already almost spent. Thanks for your understanding. |
Hello. I need more information to investigate your issue further. What's the output of following command regarding the PulseAudio flat volumes configuration option?
I'm not sure whether I understand your issue correctly.
Is this correct? If yes, what behavior do you expect? I also don't understand your workaround. If you set Rdio volume (the slider in the web interface) to a level that's comfortable for you, why do you need to use also hardware volume knobs?
What do you exactly mean by "the pulseaudio per-application volume" and "the rdio in-app volume"? |
By per-application volume, I mean the Nuvola Player stream volume.
|
I looked into pulseaudio flat-volumes, and set it to |
Exact same issue as tiliado/nuvolaplayer#84 ; I guess this can be closed? |
Actually, it is not a workaround. The behavior you have previously described is completely correct with flat-volumes enabled. The only issue is that you actually don't want that behavior and you have to change your PulseAudio settings accordingly (to disable flat-volumes).
No, that issue was about different volumes of two audio streams. The only similarity is that the flat-volumes feature makes everything worse as it is broken by design. That's why flat-volumes are disabled by default in Ubuntu. I'm closing this issue as the cause was wrong PulseAudio configuration on your system. |
Follow up: tiliado/nuvolaplayer#138 |
Actually, you are right. I didn't read the bug carefully and thought you were talking about tiliado/nuvola-app-spotify#6. |
Flat volumes would have worked if the slider in the web interface updated when the stream volume is changed from outside of the app, however, that's probably trickier to do (tiliado/nuvolaplayer#22 ??). <ramble> I suppose that flat volumes works in windows because they probably introduced a new api to control the flat volume, whereas pulse made the change while still using the same api, so apps that didn't expect to control the global volume ended up changing the global volume. </ramble> |
Rdio does not update their volume slider when the stream's volume changes, since most platforms cannot change the volume externally. With pulseaudio and gtkwebkit, the volume can be changed externally, so this will update the slider position when the stream volume is changed by pulseaudio. Implementation notes: Accesses internal Rdio app data, so this may break in the future. If this stops working, it will safely degrade and not affect the rest of the integration. - Reviewed by: Jiří Janoušek <[email protected]> - Reviewed by: Aaron Cripps <[email protected]> - Issue: #2 - Pull Request: #3
System master volume reset to 100% after track switch. KDE Plasma 5 desktop, IIRC, it also happened on KDE4. Manjaro linux (Arch-based), KMix, pulseaudio.
I've had this issue for a while, crossing my fingers that it would eventually go away.
I'm not sure if this is a Rdio-specific issue, but I figured it should go here first.
My current workaround is to lower the volume within rdio, and use the physical volume knob on my headphones and speakers.
Additionally, the volume slider within rdio sets the pulseaudio per-application volume level as well, which makes it tough to precisely control the volume (since it's like
y=x^2
instead of justy=x
). On track switch, the rdio in-app volume is also reset to the pulseaudio per-application volume, if it has been changed to anything different. This could be a separate issue, but they're probably linked.The text was updated successfully, but these errors were encountered: