search

ithlony / google-cast-sdk

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

Have a way to load a video media immediately for live content (without buffering or caching) #405

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Load a video media type (webm, matroska, ...) to the Chromecast with the 
RemoteMediaPlayer api
2. The video is generated live by a local web server through http protocol, it 
contains live data (media url is something like http://...)
3. Whatch the video on Chromecast and see that is has around 5 seconds of 
latency !

What is the expected output? What do you see instead?
I expected to have a really lower latency. The live video is around 5 seconds 
late.
Maybe this is because of caching/buffering on Chromecast side, but is there a 
way to specify that I want no buffering, or any way to display it immediately 
with lower latency as possible ? This is a local media with live content, it 
doesn't need so much caching !

What version of the product are you using? On what operating system?
I am using last version of Chromecast firmware Version 19084
Last version of Android SDK revision 23.0.2

Please provide any additional information below.

When loading the same http stream to Chrome web browser the display of video is 
almost immediate, the latency becomes very acceptable (less than 1 second). 
I expected to have to same latency with Chromecast... please help on this.

Best regards.

Original issue reported on code.google.com by nicolas....@gmail.com on 8 Oct 2014 at 3:01

GoogleCodeExporter commented 8 years ago 
any news, hints or workaround about this  ? Thanks !

Original comment by nicolas....@gmail.com on 24 Oct 2014 at 10:15

GoogleCodeExporter commented 8 years ago 
We will look into it.

Original comment by and...@google.com on 11 Nov 2014 at 9:56

GoogleCodeExporter commented 8 years ago 
great news, thanks !

Original comment by nicolas....@gmail.com on 12 Nov 2014 at 11:40

GoogleCodeExporter commented 8 years ago 
Hi,
Any hints about this ? Any clue on what do to to reduce this huge latency ?
Thank you.

Original comment by nicolas....@gmail.com on 30 Dec 2014 at 9:38

GoogleCodeExporter commented 8 years ago 
As a work around, you can change your application to use the media source, 
rather than the url. Buffering should be much shorter with media source.

Original comment by and...@google.com on 5 Jan 2015 at 5:59

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Thanks, are you talking about MSE ? If so, are there any sample or 
documentation somewhere on how to do this ?
Thanks again.

Original comment by nicolas....@gmail.com on 5 Jan 2015 at 7:57

GoogleCodeExporter commented 8 years ago 
The workaround probably can't work for my use case (if MSE) because the video 
is matroska format and contains avc codec data.

Original comment by nicolas....@gmail.com on 7 Jan 2015 at 3:49

GoogleCodeExporter commented 8 years ago 
This is the actually one of the purposes of MSE: to allow the JS application to 
control how much or how little to buffer. With content pointed at a single URL, 
the HTML spec does not provide a mechanism for a JS application to specify how 
buffering is done.

Original comment by gun...@google.com on 11 Feb 2015 at 11:56