HTTP Live Streaming - Revision history

Liz: Removing link(s) to "Trick mode": Deleted PROD.

2024-11-15T01:06:15Z

Removing link(s) to "Trick mode": Deleted PROD.

← Previous revision		Revision as of 01:06, 15 November 2024
Line 30:		Line 30:
	HLS resembles [[Dynamic Adaptive Streaming over HTTP\|MPEG-DASH]] in that it works by breaking the overall stream into a sequence of small HTTP-based file downloads, each downloading one short chunk of an overall potentially unbounded transport stream. A list of available streams, encoded at different bit rates, is sent to the client using an [[Extended M3U\|extended M3U playlist]].<ref>{{cite web\|url= https://larryjordan.com/articles/basics-of-http-live-streaming\|title= The Basics of HTTP Live Streaming\|last= Jordan\|first= Larry\|date= 10 June 2013\|work= Larry's Blog\|publisher= Larry Jordan & Associates\|access-date= 18 June 2013}}</ref>		HLS resembles [[Dynamic Adaptive Streaming over HTTP\|MPEG-DASH]] in that it works by breaking the overall stream into a sequence of small HTTP-based file downloads, each downloading one short chunk of an overall potentially unbounded transport stream. A list of available streams, encoded at different bit rates, is sent to the client using an [[Extended M3U\|extended M3U playlist]].<ref>{{cite web\|url= https://larryjordan.com/articles/basics-of-http-live-streaming\|title= The Basics of HTTP Live Streaming\|last= Jordan\|first= Larry\|date= 10 June 2013\|work= Larry's Blog\|publisher= Larry Jordan & Associates\|access-date= 18 June 2013}}</ref>

	Based on standard HTTP transactions, HTTP Live Streaming can traverse any [[Firewall (computing)\|firewall]] or [[proxy server]] that lets through standard HTTP traffic, unlike UDP-based protocols such as [[Real-time Transport Protocol\|RTP]]. This also allows content to be offered from conventional HTTP servers and delivered over widely available HTTP-based [[content delivery network]]s.<ref>{{cite web \|date=March 29, 2015 \|title=MPEG-DASH vs. Apple HLS vs. Smooth Streaming vs. Adobe HDS \|url=https://bitmovin.com/mpeg-dash-vs-apple-hls-vs-microsoft-smooth-streaming-vs-adobe-hds/ \|website=Bitmovin}}</ref><ref>{{Cite book \|last1=Chen \|first1=Songqing \|last2=Shen \|first2=Bo \|last3=Tan \|first3=Wai-tian \|last4=Wee \|first4=Susie \|last5=Zhang \|first5=Xiaodong \|title=2006 IEEE International Conference on Multimedia and Expo \|chapter=A Case for Internet Streaming via Web Servers \|date=2006-07-09 \|chapter-url=https://ieeexplore.ieee.org/document/4037057 \|pages=2145–2148 \|doi=10.1109/ICME.2006.262660 \|isbn=9781424403677 \|issn=1945-7871 \|eissn=1945-788X \|s2cid=9202042 }}</ref><ref>{{Cite journal \|last1=Songqing Chen \|last2=Bo Shen \|last3=Wee \|first3=S. \|last4=Xiaodong Zhang \|date=2007-07-23 \|title=SProxy: A Caching Infrastructure to Support Internet Streaming \|url=https://ieeexplore.ieee.org/document/4276704 \|journal=IEEE Transactions on Multimedia \|volume=9 \|issue=5 \|pages=1062–1072 \|doi=10.1109/TMM.2007.898943 \|s2cid=870854 \|issn=1520-9210\|citeseerx=10.1.1.74.4838 }}</ref> The standard also includes a standard encryption mechanism<ref>{{cite web\|url= http://tools.ietf.org/html/draft-pantos-http-live-streaming-07\|title= HTTP Live Streaming\|last= Pantos\|first= R.\|date= 30 September 2011\|publisher= Internet Engineering Task Force\|access-date= 18 June 2013}}</ref> and secure-key distribution using [[HTTPS]], which together provide a simple [[Digital rights management\|DRM]] system. Later versions of the protocol also provide for ~~[[trick mode\|~~trick-mode]] fast-forward and rewind and for integration of subtitles.		Based on standard HTTP transactions, HTTP Live Streaming can traverse any [[Firewall (computing)\|firewall]] or [[proxy server]] that lets through standard HTTP traffic, unlike UDP-based protocols such as [[Real-time Transport Protocol\|RTP]]. This also allows content to be offered from conventional HTTP servers and delivered over widely available HTTP-based [[content delivery network]]s.<ref>{{cite web \|date=March 29, 2015 \|title=MPEG-DASH vs. Apple HLS vs. Smooth Streaming vs. Adobe HDS \|url=https://bitmovin.com/mpeg-dash-vs-apple-hls-vs-microsoft-smooth-streaming-vs-adobe-hds/ \|website=Bitmovin}}</ref><ref>{{Cite book \|last1=Chen \|first1=Songqing \|last2=Shen \|first2=Bo \|last3=Tan \|first3=Wai-tian \|last4=Wee \|first4=Susie \|last5=Zhang \|first5=Xiaodong \|title=2006 IEEE International Conference on Multimedia and Expo \|chapter=A Case for Internet Streaming via Web Servers \|date=2006-07-09 \|chapter-url=https://ieeexplore.ieee.org/document/4037057 \|pages=2145–2148 \|doi=10.1109/ICME.2006.262660 \|isbn=9781424403677 \|issn=1945-7871 \|eissn=1945-788X \|s2cid=9202042 }}</ref><ref>{{Cite journal \|last1=Songqing Chen \|last2=Bo Shen \|last3=Wee \|first3=S. \|last4=Xiaodong Zhang \|date=2007-07-23 \|title=SProxy: A Caching Infrastructure to Support Internet Streaming \|url=https://ieeexplore.ieee.org/document/4276704 \|journal=IEEE Transactions on Multimedia \|volume=9 \|issue=5 \|pages=1062–1072 \|doi=10.1109/TMM.2007.898943 \|s2cid=870854 \|issn=1520-9210\|citeseerx=10.1.1.74.4838 }}</ref> The standard also includes a standard encryption mechanism<ref>{{cite web\|url= http://tools.ietf.org/html/draft-pantos-http-live-streaming-07\|title= HTTP Live Streaming\|last= Pantos\|first= R.\|date= 30 September 2011\|publisher= Internet Engineering Task Force\|access-date= 18 June 2013}}</ref> and secure-key distribution using [[HTTPS]], which together provide a simple [[Digital rights management\|DRM]] system. Later versions of the protocol also provide for trick-mode fast-forward and rewind and for integration of subtitles.

	Apple has documented HTTP Live Streaming as an [[Internet Draft]] (Individual Submission), the first stage in the process of publishing it as a [[Request for Comments]] (RFC). As of December 2015, the authors of that document have requested the RFC Independent Stream Editor (ISE) to publish the document as an informational (non-standard) RFC outside of the [[IETF]] consensus process.<ref>		Apple has documented HTTP Live Streaming as an [[Internet Draft]] (Individual Submission), the first stage in the process of publishing it as a [[Request for Comments]] (RFC). As of December 2015, the authors of that document have requested the RFC Independent Stream Editor (ISE) to publish the document as an informational (non-standard) RFC outside of the [[IETF]] consensus process.<ref>

Kvng: grammar. add link. MOS:SLASH.

2024-10-30T17:54:31Z

grammar. add link. MOS:SLASH.

← Previous revision		Revision as of 17:54, 30 October 2024
Line 25:		Line 25:
	\| extended to = .m3u8		\| extended to = .m3u8
	}}		}}

	'''HTTP Live Streaming''' (also known as '''HLS''') is an [[HTTP]]-based [[adaptive bitrate streaming]] communications protocol developed by [[Apple Inc.]] and released in 2009. Support for the protocol is widespread in media players, web browsers, mobile devices, and streaming media servers. {{As of\|2022}}, an annual video industry survey has consistently found it to be the most popular streaming format.<ref>{{cite web \|last1=Lederer \|first1=Stefan \|title=2022 Video Developer Report \|url=https://bitmovin.com/wp-content/uploads/2022/12/bitmovin-6th-video-developer-report-2022-2023.pdf \|website=Bitmovin \|access-date=25 October 2023 \|language=en}}</ref>		'''HTTP Live Streaming''' (also known as '''HLS''') is an [[HTTP]]-based [[adaptive bitrate streaming]] communications protocol developed by [[Apple Inc.]] and released in 2009. Support for the protocol is widespread in media players, web browsers, mobile devices, and streaming media servers. {{As of\|2022}}, an annual video industry survey has consistently found it to be the most popular streaming format.<ref>{{cite web \|last1=Lederer \|first1=Stefan \|title=2022 Video Developer Report \|url=https://bitmovin.com/wp-content/uploads/2022/12/bitmovin-6th-video-developer-report-2022-2023.pdf \|website=Bitmovin \|access-date=25 October 2023 \|language=en}}</ref>

Line 84:		Line 85:

	Other features include:		Other features include:
	* Playlist Delta Updates: only sending what changed between ~~playlist~~, which typically fit in single MTU making it more efficient to load the playlists which, with large DVR windows, can be quite large.		* Playlist Delta Updates: only sending what changed between playlists, which typically fit in a single MTU making it more efficient to load the playlists which, with large DVR windows, can be quite large.
	* Blocking of playlist reload: when requesting live media playlists, wait until the first segment is also ready, and return both at same time (saving additional HTTP/TCP requests)		* Blocking of playlist reload: when requesting live media playlists, wait until the first segment is also ready, and return both at the same time (saving additional HTTP/TCP requests)
	* Rendition Reports: add metadata to other media renditions to make switching between ABR faster		* Rendition Reports: add metadata to other media renditions to make switching between ABR faster
	*New tags added: EXT-X-SERVER-CONTROL / EXT-X-PART / EXT-X-SKIP / EXT-X-RENDITION-REPORT		*New tags added: EXT-X-SERVER-CONTROL / EXT-X-PART / EXT-X-SKIP / EXT-X-RENDITION-REPORT
Line 96:		Line 97:

	===Dynamic ad insertion===		===Dynamic ad insertion===
	Dynamic ad insertion is supported in HLS using splice information based on [[SCTE-35]] specification. The SCTE-35 splice message is inserted on the media playlist file using the EXT-X-DATERANGE tag. Each SCTE-35 splice_info_section() is represented by an EXT-X-DATERANGE tag with a SCTE35-CMD attribute. A SCTE-35 splice out/in pair signaled by the splice_insert() commands ~~are~~ represented by one or more EXT-X-DATERANGE tags carrying the same ID attribute. The SCTE-35 splice out command should have the SCTE35-OUT attribute and the splice in command should have the SCTE35-IN attribute.		Dynamic [[Advertisement\|ad]] insertion is supported in HLS using splice information based on [[SCTE-35]] specification. The SCTE-35 splice message is inserted into the media playlist file using the EXT-X-DATERANGE tag. Each SCTE-35 splice_info_section() is represented by an EXT-X-DATERANGE tag with a SCTE35-CMD attribute. A SCTE-35 splice out/in pair signaled by the splice_insert() commands is represented by one or more EXT-X-DATERANGE tags carrying the same ID attribute. The SCTE-35 splice out command should have the SCTE35-OUT attribute and the splice in command should have the SCTE35-IN attribute.

	Between the two EXT-X-DATERANGE tags that contain the SCTE35-OUT and SCTE35-IN attributes respectively there may be a sequence of media segment URIs. These media segments normally represent ad programs ~~which~~ can be replaced by the local or customized ad. The ad replacement does not require the replacement of the media files, only the URIs in the playlist need to be changed to point different ad programs. The ad replacement can be done on the origin server or on the client's media playing device.		Between the two EXT-X-DATERANGE tags that contain the SCTE35-OUT and SCTE35-IN attributes respectively, there may be a sequence of media segment URIs. These media segments normally represent ad programs that can be replaced by the local or customized ad. The ad replacement does not require the replacement of the media files, only the URIs in the playlist need to be changed to point to different ad programs. The ad replacement can be done on the origin server or on the client's media-playing device.

	==Server implementations==		==Server implementations==
Line 111:		Line 112:
	* [[Bitmovin]] supports HLS for on-demand and live streaming.		* [[Bitmovin]] supports HLS for on-demand and live streaming.
	* [[CDNetworks]] supports HLS for live and on-demand streams.		* [[CDNetworks]] supports HLS for live and on-demand streams.
	* [[Cisco Systems]]: supports full end to end delivery for Live/TSTV/VOD/HLS and Cloud DVR services.		* [[Cisco Systems]]: supports full end-to-end delivery for Live/TSTV/VOD/HLS and Cloud DVR services.
	* [[Cloudflare]] supports HLS for live and on-demand streams.		* [[Cloudflare]] supports HLS for live and on-demand streams.
	* [[EdgeCast Networks]] supports cross-device streaming using HLS.		* [[EdgeCast Networks]] supports cross-device streaming using HLS.
Line 382:		Line 383:
	\|{{no}}\|\| Live and stored HLS. Live can be transmuxed from several input mux including RTP, RTMP, and [[MPEG transport stream\|MPEG-TS]] using H.264 encoding		\|{{no}}\|\| Live and stored HLS. Live can be transmuxed from several input mux including RTP, RTMP, and [[MPEG transport stream\|MPEG-TS]] using H.264 encoding
	\|-		\|-
	\| Telebreeze Coder / Media Server \|\| Input streams / interfaces: UDP, TCP, RTP, HLS, HTTP, RTMP (MPEG-TS) <br />Output Streams: HLS, HTTP, UDP <br/>Preprocessing: Resize, Deinterlace, Frame Rate Conversion, Audio Resampling, Logo Rendering \|\| \|\| Telebreeze		\| Telebreeze Coder / Media Server \|\| Input streams and interfaces: UDP, TCP, RTP, HLS, HTTP, RTMP (MPEG-TS) <br />Output Streams: HLS, HTTP, UDP <br/>Preprocessing: Resize, Deinterlace, Frame Rate Conversion, Audio Resampling, Logo Rendering \|\| \|\| Telebreeze
	\|{{no}}\|\|		\|{{no}}\|\|
	\|-		\|-
Line 402:		Line 403:
	\|-		\|-
	\|TAC - Teracue Application Cloud		\|TAC - Teracue Application Cloud
	\|Professional stream routing and real-time encoding/transcoding platform supporting various audio and video ~~codedc~~ and streaming protocols		\|Professional stream routing and real-time encoding/transcoding platform supporting various audio and video codec and streaming protocols
	\|1.0		\|1.0
	\|Teracue\|Teracue		\|Teracue\|Teracue
	\|{{no}}		\|{{no}}
	\|Supported protocols IN and OUT: UDP, RTP, RTSP, RTMP, TCP (Client/Server), HLS, HTTP, FEC, SRT		\|Supported protocols IN and OUT: UDP, RTP, RTSP, RTMP, TCP (Client/Server), HLS, HTTP, FEC, SRT
	Supported ~~prptpcols~~ IN only: SDVoE and NDI		Supported protocols IN only: SDVoE and NDI
	\|-		\|-
	\|[[Peertube]]		\|[[Peertube]]
Line 456:		Line 457:

	==References==		==References==
	{{Reflist~~\|30em~~}}		{{Reflist}}

	[[Category:Hypertext Transfer Protocol]]		[[Category:Hypertext Transfer Protocol]]

BD2412: Clean up spacing around commas and other punctuation fixes, replaced: ,R → , R (5), ,S → , S

2024-10-02T12:56:41Z

Clean up spacing around commas and other punctuation fixes, replaced: ,R → , R (5), ,S → , S

← Previous revision		Revision as of 12:56, 2 October 2024
Line 416:		Line 416:
	\|Videos are made available via HTTP to download, but playback favors a peer-to-peer playback using HLS and WebTorrent.		\|Videos are made available via HTTP to download, but playback favors a peer-to-peer playback using HLS and WebTorrent.
	\|}		\|}

	=== Live Encoders ===		=== Live Encoders ===
	{\| class="wikitable"		{\| class="wikitable"
Line 423:		Line 424:
	\|-		\|-
	\|-		\|-
	\| ENC-400 Series \|\| Live hardware encoder with SDI or HDMI \|\| 1.0 \|\| Teracue \|\|{{no}}\|\| Supported protocols: TS over UDP,RTP, TCP, RTP/RTSP, RTMP push, HLS		\| ENC-400 Series \|\| Live hardware encoder with SDI or HDMI \|\| 1.0 \|\| Teracue \|\|{{no}}\|\| Supported protocols: TS over UDP, RTP, TCP, RTP/RTSP, RTMP push, HLS
	\|-		\|-
	\| WELLAV NB100 \|\| Live Streamcast with SDI or HDMI, CVBS \|\| 1.0 \|\| Wellav Technologies \|\|{{no}}\|\| Supported protocols: TS UDP,RTP, RTP/RTSP, RTMP, HLS;		\| WELLAV NB100 \|\| Live Streamcast with SDI or HDMI, CVBS \|\| 1.0 \|\| Wellav Technologies \|\|{{no}}\|\| Supported protocols: TS UDP, RTP, RTP/RTSP, RTMP, HLS;
	\|-		\|-
	\| ZyPerMX4 \|\| Live hardware encoder with 4 HDMI inputs \|\| 2.14 \|\| ZeeVee \|\|{{no}}\|\| Supported protocols: TS over UDP,RTP, H.264/MPEG-4 AVC, HLS, RTMP, RTSP		\| ZyPerMX4 \|\| Live hardware encoder with 4 HDMI inputs \|\| 2.14 \|\| ZeeVee \|\|{{no}}\|\| Supported protocols: TS over UDP, RTP, H.264/MPEG-4 AVC, HLS, RTMP, RTSP
	\|-		\|-
	\| ZyPerMX2 \|\| Live hardware encoder with 2 HDMI inputs \|\| 2.14 \|\| ZeeVee \|\|{{no}}\|\| Supported protocols: TS over UDP,RTP, H.264/MPEG-4 AVC, HLS, RTMP, RTSP		\| ZyPerMX2 \|\| Live hardware encoder with 2 HDMI inputs \|\| 2.14 \|\| ZeeVee \|\|{{no}}\|\| Supported protocols: TS over UDP, RTP, H.264/MPEG-4 AVC, HLS, RTMP, RTSP
	\|-		\|-
	\| Elecard CodecWorks \|\| Live software encoder with up to 8 SDI/HDMI or NDI inputs \|\| 4.6 \|\|Elecard\|\|{{no}} \|\| Supported protocols: TS UDP,RTP,SRT, RTMP push, HLS, Mpeg-DASH		\| Elecard CodecWorks \|\| Live software encoder with up to 8 SDI/HDMI or NDI inputs \|\| 4.6 \|\|Elecard\|\|{{no}} \|\| Supported protocols: TS UDP, RTP, SRT, RTMP push, HLS, Mpeg-DASH
	\|-		\|-
	\| StreamS Live Encoder \|\| Live software/hardware audio encoder with professional interface options \|\| 3.0 \|\| StreamS \|\|{{no}}\|\| Supported protocols: HLS/DASH ES, fMP4, FTP, FTPS, HTTP, HTTPS, DAV, DAVS, Akamai, Amazon S3, Microsoft BLOB, Google Cloud <br> AAC-LC/HE-AAC/xHE-AAC - Synchronous Realtime Now Playing and Control Metadata and Graphics		\| StreamS Live Encoder \|\| Live software/hardware audio encoder with professional interface options \|\| 3.0 \|\| StreamS \|\|{{no}}\|\| Supported protocols: HLS/DASH ES, fMP4, FTP, FTPS, HTTP, HTTPS, DAV, DAVS, Akamai, Amazon S3, Microsoft BLOB, Google Cloud <br> AAC-LC/HE-AAC/xHE-AAC - Synchronous Realtime Now Playing and Control Metadata and Graphics

2A02:B127:11:B543:E8D9:1723:ACDB:524E at 09:51, 25 September 2024

2024-09-25T09:51:12Z

← Previous revision		Revision as of 09:51, 25 September 2024
Line 123:		Line 123:
	* [[Node.js]] with the hls-server package supports hls encoding to live mode and local files conversion.<ref>{{cite web\|url=https://www.npmjs.com/package/hls-server\|title=hls-server\|date=12 February 2018 \|publisher=npm}}</ref>		* [[Node.js]] with the hls-server package supports hls encoding to live mode and local files conversion.<ref>{{cite web\|url=https://www.npmjs.com/package/hls-server\|title=hls-server\|date=12 February 2018 \|publisher=npm}}</ref>
	* [[OvenMediaEngine]] is an [[Open-source software\|open source]] project that supports Low Latency HLS (LL-HLS) and HLS for live streaming.		* [[OvenMediaEngine]] is an [[Open-source software\|open source]] project that supports Low Latency HLS (LL-HLS) and HLS for live streaming.
			* [[PeerTube]] supports HLS
	*[[Storm Streaming Server]] supports HLS as backup mode for its Media Source Extensions player<ref>{{Cite web\|title=Storm Streaming\|url=https://www.stormstreaming.com/\|access-date=2021-07-30\|website=Storm Streaming\|language=en\|quote=Output devices: HLS, MPEG-DASH, WebSocket, RTMP}}</ref>		*[[Storm Streaming Server]] supports HLS as backup mode for its Media Source Extensions player<ref>{{Cite web\|title=Storm Streaming\|url=https://www.stormstreaming.com/\|access-date=2021-07-30\|website=Storm Streaming\|language=en\|quote=Output devices: HLS, MPEG-DASH, WebSocket, RTMP}}</ref>
	* [[Tata Communications]] [[Content delivery network\|CDN]] supports HLS for live and on-demand streams.		* [[Tata Communications]] [[Content delivery network\|CDN]] supports HLS for live and on-demand streams.

125.180.84.9: /* Servers */ update software list

2024-09-09T07:42:43Z

Servers: update software list

← Previous revision		Revision as of 07:42, 9 September 2024
Line 234:		Line 234:
	\|-		\|-
	\| THEOplayer<ref>{{cite web\|url=https://www.theoplayer.com/documentation/hls.html\|title=HTML5 Video Player – THEOplayer\|first=THEO Technologies\|last=NV\|website=www.theoplayer.com}}</ref> \|\| HTML5, SDK (Android, iOS, Android TV, tvOS, Chromecast, WebOS, FireTV, Tizen) \|\| {{yes}} \|\| {{yes}} \|\| \|\| THEO Technologies		\| THEOplayer<ref>{{cite web\|url=https://www.theoplayer.com/documentation/hls.html\|title=HTML5 Video Player – THEOplayer\|first=THEO Technologies\|last=NV\|website=www.theoplayer.com}}</ref> \|\| HTML5, SDK (Android, iOS, Android TV, tvOS, Chromecast, WebOS, FireTV, Tizen) \|\| {{yes}} \|\| {{yes}} \|\| \|\| THEO Technologies
			\|-
			\| OvenPlayer \|\| HTML5 \|\| {{yes}} \|\| {{yes}} \|\| 0.10.0+ \|\| AirenSoft
	\|-		\|-
	\| Viblast Player (SDK) \|\| HTML5, iOS, Android \|\| {{yes}} \|\| {{partial}} \|\| \|\| Viblast Ltd		\| Viblast Player (SDK) \|\| HTML5, iOS, Android \|\| {{yes}} \|\| {{partial}} \|\| \|\| Viblast Ltd
Line 369:		Line 371:
	\| Nginx Plus \|\| VOD HLS as origin \|\| \|\| [[NGINX, Inc.]]		\| Nginx Plus \|\| VOD HLS as origin \|\| \|\| [[NGINX, Inc.]]
	\|{{no}}\|\|		\|{{no}}\|\|
			\|-
			\| [[OvenMediaEngine]] \|\| Supports Low Latency HLS (HLSv7+), HLS (HLSv3+), ABR LL-HLS, and ABR HLS for live streaming \|\| 0.16.0+ \|\| AirenSoft
			\|{{yes}}\|\| [[GNU Affero General Public License]]
	\|-		\|-
	\| Flussonic Media Server \|\| Multi-platform support for HTTP, RTSP, RTMP, DASH, Time Shifting, DVR Functions with Unlimited Rewind Capabilities HLS streaming specific to iOS platform support. \|\| 3.0+ \|\| Flussonic, LLC.		\| Flussonic Media Server \|\| Multi-platform support for HTTP, RTSP, RTMP, DASH, Time Shifting, DVR Functions with Unlimited Rewind Capabilities HLS streaming specific to iOS platform support. \|\| 3.0+ \|\| Flussonic, LLC.
Line 410:		Line 415:
	\|Videos are made available via HTTP to download, but playback favors a peer-to-peer playback using HLS and WebTorrent.		\|Videos are made available via HTTP to download, but playback favors a peer-to-peer playback using HLS and WebTorrent.
	\|}		\|}

	=== Live Encoders ===		=== Live Encoders ===
	{\| class="wikitable"		{\| class="wikitable"

125.180.84.9: /* Server implementations */ update server list

2024-09-09T07:23:55Z

Server implementations: update server list

← Previous revision		Revision as of 07:23, 9 September 2024
Line 122:		Line 122:
	* [[Nimble Streamer]] supports HLS in live and VOD mode, Apple Low Latency HLS spec is also supported.		* [[Nimble Streamer]] supports HLS in live and VOD mode, Apple Low Latency HLS spec is also supported.
	* [[Node.js]] with the hls-server package supports hls encoding to live mode and local files conversion.<ref>{{cite web\|url=https://www.npmjs.com/package/hls-server\|title=hls-server\|date=12 February 2018 \|publisher=npm}}</ref>		* [[Node.js]] with the hls-server package supports hls encoding to live mode and local files conversion.<ref>{{cite web\|url=https://www.npmjs.com/package/hls-server\|title=hls-server\|date=12 February 2018 \|publisher=npm}}</ref>
			* [[OvenMediaEngine]] is an [[Open-source software\|open source]] project that supports Low Latency HLS (LL-HLS) and HLS for live streaming.
	*[[Storm Streaming Server]] supports HLS as backup mode for its Media Source Extensions player<ref>{{Cite web\|title=Storm Streaming\|url=https://www.stormstreaming.com/\|access-date=2021-07-30\|website=Storm Streaming\|language=en\|quote=Output devices: HLS, MPEG-DASH, WebSocket, RTMP}}</ref>		*[[Storm Streaming Server]] supports HLS as backup mode for its Media Source Extensions player<ref>{{Cite web\|title=Storm Streaming\|url=https://www.stormstreaming.com/\|access-date=2021-07-30\|website=Storm Streaming\|language=en\|quote=Output devices: HLS, MPEG-DASH, WebSocket, RTMP}}</ref>
	* [[Tata Communications]] [[Content delivery network\|CDN]] supports HLS for live and on-demand streams.		* [[Tata Communications]] [[Content delivery network\|CDN]] supports HLS for live and on-demand streams.

Kvng: avoid unnec redirect

2024-08-18T03:12:05Z

avoid unnec redirect

← Previous revision		Revision as of 03:12, 18 August 2024
Line 29:		Line 29:
	HLS resembles [[Dynamic Adaptive Streaming over HTTP\|MPEG-DASH]] in that it works by breaking the overall stream into a sequence of small HTTP-based file downloads, each downloading one short chunk of an overall potentially unbounded transport stream. A list of available streams, encoded at different bit rates, is sent to the client using an [[Extended M3U\|extended M3U playlist]].<ref>{{cite web\|url= https://larryjordan.com/articles/basics-of-http-live-streaming\|title= The Basics of HTTP Live Streaming\|last= Jordan\|first= Larry\|date= 10 June 2013\|work= Larry's Blog\|publisher= Larry Jordan & Associates\|access-date= 18 June 2013}}</ref>		HLS resembles [[Dynamic Adaptive Streaming over HTTP\|MPEG-DASH]] in that it works by breaking the overall stream into a sequence of small HTTP-based file downloads, each downloading one short chunk of an overall potentially unbounded transport stream. A list of available streams, encoded at different bit rates, is sent to the client using an [[Extended M3U\|extended M3U playlist]].<ref>{{cite web\|url= https://larryjordan.com/articles/basics-of-http-live-streaming\|title= The Basics of HTTP Live Streaming\|last= Jordan\|first= Larry\|date= 10 June 2013\|work= Larry's Blog\|publisher= Larry Jordan & Associates\|access-date= 18 June 2013}}</ref>

	Based on standard HTTP transactions, HTTP Live Streaming can traverse any [[Firewall (computing)\|firewall]] or [[proxy server]] that lets through standard HTTP traffic, unlike UDP-based protocols such as [[Real-time Transport Protocol\|RTP]]. This also allows content to be offered from conventional HTTP servers and delivered over widely available HTTP-based [[content delivery network]]s.<ref>{{cite web \|date=March 29, 2015 \|title=MPEG-DASH vs. Apple HLS vs. Smooth Streaming vs. Adobe HDS \|url=https://bitmovin.com/mpeg-dash-vs-apple-hls-vs-microsoft-smooth-streaming-vs-adobe-hds/ \|website=Bitmovin}}</ref><ref>{{Cite book \|last1=Chen \|first1=Songqing \|last2=Shen \|first2=Bo \|last3=Tan \|first3=Wai-tian \|last4=Wee \|first4=Susie \|last5=Zhang \|first5=Xiaodong \|title=2006 IEEE International Conference on Multimedia and Expo \|chapter=A Case for Internet Streaming via Web Servers \|date=2006-07-09 \|chapter-url=https://ieeexplore.ieee.org/document/4037057 \|pages=2145–2148 \|doi=10.1109/ICME.2006.262660 \|isbn=9781424403677 \|issn=1945-7871 \|eissn=1945-788X \|s2cid=9202042 }}</ref><ref>{{Cite journal \|last1=Songqing Chen \|last2=Bo Shen \|last3=Wee \|first3=S. \|last4=Xiaodong Zhang \|date=2007-07-23 \|title=SProxy: A Caching Infrastructure to Support Internet Streaming \|url=https://ieeexplore.ieee.org/document/4276704 \|journal=IEEE Transactions on Multimedia \|volume=9 \|issue=5 \|pages=1062–1072 \|doi=10.1109/TMM.2007.898943 \|s2cid=870854 \|issn=1520-9210\|citeseerx=10.1.1.74.4838 }}</ref> The standard also includes a standard encryption mechanism<ref>{{cite web\|url= http://tools.ietf.org/html/draft-pantos-http-live-streaming-07\|title= HTTP Live Streaming\|last= Pantos\|first= R.\|date= 30 September 2011\|publisher= Internet Engineering Task Force\|access-date= 18 June 2013}}</ref> and secure-key distribution using [[HTTPS]], which together provide a simple [[Digital ~~Rights~~ ~~Management~~\|DRM]] system. Later versions of the protocol also provide for [[trick mode\|trick-mode]] fast-forward and rewind and for integration of subtitles.		Based on standard HTTP transactions, HTTP Live Streaming can traverse any [[Firewall (computing)\|firewall]] or [[proxy server]] that lets through standard HTTP traffic, unlike UDP-based protocols such as [[Real-time Transport Protocol\|RTP]]. This also allows content to be offered from conventional HTTP servers and delivered over widely available HTTP-based [[content delivery network]]s.<ref>{{cite web \|date=March 29, 2015 \|title=MPEG-DASH vs. Apple HLS vs. Smooth Streaming vs. Adobe HDS \|url=https://bitmovin.com/mpeg-dash-vs-apple-hls-vs-microsoft-smooth-streaming-vs-adobe-hds/ \|website=Bitmovin}}</ref><ref>{{Cite book \|last1=Chen \|first1=Songqing \|last2=Shen \|first2=Bo \|last3=Tan \|first3=Wai-tian \|last4=Wee \|first4=Susie \|last5=Zhang \|first5=Xiaodong \|title=2006 IEEE International Conference on Multimedia and Expo \|chapter=A Case for Internet Streaming via Web Servers \|date=2006-07-09 \|chapter-url=https://ieeexplore.ieee.org/document/4037057 \|pages=2145–2148 \|doi=10.1109/ICME.2006.262660 \|isbn=9781424403677 \|issn=1945-7871 \|eissn=1945-788X \|s2cid=9202042 }}</ref><ref>{{Cite journal \|last1=Songqing Chen \|last2=Bo Shen \|last3=Wee \|first3=S. \|last4=Xiaodong Zhang \|date=2007-07-23 \|title=SProxy: A Caching Infrastructure to Support Internet Streaming \|url=https://ieeexplore.ieee.org/document/4276704 \|journal=IEEE Transactions on Multimedia \|volume=9 \|issue=5 \|pages=1062–1072 \|doi=10.1109/TMM.2007.898943 \|s2cid=870854 \|issn=1520-9210\|citeseerx=10.1.1.74.4838 }}</ref> The standard also includes a standard encryption mechanism<ref>{{cite web\|url= http://tools.ietf.org/html/draft-pantos-http-live-streaming-07\|title= HTTP Live Streaming\|last= Pantos\|first= R.\|date= 30 September 2011\|publisher= Internet Engineering Task Force\|access-date= 18 June 2013}}</ref> and secure-key distribution using [[HTTPS]], which together provide a simple [[Digital rights management\|DRM]] system. Later versions of the protocol also provide for [[trick mode\|trick-mode]] fast-forward and rewind and for integration of subtitles.

	Apple has documented HTTP Live Streaming as an [[Internet Draft]] (Individual Submission), the first stage in the process of publishing it as a [[Request for Comments]] (RFC). As of December 2015, the authors of that document have requested the RFC Independent Stream Editor (ISE) to publish the document as an informational (non-standard) RFC outside of the [[IETF]] consensus process.<ref>		Apple has documented HTTP Live Streaming as an [[Internet Draft]] (Individual Submission), the first stage in the process of publishing it as a [[Request for Comments]] (RFC). As of December 2015, the authors of that document have requested the RFC Independent Stream Editor (ISE) to publish the document as an informational (non-standard) RFC outside of the [[IETF]] consensus process.<ref>

Bruce1ee: fixed lint errors – missing end tag

2024-08-09T00:37:24Z

fixed lint errors – missing end tag

← Previous revision		Revision as of 00:37, 9 August 2024
Line 160:		Line 160:
	\| [[Safari (web browser)]] \|\| macOS, iOS \|\| {{yes}} \|\| {{yes}} \|\| 6.0+ <p> Has full HLS support.</p> \|\| Apple		\| [[Safari (web browser)]] \|\| macOS, iOS \|\| {{yes}} \|\| {{yes}} \|\| 6.0+ <p> Has full HLS support.</p> \|\| Apple
	\|-		\|-
	\| [[Microsoft Edge]] (web browser) \|\| Windows 10 \|\| {{partial\|Native support on Edge Legacy.<p>Support via [[Media Source Extensions]] on Edge Chromium.</p>}} \|\| {{yes}} \|\| Supported natively on Edge Legacy's engine EdgeHTML from version 12 to 18. <p> No native support on Edge Chromium from version 79 to present.<ref>{{Cite web\|url=https://caniuse.com/http-live-streaming\|title=HTTP Live Streaming (HLS) \| Can I use... Support tables for HTML5, CSS3, etc\|website=caniuse.com}}</ref> \|\| Microsoft		\| [[Microsoft Edge]] (web browser) \|\| Windows 10 \|\| {{partial\|Native support on Edge Legacy.<p>Support via [[Media Source Extensions]] on Edge Chromium.</p>}} \|\| {{yes}} \|\| Supported natively on Edge Legacy's engine EdgeHTML from version 12 to 18. <p> No native support on Edge Chromium from version 79 to present.<ref>{{Cite web\|url=https://caniuse.com/http-live-streaming\|title=HTTP Live Streaming (HLS) \| Can I use... Support tables for HTML5, CSS3, etc\|website=caniuse.com}}</ref></p> \|\| Microsoft
	\|-		\|-
	\| [[Google Chrome]] (web browser) / [[Chromium (web browser)\|Chromium]] \|\| Windows, macOS, Linux, Android, iOS \|\| {{partial\|OS-dependent support on Android/iOS.<p>Support via [[Media Source Extensions]] on other OS.</p>}} \|\| {{yes}} \|\| 30+ <p> Android and iOS have OS-dependent native support.</p> <p> Other platforms require Media Source Extensions. </p>\|\| Google		\| [[Google Chrome]] (web browser) / [[Chromium (web browser)\|Chromium]] \|\| Windows, macOS, Linux, Android, iOS \|\| {{partial\|OS-dependent support on Android/iOS.<p>Support via [[Media Source Extensions]] on other OS.</p>}} \|\| {{yes}} \|\| 30+ <p> Android and iOS have OS-dependent native support.</p> <p> Other platforms require Media Source Extensions. </p>\|\| Google

Uzume: /* Clients */ HTML audio & HTML video

2024-05-10T08:13:44Z

Clients: HTML audio & HTML video

← Previous revision		Revision as of 08:13, 10 May 2024
Line 153:		Line 153:

	=== Clients ===		=== Clients ===
	{{See also\|~~HTML5~~ audio}}		{{See also\|HTML audio\|HTML video}}
	{\| class="wikitable sortable"		{\| class="wikitable sortable"
	\|-		\|-

CoolieCoolster: Added non-breaking space to non-template file size, bitrate, and bandwidth values (via WP:JWB)

2024-04-23T16:48:44Z

Added non-breaking space to non-template file size, bitrate, and bandwidth values (via WP:JWB)

← Previous revision		Revision as of 09:51, 25 September 2024
Line 123:		Line 123:
	* [[Node.js]] with the hls-server package supports hls encoding to live mode and local files conversion.<ref>{{cite web\|url=https://www.npmjs.com/package/hls-server\|title=hls-server\|date=12 February 2018 \|publisher=npm}}</ref>		* [[Node.js]] with the hls-server package supports hls encoding to live mode and local files conversion.<ref>{{cite web\|url=https://www.npmjs.com/package/hls-server\|title=hls-server\|date=12 February 2018 \|publisher=npm}}</ref>
	* [[OvenMediaEngine]] is an [[Open-source software\|open source]] project that supports Low Latency HLS (LL-HLS) and HLS for live streaming.		* [[OvenMediaEngine]] is an [[Open-source software\|open source]] project that supports Low Latency HLS (LL-HLS) and HLS for live streaming.
			* [[PeerTube]] supports HLS
	*[[Storm Streaming Server]] supports HLS as backup mode for its Media Source Extensions player<ref>{{Cite web\|title=Storm Streaming\|url=https://www.stormstreaming.com/\|access-date=2021-07-30\|website=Storm Streaming\|language=en\|quote=Output devices: HLS, MPEG-DASH, WebSocket, RTMP}}</ref>		*[[Storm Streaming Server]] supports HLS as backup mode for its Media Source Extensions player<ref>{{Cite web\|title=Storm Streaming\|url=https://www.stormstreaming.com/\|access-date=2021-07-30\|website=Storm Streaming\|language=en\|quote=Output devices: HLS, MPEG-DASH, WebSocket, RTMP}}</ref>
	* [[Tata Communications]] [[Content delivery network\|CDN]] supports HLS for live and on-demand streams.		* [[Tata Communications]] [[Content delivery network\|CDN]] supports HLS for live and on-demand streams.

← Previous revision		Revision as of 07:23, 9 September 2024
Line 122:		Line 122:
	* [[Nimble Streamer]] supports HLS in live and VOD mode, Apple Low Latency HLS spec is also supported.		* [[Nimble Streamer]] supports HLS in live and VOD mode, Apple Low Latency HLS spec is also supported.
	* [[Node.js]] with the hls-server package supports hls encoding to live mode and local files conversion.<ref>{{cite web\|url=https://www.npmjs.com/package/hls-server\|title=hls-server\|date=12 February 2018 \|publisher=npm}}</ref>		* [[Node.js]] with the hls-server package supports hls encoding to live mode and local files conversion.<ref>{{cite web\|url=https://www.npmjs.com/package/hls-server\|title=hls-server\|date=12 February 2018 \|publisher=npm}}</ref>
			* [[OvenMediaEngine]] is an [[Open-source software\|open source]] project that supports Low Latency HLS (LL-HLS) and HLS for live streaming.
	*[[Storm Streaming Server]] supports HLS as backup mode for its Media Source Extensions player<ref>{{Cite web\|title=Storm Streaming\|url=https://www.stormstreaming.com/\|access-date=2021-07-30\|website=Storm Streaming\|language=en\|quote=Output devices: HLS, MPEG-DASH, WebSocket, RTMP}}</ref>		*[[Storm Streaming Server]] supports HLS as backup mode for its Media Source Extensions player<ref>{{Cite web\|title=Storm Streaming\|url=https://www.stormstreaming.com/\|access-date=2021-07-30\|website=Storm Streaming\|language=en\|quote=Output devices: HLS, MPEG-DASH, WebSocket, RTMP}}</ref>
	* [[Tata Communications]] [[Content delivery network\|CDN]] supports HLS for live and on-demand streams.		* [[Tata Communications]] [[Content delivery network\|CDN]] supports HLS for live and on-demand streams.

← Previous revision		Revision as of 16:48, 23 April 2024
Line 29:		Line 29:
	HLS resembles [[Dynamic Adaptive Streaming over HTTP\|MPEG-DASH]] in that it works by breaking the overall stream into a sequence of small HTTP-based file downloads, each downloading one short chunk of an overall potentially unbounded transport stream. A list of available streams, encoded at different bit rates, is sent to the client using an [[Extended M3U\|extended M3U playlist]].<ref>{{cite web\|url= https://larryjordan.com/articles/basics-of-http-live-streaming\|title= The Basics of HTTP Live Streaming\|last= Jordan\|first= Larry\|date= 10 June 2013\|work= Larry's Blog\|publisher= Larry Jordan & Associates\|access-date= 18 June 2013}}</ref>		HLS resembles [[Dynamic Adaptive Streaming over HTTP\|MPEG-DASH]] in that it works by breaking the overall stream into a sequence of small HTTP-based file downloads, each downloading one short chunk of an overall potentially unbounded transport stream. A list of available streams, encoded at different bit rates, is sent to the client using an [[Extended M3U\|extended M3U playlist]].<ref>{{cite web\|url= https://larryjordan.com/articles/basics-of-http-live-streaming\|title= The Basics of HTTP Live Streaming\|last= Jordan\|first= Larry\|date= 10 June 2013\|work= Larry's Blog\|publisher= Larry Jordan & Associates\|access-date= 18 June 2013}}</ref>

	Based on standard HTTP transactions, HTTP Live Streaming can traverse any [[Firewall (computing)\|firewall]] or [[proxy server]] that lets through standard HTTP traffic, unlike UDP-based protocols such as [[Real-time Transport Protocol\|RTP]]. This also allows content to be offered from conventional HTTP servers and delivered over widely available HTTP-based [[content delivery network]]s.<ref>{{cite web \|date=March 29, 2015 \|title=MPEG-DASH vs. Apple HLS vs. Smooth Streaming vs. Adobe HDS \|url=https://bitmovin.com/mpeg-dash-vs-apple-hls-vs-microsoft-smooth-streaming-vs-adobe-hds/ \|website=Bitmovin}}</ref><ref>{{Cite book \|last1=Chen \|first1=Songqing \|last2=Shen \|first2=Bo \|last3=Tan \|first3=Wai-tian \|last4=Wee \|first4=Susie \|last5=Zhang \|first5=Xiaodong \|title=2006 IEEE International Conference on Multimedia and Expo \|chapter=A Case for Internet Streaming via Web Servers \|date=2006-07-09 \|chapter-url=https://ieeexplore.ieee.org/document/4037057 \|pages=2145–2148 \|doi=10.1109/ICME.2006.262660 \|isbn=9781424403677 \|issn=1945-7871 \|eissn=1945-788X \|s2cid=9202042 }}</ref><ref>{{Cite journal \|last1=Songqing Chen \|last2=Bo Shen \|last3=Wee \|first3=S. \|last4=Xiaodong Zhang \|date=2007-07-23 \|title=SProxy: A Caching Infrastructure to Support Internet Streaming \|url=https://ieeexplore.ieee.org/document/4276704 \|journal=IEEE Transactions on Multimedia \|volume=9 \|issue=5 \|pages=1062–1072 \|doi=10.1109/TMM.2007.898943 \|s2cid=870854 \|issn=1520-9210\|citeseerx=10.1.1.74.4838 }}</ref> The standard also includes a standard encryption mechanism<ref>{{cite web\|url= http://tools.ietf.org/html/draft-pantos-http-live-streaming-07\|title= HTTP Live Streaming\|last= Pantos\|first= R.\|date= 30 September 2011\|publisher= Internet Engineering Task Force\|access-date= 18 June 2013}}</ref> and secure-key distribution using [[HTTPS]], which together provide a simple [[Digital Rights Management\|DRM]] system. Later versions of the protocol also provide for [[trick mode\|trick-mode]] fast-forward and rewind and for integration of subtitles.		Based on standard HTTP transactions, HTTP Live Streaming can traverse any [[Firewall (computing)\|firewall]] or [[proxy server]] that lets through standard HTTP traffic, unlike UDP-based protocols such as [[Real-time Transport Protocol\|RTP]]. This also allows content to be offered from conventional HTTP servers and delivered over widely available HTTP-based [[content delivery network]]s.<ref>{{cite web \|date=March 29, 2015 \|title=MPEG-DASH vs. Apple HLS vs. Smooth Streaming vs. Adobe HDS \|url=https://bitmovin.com/mpeg-dash-vs-apple-hls-vs-microsoft-smooth-streaming-vs-adobe-hds/ \|website=Bitmovin}}</ref><ref>{{Cite book \|last1=Chen \|first1=Songqing \|last2=Shen \|first2=Bo \|last3=Tan \|first3=Wai-tian \|last4=Wee \|first4=Susie \|last5=Zhang \|first5=Xiaodong \|title=2006 IEEE International Conference on Multimedia and Expo \|chapter=A Case for Internet Streaming via Web Servers \|date=2006-07-09 \|chapter-url=https://ieeexplore.ieee.org/document/4037057 \|pages=2145–2148 \|doi=10.1109/ICME.2006.262660 \|isbn=9781424403677 \|issn=1945-7871 \|eissn=1945-788X \|s2cid=9202042 }}</ref><ref>{{Cite journal \|last1=Songqing Chen \|last2=Bo Shen \|last3=Wee \|first3=S. \|last4=Xiaodong Zhang \|date=2007-07-23 \|title=SProxy: A Caching Infrastructure to Support Internet Streaming \|url=https://ieeexplore.ieee.org/document/4276704 \|journal=IEEE Transactions on Multimedia \|volume=9 \|issue=5 \|pages=1062–1072 \|doi=10.1109/TMM.2007.898943 \|s2cid=870854 \|issn=1520-9210\|citeseerx=10.1.1.74.4838 }}</ref> The standard also includes a standard encryption mechanism<ref>{{cite web\|url= http://tools.ietf.org/html/draft-pantos-http-live-streaming-07\|title= HTTP Live Streaming\|last= Pantos\|first= R.\|date= 30 September 2011\|publisher= Internet Engineering Task Force\|access-date= 18 June 2013}}</ref> and secure-key distribution using [[HTTPS]], which together provide a simple [[Digital Rights Management\|DRM]] system. Later versions of the protocol also provide for [[trick mode\|trick-mode]] fast-forward and rewind and for integration of subtitles.

	Apple has documented HTTP Live Streaming as an [[Internet Draft]] (Individual Submission), the first stage in the process of publishing it as a [[Request for Comments]] (RFC). As of December 2015, the authors of that document have requested the RFC Independent Stream Editor (ISE) to publish the document as an informational (non-standard) RFC outside of the [[IETF]] consensus process.<ref>		Apple has documented HTTP Live Streaming as an [[Internet Draft]] (Individual Submission), the first stage in the process of publishing it as a [[Request for Comments]] (RFC). As of December 2015, the authors of that document have requested the RFC Independent Stream Editor (ISE) to publish the document as an informational (non-standard) RFC outside of the [[IETF]] consensus process.<ref>
	{{cite web		{{cite web
	\|url= https://datatracker.ietf.org/doc/draft-pantos-http-live-streaming/history/		\|url= https://datatracker.ietf.org/doc/draft-pantos-http-live-streaming/history/
Line 80:		Line 80:

	The remainder of this section describes Apple's ALHLS. It reduces the glass-to-glass delay when streaming via HLS by reducing the time to start live stream playbacks and maintain that time during a live-streaming event.		The remainder of this section describes Apple's ALHLS. It reduces the glass-to-glass delay when streaming via HLS by reducing the time to start live stream playbacks and maintain that time during a live-streaming event.
	It works by adding partial media segment files into the mix, much like MPEG-CMAF's fMP4. Unlike CMAF, ALHLS also supports partial MPEG-2 TS transport files. A partial media segment is a standard segment (e.g. 6 seconds) split into equal segments of less than a second (e.g. 200 milliseconds). The standard first segment is replaced by the series of partial segments. Subsequent segments are of the standard size.<ref>{{Cite web \|title=Apple Developer Documentation \|url=https://developer.apple.com/documentation/http_live_streaming/enabling_low-latency_http_live_streaming_hls \|access-date=2022-08-10 \|website=developer.apple.com}}</ref>		It works by adding partial media segment files into the mix, much like MPEG-CMAF's fMP4. Unlike CMAF, ALHLS also supports partial MPEG-2 TS transport files. A partial media segment is a standard segment (e.g. 6 seconds) split into equal segments of less than a second (e.g. 200 milliseconds). The standard first segment is replaced by the series of partial segments. Subsequent segments are of the standard size.<ref>{{Cite web \|title=Apple Developer Documentation \|url=https://developer.apple.com/documentation/http_live_streaming/enabling_low-latency_http_live_streaming_hls \|access-date=2022-08-10 \|website=developer.apple.com}}</ref>
	HTTP/2 is required to push the segments along with the playlist, reducing the overhead of establishing repeated HTTP/TCP connections.		HTTP/2 is required to push the segments along with the playlist, reducing the overhead of establishing repeated HTTP/TCP connections.

Line 137:		Line 137:
	* [[Yospace]] added HTTP Live Streaming support in Yospace HLS Player and SDK for flash version 1.0.{{citation needed\|date=March 2019}}		* [[Yospace]] added HTTP Live Streaming support in Yospace HLS Player and SDK for flash version 1.0.{{citation needed\|date=March 2019}}
	* [[Sling Media]] added HTTP Live Streaming support to its [[Slingbox]]es and its SlingPlayer apps.<ref>{{cite web\|website=Blogcritics\|date=November 26, 2010\|url=https://blogcritics.org/ipad-app-review-slingplayer/\|title=iPad App Review: SlingPlayer\|first=David\|last=Chan\|access-date=April 14, 2014\|archive-url=https://web.archive.org/web/20140415025424/https://blogcritics.org/ipad-app-review-slingplayer/\|archive-date=April 15, 2014}}</ref>		* [[Sling Media]] added HTTP Live Streaming support to its [[Slingbox]]es and its SlingPlayer apps.<ref>{{cite web\|website=Blogcritics\|date=November 26, 2010\|url=https://blogcritics.org/ipad-app-review-slingplayer/\|title=iPad App Review: SlingPlayer\|first=David\|last=Chan\|access-date=April 14, 2014\|archive-url=https://web.archive.org/web/20140415025424/https://blogcritics.org/ipad-app-review-slingplayer/\|archive-date=April 15, 2014}}</ref>
	* In 2014/15, the [[BBC]] introduced HLS-AAC streams for its live internet radio and on-demand audio services, and supports those streams with its [[iPlayer Radio]] clients.<ref>{{Cite web\|url=https://www.bbc.co.uk/blogs/internet/entries/234a65f0-89c1-489c-b6e9-55d2de932e53\|last=Scott\|first=Andrew\|title=Audio Factory: an overview\|date=27 Feb 2015\|publisher=BBC\|work=Internet Blog\|quote=the only on-demand assets will be AAC HLS. ... We are still talking to manufacturers and many are confident that they will be able to provide their users with access to all 57 of our HLS AAC streams at ~~320kb~~/s within a few weeks or months.}}</ref>		* In 2014/15, the [[BBC]] introduced HLS-AAC streams for its live internet radio and on-demand audio services, and supports those streams with its [[iPlayer Radio]] clients.<ref>{{Cite web\|url=https://www.bbc.co.uk/blogs/internet/entries/234a65f0-89c1-489c-b6e9-55d2de932e53\|last=Scott\|first=Andrew\|title=Audio Factory: an overview\|date=27 Feb 2015\|publisher=BBC\|work=Internet Blog\|quote=the only on-demand assets will be AAC HLS. ... We are still talking to manufacturers and many are confident that they will be able to provide their users with access to all 57 of our HLS AAC streams at 320 kb/s within a few weeks or months.}}</ref>
	* [[Twitch (service)\|Twitch]] uses HTTP Live Streaming (HLS) to transmit and scale the live streaming to many concurrent viewers, also supporting multiple variants (e.g., 1080p, 720p, etc.).<ref>{{cite web\|url=https://blog.twitch.tv/en/2017/10/10/live-video-transmuxing-transcoding-f-fmpeg-vs-twitch-transcoder-part-i-489c1c125f28\|title=Live video transmuxing/transcoding: FFmpeg vs TwitchTranscoder, Part 1\|first=Yueshi\|last=Shen\|year=2017}}</ref>		* [[Twitch (service)\|Twitch]] uses HTTP Live Streaming (HLS) to transmit and scale the live streaming to many concurrent viewers, also supporting multiple variants (e.g., 1080p, 720p, etc.).<ref>{{cite web\|url=https://blog.twitch.tv/en/2017/10/10/live-video-transmuxing-transcoding-f-fmpeg-vs-twitch-transcoder-part-i-489c1c125f28\|title=Live video transmuxing/transcoding: FFmpeg vs TwitchTranscoder, Part 1\|first=Yueshi\|last=Shen\|year=2017}}</ref>