![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Check that please: solved my blackouts/no signal: YFI: In my case I also thought it's the cable, however it turned out that intermittent blackouts where caused by a setting in Nvidia Control panel in the scaling section. Make sure scaling is set to "display" not "gpu"
Thanks for the info. I do have RGB 10 bit full range in NVCP. And my Black Level is also set to Auto in the TV and Dynamic Tone Mapping OFF on both madVR and TV. It's just weird how the stat is staying "NV, 8bit, 4:2:0" under "D3D11 fullscreen windowed (10 bit)". As for the BT.709 thing, I'm not even sure what it is anymore. I previously thought it should be BT.2020, but I checked my TV and I have Gamma set to 2.2 (not any of the BT.XXXX stuff), as per rtings recommended settings.
One of the filters in the playback chain is not reporting the metadata correctly. That's what it means when you see "best guess" in madVR. It could be a decoder, or intermediate video processing filter. MPC-HC is obsolete - use MPC-BE.
Passthrough of HDR metadata does not work in any player, period. You must use a HDR-aware renderer like madVR with MPC-BE to output BT.2020 PQ and manually set the HDMI signal parameters on the TV based on the content you're watching or the TV will use the wrong tone mapping curve. Alternatively you can leave the TV in HGIG mode for the most accurate image. Use madVR's tone mapping to 800 nits in HGIG mode if you want to preserve highlights instead of hard clipping.
Hello, I'm not native so I hope you can forgive some of my yoinky phrasings.
Turn out I already had this set
I assume you're not unplugging the TV but turning it off with the remote. Also make sure you have quickstart+ enabled, I suspect this keeps the hdmi link active since it just goes into suspend mode.
Thank you, I already have HW acceleration disabled as I already had trouble with it in the past
This is really strange! I don't have any dropouts at all. But it seems like it is happening to a few people.Thank you, I already have HW acceleration disabled as I already had trouble with it in the past
FYI my Monoprice cable works perfectly at 4K/120/10bit/RGB with GSync. Really nice to have everything working with this screen.
It mentions "Stadia" in the gaming section. Is it built-in?
Thanks. That was it. After hours of testing with MPC-HC+madVR, MPC-BE+madVR, Kodi (HDR version), I found the issue for me. The reason I'm getting "best guesses" and "BT.709" was because of an external filter I added to MPC-HC aka "ffdshow raw video filter". I needed to add this to MPC-HC for my SVP Pro to work. When playing the HDR movie using MPC-BE+madVR (which didn't have this external filter added) or Kodi, I'm getting correct passthrough HDR stats (I'm assuming...see pic below). Guess now I gotta keep a separate player for HDR movies or research into Smart Share like sharknice said.
The 4000-nit curve results in reduced clipping, not more clipping, by reducing peak brightness and rolling off above 480 nits. Washed out colours are due to a broken decoder chain not reporting BT.2020 PQ - that has nothing to do with HDR.
Use the new AviSynth beta filter in SVP Pro in the installer, and uninstall ffdshow. It works with HDR in MPC-BE.
#
# THIS FILE WILL BE OVERWRITTEN WITH THE PACKAGE UPDATE
# Use %APPDATA%/mpv/mpv.conf
# OR SVP's menu -> Information -> Add. information -> mpv config. file
# to define your own customized configuration
#
# Sample mpv configuration
#
# this is required for SVP to "catch" the mpv
input-ipc-server=mpvpipe
# hardware video decoder
hwdec=d3d11va
hwdec-codecs=all
vo=gpu
gpu-api=d3d11
gpu-context=d3d11
# high quality video output, require rather fast video card
profile=gpu-hq
# use ANGLE if you have problems with default d3d11 renderer
# gpu-context=angle
# OR the newest VULKAN API
# gpu-api=vulkan
# miscellaneous options
# fixes audio desync
hr-seek-framedrop=no
# this can't be used with SVP cause it also saves vf's states
save-position-on-quit=no
# "ReClock" replacement
# video-sync=display-resample
# video-sync-max-video-change=5
#log-file=mpv.log
ao=wasapi
# audio-exclusive
audio-spdif=ac3,dts,dts-hd,eac3,truehd
audio-channels=auto
# icc-profile-auto
The curves are arbitrarily decided by LG and don't follow a standard roll-off. There does exist the BT.2390 standard for tone mapping which madVR supports (when using HGIG mode).