Hello,
We are considering moving to HLS but the best option would be to use HLSv4 with single TS file and byte range mapping.
Why that? Because it's much easier to manage two files (m3u and .ts) than an "unlimited" number of files per video.
Do you have any plan to support it in the next release?
Thanks.
Currently we do not have plans to support this method of streaming. If too many files is a concern, can I ask why MP4 would not be utilized here?
Well for us the combination of HLS + HTML5 streaming is the best because with only two formats we are able to serve all different kind of users from IE8 to Chrome42 and mobile users.
Managing tons of files for HLS (on S3/CloudFront) is at the end more difficult than only one file like we do for the HTML5 streaming.
You could argue that RTMP could be suitable instead of HLS but RTMP pause so many problems (firewall, proxy, https etc.) and I would prefer to bet on the futur with HLS than the past with RTMP..
Thanks.
Thanks for the insight. I’ll pass this back over to our team, but again, there are no plans so support this at this time.
MAJOR +1 for hlsv4.
Now that Amazon added signed cookies, I'm trying to move over to HLS. Just realized that you don't support v4 yet. MASSIVELY easier to manage a large file set with only 3 files per video (ts,iframe m3u8, index m3u8) rather than to have to manage hundreds of files for every variant speed of every single video.
Thanks Andrew, I really think this will ease many developers work to adopt HLS.
Of course! If this keeps surfacing as a request/trend in the industry, this may indeed be something that we gravitate towards.
