locked
MF_MEDIA_ENGINE_ERR_SRC_NOT_SUPPORTED : HRESULT - 0x80004005 when trying to play MPEG-DASH

    Question

  • Hi

    When trying to play back MPEG-DASH content that is packaged using the Live profile as it should be. I am receiving MediaFailed from the MS player framework, with the error: MF_MEDIA_ENGINE_ERR_SRC_NOT_SUPPORTED : HRESULT - 0x80004005 

    This even though the content is playable without problems using the dashjs reference player available here: http://dashif.org/reference/players/javascript/1.2.0/index.html

    What are the cause of that error?

    Wednesday, October 08, 2014 1:58 PM

Answers

  • Hello,

    Matt asked me to take a look at this for you. Unfortunately I don't know anything about the Player Framework. The error you reported usually indicates that the Media Engine can't automatically determine the proper source to load. The Player Framework is likely providing a MediaStreamSource that is not getting loaded properly or is generating an internal error causing the Media Engine to try and find a more suitable source. In this case there isn't a more suitable source and the Media Engine is throwing the error you are reporting.

    I would recommend that you post on the "discussions" tab of the Payer Framework page you referenced. The MS Open Tech guys are usually pretty good at responding.

    I hope this helps,

    James


    Windows SDK Technologies - Microsoft Developer Services - http://blogs.msdn.com/mediasdkstuff/

    Thursday, October 09, 2014 8:50 PM
    Moderator

All replies

  • How exactly are you playing the content?

    Matt Small - Microsoft Escalation Engineer - Forum Moderator
    If my reply answers your question, please mark this post as answered.

    NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined objects and unknown namespaces.

    Wednesday, October 08, 2014 8:02 PM
    Moderator
  • Hi Matt

    I am using the sample from http://playerframework.codeplex.com/ (the C# version). Where i use the DashPage.xaml, and modified the streaming url to the one i wanted to use. I then hooked up an event listener to MediaFailed in order for me to extract the error info. Do you need the actual source?

    Thursday, October 09, 2014 7:09 AM
  • I'll ask our media guy to check this out.

    Matt Small - Microsoft Escalation Engineer - Forum Moderator
    If my reply answers your question, please mark this post as answered.

    NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined objects and unknown namespaces.

    Thursday, October 09, 2014 1:22 PM
    Moderator
  • Hello,

    Matt asked me to take a look at this for you. Unfortunately I don't know anything about the Player Framework. The error you reported usually indicates that the Media Engine can't automatically determine the proper source to load. The Player Framework is likely providing a MediaStreamSource that is not getting loaded properly or is generating an internal error causing the Media Engine to try and find a more suitable source. In this case there isn't a more suitable source and the Media Engine is throwing the error you are reporting.

    I would recommend that you post on the "discussions" tab of the Payer Framework page you referenced. The MS Open Tech guys are usually pretty good at responding.

    I hope this helps,

    James


    Windows SDK Technologies - Microsoft Developer Services - http://blogs.msdn.com/mediasdkstuff/

    Thursday, October 09, 2014 8:50 PM
    Moderator
  • Even though the Player Framework claims to support MPEG-DASH via the DashDownloaderPlugin, I do not think the framework actually supports true DASH content (.m4s for mp4 containers or .ts for MPEG-2 containers).

    All of the example URIs MS provides for testing "Dash" content contain the .ism extension -- which is actually associated with MS Smooth Streaming content (.ismv), not MPEG-DASH. But because Smooth Stream content is similar to DASH in that .ismv files are simply fragmented MP4 files, just the same as DASH .m4s files, it is possible to ‘trick’ a server into delivering .ismv files to any Dash client by simply creating DASH init segments and a MPD. I believe this is what Microsoft Azure does in delivering "Dash" content via their Dynamic Packager if you provide them with a Smooth Stream. 

    This means the Player Framework can play Smooth Stream content packaged as "Dash", for example: 

    http://wams.edgesuite.net/media/SintelTrailer_Smooth_SeekDemo/sintel_trailer-1080p.ism/manifest(format=mpd-time-csf) 

    but it cannot play true MPEG-DASH content, for example:

    http://dash.edgesuite.net/dash264/TestCases/1a/netflix/exMPD_BIP_TC1.mpd

    References:

    Building "Dash" A/V Apps w/ Player Framework

    Serving "Dash"with IIS

    Azure Streaming

    Test Content URLs



    • Edited by Paul Martel Thursday, April 23, 2015 9:07 PM format for clarity
    • Proposed as answer by Paul Martel Thursday, April 23, 2015 9:08 PM
    Thursday, April 23, 2015 8:58 PM