A problem with seeking in Nexus Player when casting

[GoogleCodeExporter]

We have 4 types of MPD manifests, namely Time-Based Segment, Number-Based 
Segment, Segment List and Segment Base.

In case, that we use Time-Based Segment, Number-Based Segment or Segment List, 
there is a problem with seeking in Nexus Player. If we use Chromecast instead 
of Nexus Player, everything works fine.

Only Segment-Base works fine in Nexus Player. In other three manifests, the 
Nexus Player cannot find "seek index", it is trying to move second by second to 
find seek index, but unsuccessfully.

We use Nexus Player in version 5.1.1 and we use this receiver from GitHub - 
https://github.com/googlecast/Cast-Player-Sample. 

Original issue reported on code.google.com by sklenick...@gmail.com on 16 Jul 2015 at 2:45

[GoogleCodeExporter]

Could you please

1. Test this on a Default or Styled receiver as well and report back the result?
2. Provide logs
3. More importantly, could you provide a sample stream that exhibits this issue 
so we can debug and fix the issue?

Thanks.

Original comment by anad...@google.com on 16 Jul 2015 at 7:10

[GoogleCodeExporter]

Original comment by jonathan...@google.com on 16 Jul 2015 at 8:28

• Changed state: NeedInfo

[GoogleCodeExporter]

1. We tested this behaviour against Default receiver - same result. 
APPLICATION_ID = CastMediaControlIntent.DEFAULT_MEDIA_RECEIVER_APPLICATION_ID;
2. Log included
3. Links for testing videos
http://wcdn1007.nacevi.cz/vod/sample2.mp4/manifest.mpd
http://wcdn1007.nacevi.cz/vod/_definst_/bb/bb.smil/manifest.mpd

Sometimes first few seekings are fine (index is found in 3 seconds) but then 
seeking get stuck (see log). Many times you can get stuck during first seek.

Chromecast works fine. We've this problem with mentioned Nexus Player 5.1.1 - 
build LMY47V

Original comment by sklenick...@gmail.com on 20 Jul 2015 at 9:52

Attachments:

• log.txt

[GoogleCodeExporter]

We will investigate the issue further. Please keep the streams available for us 
to test.

Original comment by jonathan...@google.com on 21 Jul 2015 at 7:54

• Changed state: Acknowledged

[GoogleCodeExporter]

How long we have to keep streams available? Is there any progress in this issue?

Original comment by sklenick...@gmail.com on 10 Sep 2015 at 10:52

[GoogleCodeExporter]

The cause may be a content metadata issue, an issue with how we parse the 
MPEG-DASH manifest, or something in the Chrome stack with how we identify the 
keyframes. Please continue to keep the streams available while we investigate, 
and thanks for your ongoing patience.

Original comment by jonathan...@google.com on 17 Sep 2015 at 9:47