2018-11-03, 18:45
(2018-11-03, 17:18)Warner306 Wrote: I don't know why you are always blowing your top over these bug reports. I was just trying to be helpful. You could simplify your explanation to AMD as to what is wrong.whos blowing their tops?, I even stated clearly it wasnt your fault, I think you are misreading some of my posts, i'm not angry with you at all, far from it.
Can you run the following quick tests:
- Direct3D 11 + madVR (8-bit) + BT.709 + AMD (8-bit) = normal/not normal
- Direct3D 11 + madVR (10-bit) + BT.709 + AMD (8-bit) = normal/not normal
- Direct3D 11 + madVR (8-bit) + BT.709 + AMD (10-bit) = normal/not normal
- Direct3D 11 + madVR (10-bit) + BT.709 + AMD (10-bit) = normal/not normal
This should tell you whether madVR is involved at all. The media player and GPU will operate independent of each other.
here are the results.
- Direct3D 11 + madVR (8-bit) + BT.709 + AMD (8-bit) = normal
- Direct3D 11 + madVR (10-bit) + BT.709 + AMD (8-bit) = not normal - very red
- Direct3D 11 + madVR (8-bit) + BT.709 + AMD (10-bit) = normal
- Direct3D 11 + madVR (10-bit) + BT.709 + AMD (10-bit) = not normal - very red
I