Stopping a track via tray icon and playing it again starts at 0% volume

[GoogleCodeExporter]

Which version of Cantata?
1.4.0

Which build? KDE, Qt4, Qt5, Windows, Ubuntu, Mac?
KDE

What steps will reproduce the problem?
1. Enable Cantata systray icon
2. Play a song, right-click the Cantata tray icon and press stop
3. After stopping, select the song you just stopped, click on Cantata icon to 
display main GUI and press on the playback button. Track will start at 0% 
volume.

Please provide any additional information below.

Track will also start at 0% if you Stop and Play/Pause again.

Original issue reported on code.google.com by allen...@gmail.com on 17 Aug 2014 at 6:10

[GoogleCodeExporter]

Can't seem to recreate this. I'm assuming you have 'fade when stop' enabled? IF 
so, when you press stop - Cantata does not stop straight away, but lowers the 
volume bit by bit, and then stops. After the stop the volume should be 
restored. If you use another MPD client simultaneously, then you should see the 
real volume in that client.

How quickly are you pressing the play after the stop? Whilst the fade is 
happening, or before the fade ends (and before the song actually stops)?

Also, please run Cantata from the commandline as follows:

CANTATA_DEBUG=1 cantata

Then recreate the issue - and quit cantata. There should now be a log file 
~/.cache/cantata/cantata.log - please upload this somewhere and add a link to 
its location in this bug report.

Original comment by craig.p....@gmail.com on 18 Aug 2014 at 11:12

[GoogleCodeExporter]

I don't recall enabling it... not even sure where is the option. But yea, it 
does fade to stop. 

I used ncmpc to see what happens after I play stop. The volume will drop 
rapidly (also shown in the logs in the setvol), once dropped it won't restore 
back to its original value. I waited like 10-15 seconds, maybe, I was looking 
for the next track to play so it took a while to notice. After I noticed I did 
a few stop/plays and the behavior didn't really change.

Link to log: https://dl.dropboxusercontent.com/u/37705/cantata/cantata.log 

Original comment by allen...@gmail.com on 18 Aug 2014 at 11:45

[GoogleCodeExporter]

Looking at the log, it *does* attempt to restore the volume:

2014-08-18 07:28:00 - MPDConnection 139684416059136 0x10183c0 sendCommand: 
"setvol "95"" false true 
2014-08-18 07:28:00 - MPDConnection 139684416059136 Timeout (ms): 2000 
2014-08-18 07:28:00 - MPDConnection 139684416059136 Socket state after write: 3 
2014-08-18 07:28:00 - MPDConnection 139684416059136 0x10183c0 Waiting for read 
data, attempt 0 
2014-08-18 07:28:00 - MPDConnection 139684416059136 0x10183c0 Read: "ACK [52@0] 
{setvol} problems setting volume
" , socket state: 3 
2014-08-18 07:28:00 - MPDConnection 139684416059136 "setvol "95"" failed 

Why would your MPD not like the volume being set whilst it is NOT playing? 
Using another client (ncmpc, gmpc, etc) can you alter the volume whilst not 
playing? Can you manually alter the volume in Cantata whilst not playing? (Use 
another client to verify changes are being made...)

Original comment by craig.p....@gmail.com on 18 Aug 2014 at 12:12

[GoogleCodeExporter]

I have no idea why MPD doesn't want to set the volume... I used MPC for the 
sake of simplicity:

# david at debianbox in ~ [10:06:11]
$ mpc stop     
volume: n/a   repeat: off   random: on    single: off   consume: off

# david at debianbox in ~ [10:06:16]
$ mpc volume 50
error: problems setting volume

So I looked into MPD verbose: 

client: [10] opened from [::1]:49186
client: [10] process command "setvol "20""
client: [10] command returned 2
^ returns 2 if you try to set volume while no song is playing, else if it's 
playing it will setvol to anything and return 0

Weird thing is that I'm using 0.18.11 and the newest stable is 0.18.12... looks 
like I've hit a bug within MPD itself and not the clients. 

I'll hit up mpd-devel mailing list, hopefully they won't bite. 

Original comment by allen...@gmail.com on 18 Aug 2014 at 2:18

[GoogleCodeExporter]

Just wanted to say that if you could please close the bug. I tried with just 
ALSA and setting the volume works as expected. It seems to be an issue with 
PulseAudio, hopefully the mpd folks will be able to aid me in this tiny issue. 

Original comment by allen...@gmail.com on 19 Aug 2014 at 1:38

[GoogleCodeExporter]

OK, no probs. Thanks for getting back.

Original comment by craig.p....@gmail.com on 20 Aug 2014 at 6:36

• Changed state: Invalid