Mark Raishbrook

It turns out the user hadn't reloaded the video after making the changes I suggested! So that's solved. Still no access to the full property page for VMR9 on Windows 10, however. Anybody else experiencing that?

The enhanced renderer gives an unexpected interface error, unfortunately.

And today someone has a video that only plays sound even though VMR9 is being used. The video section of the graph is: xxxx.avi (source) - AVI splitter - LAV video decoder - VMR9. Any ideas, anybody?

Thanks for the response, Michael. I don't think the codecs are the problem, though. Most of our users receive Netflix videos and they have the correct codecs and decoders installed on their system. This "sound but no image" problem suddenly started happening a few Windows 10 updates ago, so I guess a core DS file was changed. I've also noticed that the dreaded Microsoft DTV-DVD Video Decoder gets dragged into a lot of videos now, which makes it almost impossible to frame backward or forwards smoothly....

Over recent months, some of our users are reporting that they get sound but no image when opening certain video files in our software on Windows 10. By default, our application uses the standard video renderer, but it has an option to use the VMR9 instead and that usually solves the problem. So I have two questions. Firstly, is there a reason why the video renderer is no longer working in Windows 10? We have a solution, as I said, but I'd be interested to know why the "old" renderer seems to have...