admin 管理员组文章数量: 1086019
I built an application to launch each of the TV capture filters in a machine and run them in a graph to check they are still functional. I built this application because on Windows 10, an application crash in the course of development leaves the tuner hardware unusable. It needs the machine to be shut down and re-started to get the tuners back online, a simple re-start is not enough (probably a driver issue but its the same for three different card manufacturers). I notice that on Windows 7 and 8.1, the application completes four tuners in less than a second. On Windows 10, it takes over 5 seconds. This is a relatively simple DirectShow application.
The same code built in Windows 7 and Windows 10 results in the same behaviour. It is simple code, creating a graph, adding filters tuning the capture filter and running the graph. Destroy that graph and move on to the next filter in the iteration.
I also have a multiple tuner capture application that runs perfectly on Windows 7 and 8.1 but takes forever to launch on windows 10 and fails to run the graphs successfully. The processing takes much longer and the tuner stops delivering samples despite receivng successful receive results. It almost feels like each call to DirectShow is taking much longer. I have not timed each call but have timed the whole process, which confirms the processing time difference.
本文标签:
版权声明:本文标题:execution - TV reception, editing and replay written in DirectShow runs much slower on Windows 10 than windows 7 and 8.1 - Stack 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://roclinux.cn/p/1744097647a2533195.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论