Reply to thread

Message

<blockquote data-quote="oldyellow" data-source="post: 419233" data-attributes="member: 17727">rnoorda, I know that this is a frustrating problem because I suffered from it also.&nbsp; Have you tried the registry fix that I am posting below (which is the same fix contained in the <a href="http://home.comcast.net/~exdeus/ati-hd2x00" target="_blank">ATI registry tweaks</a>?I am pretty sure that the problem is in how the VMR9 or EVR renderers are interacting with the video drivers.&nbsp; In <a href="https://forum.team-mediaportal.com/codecs-external-players-55/new-nvide-driver-fixed-black-level-problem-vmr9-me-59636/#post418953" target="_blank">this thread</a>, I posted a quick test that will demonstrate whether or not this is the issue.I strongly suggest that you (1) make sure that you go to ATI's support site and make sure you have the latest version of the drivers and (2) try the registry fix.I have use NVidea instead of ATI, and the suggested NVidea registry hack did not work for me.&nbsp; However, when I installed the latest driver (released on May, 8) - my problem was fixed.</blockquote>

[QUOTE="oldyellow, post: 419233, member: 17727"] rnoorda, I know that this is a frustrating problem because I suffered from it also. Have you tried the registry fix that I am posting below (which is the same fix contained in the [url=http://home.comcast.net/~exdeus/ati-hd2x00]ATI registry tweaks[/url]? I am pretty sure that the problem is in how the VMR9 or EVR renderers are interacting with the video drivers. In [url=https://forum.team-mediaportal.com/codecs-external-players-55/new-nvide-driver-fixed-black-level-problem-vmr9-me-59636/#post418953]this thread[/url], I posted a quick test that will demonstrate whether or not this is the issue. I strongly suggest that you (1) make sure that you go to ATI's support site and make sure you have the latest version of the drivers and (2) try the registry fix. I have use NVidea instead of ATI, and the suggested NVidea registry hack did not work for me. However, when I installed the latest driver (released on May, 8) - my problem was fixed. [/QUOTE]

Verification