Every time JuK goes from one track to the next when crossfade is enabled, the master volume in KMix jumps to 100%. Disabling crossfade between tracks is a suitable workaround. Reproducible: Always Steps to Reproduce: 1. Enable crossfade between tracks (Player -> Crossfade Between Tracks) 2. Press the play button 3. If it doesn't happen on initial play, skip to another track. Actual Results: My volume magically jumped to maximum. Also, my heart rate increased drastically at the sudden adrenaline rush caused by the intense volume. Expected Results: It should have left the volume where it was. I have the haskell platform pinned from testing but I'm running stable otherwise. I don't think I'm even running any backports.
Also, I've seen the same behavior in Debian testing on another computer, although it jumps in smaller increments instead of straight to 100%
Combined with bug #350753 (https://bugs.kde.org/show_bug.cgi?id=350753), this is _really_ annoying.
I've tried both steps to reproduce and I can't. What phonon backend are you using? Do you have any applets or other programs that also try to control the media player? For instance there are Plasma applets that use "MPRIS" to interact with Juk, KDE Connect can do the same thing, etc. The behavior you're seeing could be related to that somehow, I suppose... but I can't reproduce it myself. :-/
I have the VLC phonon backend (https://packages.debian.org/jessie/phonon-backend-vlc) installed. I have it because it's what shipped with the debian/kde distro. I don't believe I have any applets or programs that try to control the media player - except, possibly, my browsers. Kwin has volume control, but I think that's expected. I'm pretty sure that the problem still happens when my browsers are closed. I'll double check and post again.
Confirmed. It still happens with closed browsers.
Also, it seems that it never triggers on the _first_ track to play. Skipping to another track or stopping playback and then starting it again causes the problem.
I made a change to the git version of JuK (what will eventually be in 16.08) and realized it might be related to this. The change [1] is to keep Juk and media status monitors (like the default media player control in Plasma) from fighting over the volume. Maybe it would help here? Either way I've still be unable to reproduce. :( [1] https://quickgit.kde.org/?p=juk.git&a=commit&h=3ad38ca68cd3f066d057519c3f134dccf7987590
If you can't reproduce, maybe it's some sort of integration bug - which could concern any number of packages. Have you tried it on a debian system? Running the amd64 architecture? If not, then this hypothesis holds a little more water. In any event, I appreciate that you're continuing to be aware of the issue.
I just noticed similar behavior from something outside of JuK. I got alerts asking for a passphrase. The first happened at a normal volume level; the second alert was at maximum volume. I then launched JuK to see if it would still behave the same. I turned it on, disabled crossfade, started playing a track, stopped playback, and started another. The volume jumped exactly as it has before. This indicates that the problem is unlikely to be in JuK itself but somewhere in the KDE codebase.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!