search

will1971 / google-cast-sdk

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

Default Receiver initially reports 2 pause events instead of buffering events for audio streams #443

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Load an mp3 stream using content type "audio/mpeg" and a stream type of 
MediaInfo.STREAM_TYPE_BUFFERED and the default receiver

What is the expected output? What do you see instead?
I would expect to get a buffering event, followed by a play event.
Instead, I get 2 paused events in place of the expected buffering event, then a 
play event.

What version of the product are you using? On what operating system?
com.android.support:mediarouter-v7:21.0.2
com.android.support:appcompat-v7:21.0.2
com.google.android.gms:play-services:6.1.71

Please provide any additional information below.

This was originally seen using the Cast Companion Library, but confirmed to be 
the case when using a RemoteMediaPlayer directly in a very simple test case.

It was also confirmed when using the latest CastVideos-Android project, when 
altering the media source to be as described above, so it should be very easy 
to reproduce.

Original issue reported on code.google.com by j...@soundcloud.com on 4 Dec 2014 at 4:41

GoogleCodeExporter commented 8 years ago 
Do you see the same issue with playing video as well, or is it specific to 
audio?

Original comment by anad...@google.com on 4 Dec 2014 at 4:46

GoogleCodeExporter commented 8 years ago 
I just tested using the CastVideos-Android project without my changes, and yes, 
it happens for video as well. Very surprised this is the case, as this seems 
like a pretty obvious issue. Perhaps it is specific to my environment for some 
reason.

Original comment by j...@soundcloud.com on 4 Dec 2014 at 4:52

GoogleCodeExporter commented 8 years ago 
btw the firmware version on the chromecast I am using is 22062

Original comment by j...@soundcloud.com on 4 Dec 2014 at 4:57

GoogleCodeExporter commented 8 years ago 
Thanks for reporting that. The issue is now reproduced and will be tracked in 
our internal system; when a fix is available, I will update this issue.

Original comment by anad...@google.com on 4 Dec 2014 at 6:39