Skip navigation
Nick Denic
Currently Being Moderated

problem with osmf and edgecast

May 3, 2010 2:36 AM


for past two weeks I desperately tried to use osmf with edgecast cdn, but without any result.


Since my client insist on osmf, "quick and easy" development turns to a never ending story.

Is there a way to get basic playback functionality without developing additional plugin for such a thing?


I already searched for solution, but except one guy who already notice edgecast problem with osmf, I couldn't find anything else.


Thanks in advance.

  • Currently Being Moderated
    May 3, 2010 8:26 AM   in reply to Nick Denic

    Could you send me (briggs at adobe etc.) an RTMP URL that I can try to connect to against EdgeCast?  Also, are you able to get this working with a plain NetConnection/NetStream approach (and if so, can you send me the code)?  Thanks!

    Mark as:
  • Currently Being Moderated
    May 3, 2010 1:28 PM   in reply to Brian Riggs

    It looks like EdgeCast URLs include the FMS application instance.  (Some CDNs include this, others don’t.)  The default OSMF behavior is to assume that the FMS application instance is not used, since this is the more common case.  To support the latter, use the StreamingURLResource.urlIncludesFMSApplicationInstance param, e.g.:


    var resource:StreamingURLResource = new StreamingURLResource("rtmp://myserver/mp4:mystream.mp4");

    resource.urlIncludesFMSApplicationInstance = true; = new VideoElement(resource);

    Mark as:
  • Currently Being Moderated
    May 3, 2010 4:08 PM   in reply to Nick Denic

    I think we (as in Adobe) are trying to standardize things that vary by CDN, so that player developers don't need to worry about the details.  This property for whether to use the instance or not is a good example.  For the things that truly must vary, CDN-specific plugins are a good solution.  Either way, the player developer ought to be isolated from the CDN-specific logic.  Clearly, we're not there yet.

    Mark as:
  • Currently Being Moderated
    Jun 3, 2010 1:25 PM   in reply to Nick Denic

    Yes, you may need to specify "urlIncludesFMSApplicationInstance to true for such url you are trying.

    Also if the url is a live (it seems a live by looking at your attempted url), you might want to set "StreamType" to LIVE or "LIVE_OR_RECORDED" depending on how your application does.



    Mark as:
  • Currently Being Moderated
    Feb 29, 2012 5:49 AM   in reply to Nick Denic

    Thanks a lot for this solution, i lost a lot of time with it.

    For those who wonder:

    If you want to use Flex 4 VideoPlayer (which is based on OSMF) with EdgeCast or any other CDN which add FMS App in URL for RTMP streaming:

    until its done properly in the SDK you can do that:


    var resourceFullURL:String = "rtmp://";  //For EdgeCast FMSAPP is your client ID

    var resource:StreamingURLResource = new StreamingURLResource(resourceFullURL);

    resource.urlIncludesFMSApplicationInstance = true;

    var videoElement:VideoElement = new VideoElement(resource);                       

    flexVideoPlayer.source = videoElement; // also work for VideoDisplay of course


    I also lost a lot of time trying to work with flv files so here is what i found:

    for the resourceFullURL of previous example:

    the base is always: "rtmp://"

    but you must add the following according to your video format:





    NO EXTENSION FOR FLV FILE! its stupid but it does not work if you add it. Of course your file on the server needs to have the extention!


    For HTTP streaming its more easy to use flex 4 VideoPlayer:

    flexVideoPlayer.source = " Extention";

    extention can be mp4, f4v, mov or flv without issues!

    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points