Version: 2.4-GIT (using Devel) OS: Linux When Amarok tries the remote streaming and fails to connect, reproduces the local .mp3 but the volume goes 100%, without modifying the volume bar. It only happens when the remote streaming is the last in the playlist. I must click on the volume gear to have my previous volume. Reproducible: Always Steps to Reproduce: In a playlist with only two items: A local .mp3 file A remote http streaming source rarely reachable.. try to reproduce the remote streaming without success. Actual Results: volume up to 100% Expected Results: same volume as before OS: Linux (x86_64) release 3.1.0-rc9-1-desktop Compiler: gcc-4.6
Which Phonon backend do you use? Could you please try alterantively the phonon-backend-gstreamer or phonon-backend-vlc and see if that changes?
I use phonon-vlc. Can not reproduce with phonon-gstreamer, because when the streamer can not be reproduced, nothing else is reproduced until I press stop and play again, then the local file is played.
After asking in #kde-multimedia, reassigning to the phonon-backend-vlc
what version of phonon, phonon-vlc and vlc? FWIW, I cannot reproduce the issue here.
phonon-vlc 0.4.55 (from git) vlc 1.1.12
Hm, exactly my setup too :/ Please get us a debug log of at least the song before the last song and the last song, up until you change the volume manually. http://techbase.kde.org/Development/Tutorials/Debugging/Phonon#Environment_Variables
Created attachment 65354 [details] The log asked. You can see there how the volume goes (unasked) from 5 to 50 You can see there are three volume changes in the log file. The first from 5 to 5 (no idea) The second from 5 to 50 is the bad one The third from 50 to 5 is done by pressing the volume bar.
I forgot to change the status..
Oh yes, you should totally use PulseAudio.
I am reasonable certain it has to do with amarok reinitalizing phonon but apparently not (re)setting the volume. Phonon defaults to a volume of 1.0 (0db, 100% in amarok) which gets applied by phonon vlc as expected.
Harald: isn't this the same bug as bug 298569?
@Myriam: I guess you pasted the wrong bug number. A bug about ktorrent?
Yes, indeed, sorry for that, I meant bug 296589
*** This bug has been marked as a duplicate of bug 296589 ***