媒体基础中转码与源阅读器+宿作者之间的表现 [英] the performance between transcode and source reader+sink writer in media foundation

问题描述

大家

 当我写了一个媒体转换器应用时，我发现了一件有趣的事情。我发现Transcode API的性能或

MediaTranscoder

class比source reader + sinkwriter好。这两种架构有什么不同。

谢谢。 

解决方案

< blockquote>

您好，

MediaTranscoder使用MF Transcode API，而这些API又使用Media Session。 Source Reader和Sink Writer不使用媒体会话。

确保您传递的是" MF_READWRITE_ENABLE_HARDWARE_TRANSFORMS "你的水槽作家的旗帜。

我希望这有帮助，

詹姆斯

hi all

 I found a interesting thing when I wrote a media converter app. I found the performance of Transcode API or

MediaTranscoder

class is better than source reader+sinkwriter. What's the different between this two architecture.

Thanks. 

解决方案

Hello,

The MediaTranscoder uses the MF Transcode APIs these in turn use the Media Session. The Source Reader and Sink Writer do not use the Media Session.

Make sure that you are passing the "MF_READWRITE_ENABLE_HARDWARE_TRANSFORMS" flag to your Sink Writer.

I hope this helps,

James

这篇关于媒体基础中转码与源阅读器+宿作者之间的表现的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！