Wrong segment index in playing MPEG-DASH live stream with SegmentTemplate

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Play the attached MPD.
2. The library seems to calculate wrong segment index.(-6 in attached log)

I use Styled Media Receiver.
dash.js could correctly calculate it.

Original issue reported on code.google.com by reussir....@gmail.com on 4 Dec 2014 at 5:06

Attachments:

• error.log
• steam.mpd

[GoogleCodeExporter]

This is due to a bug with how MPL is processing this type of segment template 
for a dynamic stream.

By the way, there might be one more issue - it appears the manifest has a 
single adaptation where both audio and video are combined.  This is not be 
supported - audio and video need to be in separate adaptations.

Original comment by vadi...@google.com on 4 Dec 2014 at 11:31

[GoogleCodeExporter]

Original comment by jonathan...@google.com on 5 Dec 2014 at 11:38

• Changed state: Acknowledged

[GoogleCodeExporter]

Hi, DASH-IF has a live simulator (disclosure: created by my employer) that has 
been available for a while at http://vm2.dashif.org/livesim.html

This is playable using the dash.js reference player.

I get a similar failure to this bug report when trying to play on Chromecast. 
The Chromecast console log reports:
GET http://vm2.dashif.org/livesim/testpic_2s/A48/-1.m4s 404 (Not Found)

Notice the MPD also uses $Number$ in the segment template. However, to be 
compliant with DASH-IF's own DASH-AVC/264, of course, this stream uses separate 
AdaptationSets for audio and video.

I am using a custom receiver based on 
https://github.com/googlecast/Cast-Player-Sample.git

Original comment by ddenn...@mobitv.com on 16 Oct 2015 at 12:53

[GoogleCodeExporter]

I'm the maintainer of the DASH-IF live simulator. It would be great if this 
issue could be resolved so that the SegmentTemplate live content could be 
played.

A suitable test URL is http://vm2.dashif.org/livesim/testpic_2s/Manifest.mpd
One can also change parameters by specifying other URLs as explained in the 
Github Wiki for the project: 
https://github.com/Dash-Industry-Forum/dash-live-source-simulator

Original comment by mobito...@gmail.com on 16 Oct 2015 at 10:33

[GoogleCodeExporter]

I am also experiencing issues with playing live MPEG-DASH stream to Chromecast.
I have attached sample mpd. This live stream is generated from Wowza using 
H.264/AAC and works fine with dash.js. I can play on-demand content to 
Chromecast with MPEG-DASH using the same source, so the issue seems to be with 
live content. 
What I am seeing is that content plays for about 10 sec and then the receiver 
app enters buffering mode. After that it never stops trying buffering and 
content never resumes. I am also attaching Chromecast receiver app logs for the 
stream that does not play.

Original comment by arnaud.l...@gmail.com on 16 Feb 2016 at 11:35

Attachments:

• manifest.mpd
• cclogs.txt

[GoogleCodeExporter]

Hello,

I'm testing my live stream (live.mpd) with the CastReferencePlayer and the 
receiver somehow starts requesting segment seg-2.m4s instead of the one at live 
point or close to live point, doesn't matter if I set the MPL player.load()'s 
InitStart to Infinity or the Period's duration.

dashif's and shaka player seems to play the same live stream without problems. 
They always start requesting segment that is just a few seconds behind live 
point.

Can I ask how Chromecast's MPL calculate the segment index's $Number$ in live 
streaming with dynamic type?

Does it use only the information in the MPD file or any other information in 
the initialization segment as well, to calculate the segment index $Number$?

Thank you so much for your support!

Original comment by hangu...@gmail.com on 8 Mar 2016 at 2:01

Attachments:

• live.mpd

[GoogleCodeExporter]

I think the cause is missing of MPD@mediaPresentationDuration.

Original comment by hangu...@gmail.com on 8 Mar 2016 at 6:41