Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

adaptive streaming for hds

Hi there.

I'm using Amazon and Adobe Media Server to stream live events. In Amazon's manual, they say to use OSMF player for the .f4v manifest that they provide. OSMF hasn't been updated since 2012 and I would like to have one player for all stream types. From what I understand, JW Player 6 does NOT support HDS (only with Akamai).

I have followed the instructions here (settings are for one stream at 800K High Bandwidth:

In livepkgr's Manifest.xml it says this:
<manifest xmlns="">
<media streamId="livestream1" bitrate="100" />
<media streamId="livestream2" bitrate="200" />
<media streamId="livestream3" bitrate="350" />

Seeing that I think to myself, Adobe Media Server must support adaptive streaming for rtmp automatically (aka I don't have to push multiple streams in FMLE). If AMS indeed automatically has adaptive streaming (f4m) then can I take that f4m manifest and write it as a .smil? I know you support .smil files. I tried to do this but it wasn't adaptive. It did not support livestream1, livestream2, livestream3. It only played with livestream. Aka no adaptive streaming.

This is my smil:
<meta base='rtmp://' />
<video src='mp4:livestream1.f4m' height='720' system-bitrate='700000' width='1280' />
<video src='mp4:livestream2.f4m' height='360' system-bitrate='400000' width='640' />
<video src='mp4:livestream3.f4m' height='180' system-bitrate='150000' width='320' />

Like I said, If I were to change the first value to mp4:livestream.f4m it works (aka now adaptive). Any ideas how to support f4m in the JWPlayer?

1 Community Answers


JW Player Support Agent  
0 rated :

Is there any way that you can provide a link to this setup? Since you are using RTMP as a base for your F4M files, this is likely why things are working here. Regardless, as you’ve stated, we do not have support for F4M Natively within the player. Smil files also will not function adaptively, but will rather choose a quality “starting point” when loading initially.

This question has received the maximum number of answers.