An automated reference implementation leveraging AWS Step Functions and AWS Media Services to deploy a scalable fault tolerant Video on demand workflow
I really like this solution, but I'm stymied by the fact that desktop browsers do not (generally) natively support the m3u8 file standard.
That being the case, wouldn't it be easier to simply load all my files in m4v format into an S3 bucket and access them from there? In other words, I could just have static files in S3 and get the same result but with the added assurance that most browsers will understand the file format.
Or, are there other things your solution provides that make it worthwhile even if I have to tinker with desktop browsers to get them working?
I hope this all makes sense. I would love to justify keeping your solution. But if I can just serve up the files via S3, I'll have to go that route.
gamename
commented
11 months ago
I really like this solution, but I'm stymied by the fact that desktop browsers do not (generally) natively support the
m3u8file standard.That being the case, wouldn't it be easier to simply load all my files in
m4vformat into an S3 bucket and access them from there? In other words, I could just have static files in S3 and get the same result but with the added assurance that most browsers will understand the file format.Or, are there other things your solution provides that make it worthwhile even if I have to tinker with desktop browsers to get them working?
I hope this all makes sense. I would love to justify keeping your solution. But if I can just serve up the files via S3, I'll have to go that route.
Thanks, -T