View Single Post
Old 11th April 2019, 14:52   #55685  |  Link
huhn
Registered User
 
Join Date: Oct 2012
Posts: 7,926
@Manni

as long as no other user group reproduces the problem you should assume your end device first.
more then try to reproduce is is not possible for me.
i blamed mclingos screen first too.

@If6was9
i'm over this topic
i'm using 8 bit myself. i'm recommending it for quite sometime but...

if TV processing would be flawless we wouldn't get any issues.
every TV in theory can do the same as madVR. that doesn't change that 10 bit has to work properly.

edit: AFAIK the AMD HDR API needs 10 bit input. that doesn't stop you from sending 8 bit to the display but you have to use 10 bit rendering which creates this bug if i see this correctly.
@Sunset1982

can you please try the "compatibility" FSE mode.
mpc-hc64.exe -> right click properties -> compatibility -> disable full-screen optimisations. just as a warning my TV/driver/windows version combination was happy about this to say it friendly so use it at your own risk... my desktop PC was fine with that.

Last edited by huhn; 11th April 2019 at 15:01.
huhn is offline   Reply With Quote