Fix support dash.js >= 2.1

[sergey-dryabzhinsky]

As mentioned in #121 (comment)
Pull #121 broke dash.js support.
Seems like we need to return availabilityEndTime back.
Or don't. May be just need right times in playlist.

Use fix-121-dash-availabilityEndTime branch to test fixes and improvements.

[ArhiChief]

Strange, otherwise, its better to have UTCTiming element in MPD

[sergey-dryabzhinsky]

It's recommended. And if you needed it you must use link to the streaming server.
And you should expire file by link:

# HTTP virt-host config

location /time.txt {
  expire -1;
  open_file_cache off;
}

[sergey-dryabzhinsky]

@ArhiChief Can you test latest code from fix-121-dash-availabilityEndTime branch with dash.js ~= 2.0.0 and shaka-player?

[sergey-dryabzhinsky]

Just add into rtmp config:

dash_clock_compensation http_head;
dash_clock_helper_uri http://your-rtmp-server/any-static-file-like-robots.txt;

And add forced expiration for that file in http config section.

[ArhiChief]

ok, I'll test it today

[zydronium]

I have just tested this branch and with the Dash.js 2.1 player the livestream stops after 3 seconds.

[arition]

I have tested http_head and ntp, both methods work fine.
It can be closed now and merge fix-121-dash-availabilityEndTime branch to dev.

[sergey-dryabzhinsky]

@arition I waiting response from @ArhiChief
@zydronium and dev branch working fine? Can you provide you config option for dash, stream encoding options like keyframe interval/GOP?

[sergey-dryabzhinsky]

@Iratu I wonder what is error was: Debug.js:108[40318] [object MediaError].
It may be video/audio decode error. Or playlist chunk download error.
Or even chunk index desynchronization.

And maybe we need msec precision in times.

Can someone provide MPD-playlist from other software, like Wowza?

[sergey-dryabzhinsky]

Seems like we can add some precision to buffer/period times.
And probably fix some roundup for int values.