lihaosky / google-cast-sdk

Automatically exported from code.google.com/p/google-cast-sdk
0 stars 0 forks source link

Mute and Volume not reported correctly #520

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
When using google chrome as the sender, if the user uses the plugin to mute or 
unmute media, an event is not triggered for the current media session update 
listener (pressing play or pause from the plugin will trigger the event).  Also 
the volume.muted property is always false, even when the audio is in fact 
muted.  The volume.level property is always 1 even if the volume is set to 50%.

What version of the product are you using? On what operating system?
Windows 7 Chrome.

Please provide any additional information below.

Original issue reported on code.google.com by a...@milrr.com on 6 Mar 2015 at 3:58

GoogleCodeExporter commented 9 years ago
Please refer to the Chromecast Github sample apps 
(https://github.com/googlecast), in particular the CastVideos-Chrome app, on 
how to handle mute and volume change events. If you believe there's still an 
error, please provide receiver logs along with a detailed list of steps to 
reproduce it and we can reopen the ticket.

Original comment by jonathan...@google.com on 7 Mar 2015 at 1:30

GoogleCodeExporter commented 9 years ago
I have validated that the sample CastVideos-Chromesender also has the bugs I 
noted.

Original comment by a...@milrr.com on 9 Mar 2015 at 3:17

GoogleCodeExporter commented 9 years ago
This is specifically what the volume property of currentMediaSessoin looks like 
when the volume is set to 40% and muted:
volume: chrome.cast.Qc
level: 1
muted: false

Original comment by a...@milrr.com on 9 Mar 2015 at 3:20

GoogleCodeExporter commented 9 years ago

Original comment by jonathan...@google.com on 10 Mar 2015 at 11:27

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
issue #154 might be related

Original comment by p...@zattoo.com on 16 Mar 2015 at 1:19

GoogleCodeExporter commented 9 years ago
We were unable to reproduce the issue. We verified that the session update 
listener (not the media listener) is invoked and the volume level and mute 
state are properly reflected in session.receiver.volume. Please verify that 
you're looking at the correct listener.

Original comment by jonathan...@google.com on 11 Apr 2015 at 12:34