Skip to content

brainfood / videojs-contrib-hls

Go to a project
Toggle navigation
Toggle navigation pinning
bc2d1c4d by Parul Sharma Committed by Gary Katsevman
Options

HLS live documentation

1 parent 3a3037d0
Inline Side-by-side
Showing 1 changed file with 22 additions and 0 deletions
1 # Video.JS HLS Live
2
3 ## Brightcove Service Differences:
4 - Brightcove uses the Zencoder HLS Live API.
5 - Once ingest begins, approximately 50 seconds later the original manifest is available.
6 - I have not seen any ability to enforce a sliding window, so I believe Brightcove Live HLS serves all available segments on a continuously growing manifest.
7 - One minute after last disconnect from the ingest stream, the event is considered complete and the final manifest delivered.
8 - The final manifest will be different in two distinct ways, it will include the `EXT-X-ENDLIST` tag notifying all connected clients that the live stream has concluded and is now VOD. It will also contain a custom `ZEN-TOTAL-DURATION`: tag with representing the total amount of recorded time in seconds.
9
10 ## Akamai Service Differences:
11 - Akamai only serves HLS Live off of Akamai HD2 endpoints.
12 - These vary from their HDS counterparts by url syntax.
13 - ```<host> /i/``` vs.``` <host> /z/``` for HDS
14 - `master.m3u8` vs.`manifest.f4m` for HDS
15 - Their endpoints are difficult to arrange CORS configurations on.
16 - Akamai manifests span the gamut of known HLS tags, both supported and unsupported by our plugin.
17
18 ## Once Service Differences:
19 - Once manifests tend to include the use of `EXT-X-DISCONTINUITY` tags which are unsupported to date.
20 - Once streams so far tend to use a different encoding algorithm on their segments which sometime result in a range error during transmuxing.
21
22
1 # Live HLS Research 23 # Live HLS Research
2 This document is a collection of notes on Live HLS implementations in the wild. 24 This document is a collection of notes on Live HLS implementations in the wild.
3 25
......