locked
How can I unregister a custom decoder??

    Question

  • With MediaExtensionManager, I can register a custom decoder to the pipeline. How can I remove it to use the original inbox decoder??

    From description 3 under remark of http://msdn.microsoft.com/en-us/library/windows/apps/windows.media.mediaextensionmanager.aspx within MSDN, "The registration persists for the lifetime of the MediaExtensionManager instance". Does it mean that if I remove the instance of MediaExtensionManager, the related registration of custom decoder will unregister?? Under JavaScript, either I set the instance to "null" or delete it, the registration will still exist. Do I misunderstand the meaning of that description or there is any way I can unregister the custom decoder??

    Tuesday, March 13, 2012 5:53 AM

Answers

  • Hello Kenny & Hope,

    I've gotten a confirmation from our architect. Unregistering your codec, bytstream handler or scheme handler is not directly supported. The registrations are tied to the lifetime of the underlying Media Foundation platform components.

    If you are dealing with scheme or bytestream handlers you could have a back channel to tell these handlers to generate an error when connecting. This should cause the MF topology to try resolving with the in-box handlers.  

    Unfortunately with decoders there does not appear to be a workaround. If you try the same method above and have your decoder generate an error MF will likely just fail the connect and not try the in-box decoder.

    If you can give me a really strong business reason why you need this functionality I can request a design change. However it is not likely that they will be able to facilitate this major change this late in the development cycle.

    Thanks,

    James


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

    Saturday, March 17, 2012 1:15 AM
    Moderator

All replies

  • With MediaExtensionManager, I can register a custom decoder to the pipeline. How can I remove it to use the original inbox decoder??

    From description 3 under remark of http://msdn.microsoft.com/en-us/library/windows/apps/windows.media.mediaextensionmanager.aspx within MSDN, "The registration persists for the lifetime of the MediaExtensionManager instance". Does it mean that if I remove the instance of MediaExtensionManager, the related registration of custom decoder will unregister?? Under JavaScript, either I set the instance to "null" or delete it, the registration will still exist. Do I misunderstand the meaning of that description or there is any way I can unregister the custom decoder??

         I encounter the same question with you.
    Wednesday, March 14, 2012 5:56 AM
  • Hello Kenny & Hope,

    At this time there does not appear to be a way to unregister the codec. If you can provide a reasonable use case for this functionality I will talk with our Media Engine developers and see if they considered this scenario.

    Thanks,

    James


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

    Friday, March 16, 2012 1:04 AM
    Moderator
  • Hello Kenny & Hope,

    I've gotten a confirmation from our architect. Unregistering your codec, bytstream handler or scheme handler is not directly supported. The registrations are tied to the lifetime of the underlying Media Foundation platform components.

    If you are dealing with scheme or bytestream handlers you could have a back channel to tell these handlers to generate an error when connecting. This should cause the MF topology to try resolving with the in-box handlers.  

    Unfortunately with decoders there does not appear to be a workaround. If you try the same method above and have your decoder generate an error MF will likely just fail the connect and not try the in-box decoder.

    If you can give me a really strong business reason why you need this functionality I can request a design change. However it is not likely that they will be able to facilitate this major change this late in the development cycle.

    Thanks,

    James


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

    Saturday, March 17, 2012 1:15 AM
    Moderator