Bugzilla – Bug 7067
not returning mute/volume when state changes
Last modified: 2009-07-31 10:16:57 UTC
In cases where the player has been muted any action which would either cause the current song to change or the current song to go from being stopped or paused to playing causes the mute to be turned off (unmuted). There is no reporting of this through either prefset or through <ID> mixer mute .... First of all should the player unmute just because a song changed? I realize I do have the option for pause which will effectively mute the player and not allow a song to change, so perhaps this is a good thing. As a minimum when the mute state changes it should be reported back to the client via CLI. I would expect to see a prefset and a mixer mute notification, but prefset would be adequate
I'm no cli expert, and admittedly I'm being lazy by not looking it up, but is there a notification through the volume comand/pref somewhere? Internally, mute is just the negative of the current volume level. Thus, going back to unmuted should be giving a volume change.
I agree it should, but it does not. here is a trace from my client system. It should be easy to understand 1 SEND: bb:2c:be:ca:da:1d mixer muting 1 2 RCVD: <ID> mixer muting 1 3 RCVD: <ID> prefset server mute 1 4 RCVD: <ID> prefset server volume 0 5 RCVD: <ID> prefset server volume -75 6 RCVD: <ID> playlist open file%3A%2F%2F%2FD%3A%2FMy%2520Documents%2FMy%2520Music%2FChick%2520Corea 7 RCVD: <ID> playlist newsong 4.%20Sophisticated%20Lady 1 1 shows the client sending a mute command. 2-5 shows the result of that muste time passes with the system not audible (muted) 6,7 shows the next song starting no further notifcations of volume change are received, however the music is playing loud and clear. I can fix/compensate for it in my code, but I feel it is wrong. Knowing how you guys like things RIGHT, I am just calling it to your attention
Thanks, Barry. We'll look at this post 7.0.
Also note the superfluous return of a prefset with a volume of 0. It seems as if when you pass through 0 as you un-mute you report that too.
Barry - I do see the muting being returned from the CLI: 00%3A04%3A20%3A10%3A01%3A82 mixer muting 1 00%3A04%3A20%3A10%3A01%3A82 mixer muting Works for me. Please upload debug info from SC.
(In reply to comment #5) > Barry - I do see the muting being returned from the CLI: > > 00%3A04%3A20%3A10%3A01%3A82 mixer muting 1 > 00%3A04%3A20%3A10%3A01%3A82 mixer muting > > Works for me. Please upload debug info from SC. > Marking bug as closed. If you see this error happen again, please reopen the bug and include the debug log requested.
Reduce number of active targets for SC