Good morning Martin,

Sorry for just getting back to you, it’s been a long few weeks.

I actually managed to get it work, as mentioned in my previous post, but ran into this again and it brings up a question actually.

I use Amazon Interactive video services for live streaming events. This works fine, no problems.

While live streaming our event, Amazon S3 serves multiple copies of our stream depending on device and internet connection. So we’ll see 1080, 720, etc.

IVS also records all of these different formats as it transcodes everything. So I end up with multiple copies of my event in hls recorded files. So in my S3 bucket, I’ll have a folder for each 1080, 720, 480, 360, etc. Each with it’s own playlist.m3u8.

As part of that I get a master m3u8 with all of these different version available. So, thinking that cloudfront can serve multiple versions(again depending on device and internet connection of the client) I’ve been feeding the master m3u8 into FV player. This works great under S3 but results in an hls js error when I do this with a cloudfront distribution.

So I’m curious if I misunderstand how this works when serving different resolutions to clients over cloudfront.

So far, what I’ve done now is just give FV player the 1080 url and it works fine.