Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
10th October 2018, 10:27 | #53081 | Link |
Registered User
Join Date: May 2016
Posts: 197
|
I think there is something wrong with cropping in case upstream signalled cropping parameters in case of native DXVA2 decoding: Here is a sample file with 80 pixels of black bars at the top and at the bottom and a white rectangle in the middle which is a square when viewed with the right (i.e. non-anamorphic) aspect ratio. If I play this with DXVA2 native in MPC-BE, the pin info is as it should be:
Code:
- Connection media type: Video: dxva 1280x720 (16:7) 25fps AM_MEDIA_TYPE: majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71} subtype: MEDIASUBTYPE_NV12 {3231564E-0000-0010-8000-00AA00389B71} formattype: FORMAT_VideoInfo2 {F72A76A0-EB0A-11D0-ACE4-0000C0CC16BA} bFixedSizeSamples: 1 bTemporalCompression: 0 lSampleSize: 1382400 cbFormat: 112 VIDEOINFOHEADER: rcSource: (0,80)-(1280,640) rcTarget: (0,80)-(1280,640) dwBitRate: 0 dwBitErrorRate: 0 AvgTimePerFrame: 400000 (25.000 fps) VIDEOINFOHEADER2: dwInterlaceFlags: 0x00000081 dwCopyProtectFlags: 0x00000000 dwPictAspectRatioX: 16 dwPictAspectRatioY: 7 dwControlFlags: 0x0000a581 - VideoChromaSubsampling: 5 - NominalRange : 2 (16-235) - VideoTransferMatrix : 1 (BT.709) - VideoLighting : 0 - VideoPrimaries : 0 - VideoTransferFunction : 0 dwReserved2: 0x00000000 |
10th October 2018, 10:31 | #53082 | Link |
Registered User
Join Date: Mar 2009
Posts: 3,650
|
@blaubart
No issues here, if madVR had a bug like this I think it would've been found long before now, maybe your screen has different level settings depending on content if that's even possible? That's the only thing I can think of. |
10th October 2018, 10:41 | #53083 | Link | |
Registered User
Join Date: Aug 2016
Posts: 1,348
|
Quote:
You appear to have misremembered the conversation, I told you I didnt have any BT2020 vs BT709 settings, I only had WIDE and NORMAL settings for gamut and I told you I had it set to WIDE only for HDR. https://forum.doom9.org/showthread.p...07#post1854007
__________________
LG OLED EF950-YAM RX-V685-RYZEN 3600 - 16GBRAM - WIN10 RX 5700 - https://www.videohelp.com/software/madVR/old-versions |
|
10th October 2018, 10:44 | #53084 | Link |
Registered User
Join Date: Dec 2016
Posts: 212
|
Of course it's possible on every TV that allow you to manually force level settings or there are content presets like on Panasonics. I get proper levels output chain even if driver is set to output limited studio levels while MadVr outputs PC levels. (I suspect there are some precission losses in that case)
Last edited by mytbyte; 10th October 2018 at 10:50. |
10th October 2018, 10:49 | #53085 | Link |
Registered User
Join Date: Mar 2009
Posts: 3,650
|
Wasn't sure if any TVs did that, although I knew it would be possible, just not encountered it.
blaubart if you set your GPU output to limited levels and madVR to 0-255 does it fix your issue and display properly for each content type? |
10th October 2018, 12:02 | #53086 | Link |
Registered User
Join Date: Jun 2017
Posts: 155
|
@madshi
would it be possible to allow negative values for the "custom levels" setting, basically to cause some minor black crush?? The reason why I want to do that is that on quite a few UHD movies what should be black is just a hair above black. Just to give you an example, every fade to black and also the credits of the UHD version of Red Sparrow shows RGB values like 1,0,1 or 1,1,1 or 0,1,0. On my Oled in a pitch-dark room I can see this as a faint black glow. When using limited range in madVR I can just set the custom levels to something like 15.5 to 235 but I would rather keep the whole chain in full RGB. |
10th October 2018, 13:14 | #53087 | Link | |
Registered User
Join Date: Apr 2009
Posts: 42
|
Quote:
RGB -> 8 bpc - limited/full YCbCr 420, 422 and 444 - (limited grayed out) 420 - 8, 12 bpc 422 - 8, 10, 12 bpc 444 - 8 bpc Ok only if I set to RGB output and then open the TV's picture menu the option "HDMI Black Level - Normal/Low" is switchable. "Normal" means 16-235 and the complete desktop now washed out. Nvidia output limited/full has no more effect cause TV's input is limited. But now indeed madVR playing HDR "0-255" has correct black levels! But sorry I don't wanna live with a castrated TV forced to 16-235 8-Bit ! Would you? Last edited by blaubart; 10th October 2018 at 13:32. |
|
10th October 2018, 17:03 | #53088 | Link |
Registered User
Join Date: Oct 2017
Posts: 331
|
On a Samsung - what you are using - "Normal" is not 16-235. Low is. Normal is 0-255.
__________________
HOW TO-Kodi 2D-3D-UHD (4k) HDR Guide Internal & External Players W11 Pro 24H2 GTX960-4GB RGB 4:4:4 @Matched Refresh Rates 8,10,12bit KODI 22 MPC-HC/BE 82" Q90R Denon S720W |
10th October 2018, 17:38 | #53089 | Link |
Is this for real?
Join Date: Mar 2016
Location: Norway
Posts: 168
|
I can sort of confirm what blaubart is saying here. I have an LG C8 OLED connected to my HTPC, and I must set Black Level to High in my TVs menu or else the image is way too dark in dark scenes. This is with SDR content too. Doesn't matter is I use VLC or Media Player Classic Home Cinema(MPC-HC). So it can't be a MadVr problem I think.
__________________
My HTPC : i9 10900K | nVidia RTX 4070 Super | TV : Samsung 75Q9FN QLED |
10th October 2018, 17:50 | #53090 | Link |
Registered User
Join Date: Aug 2016
Posts: 1,348
|
on my LG EF950 OLED my chain is as follows - AMD GFX 4:4:4 FULL RGB 8 bit - MADVR 0-255 - TV "HIGH" - pretty sure this is correct.
Should be the same for HDR and SDR content.
__________________
LG OLED EF950-YAM RX-V685-RYZEN 3600 - 16GBRAM - WIN10 RX 5700 - https://www.videohelp.com/software/madVR/old-versions Last edited by mclingo; 10th October 2018 at 17:54. |
10th October 2018, 18:27 | #53091 | Link |
Is this for real?
Join Date: Mar 2016
Location: Norway
Posts: 168
|
Yes, but Black Level = Low works well with my Panasonic UB820 bluray player with SDR and HDR content. Not sure why it is different with a PC connected.
__________________
My HTPC : i9 10900K | nVidia RTX 4070 Super | TV : Samsung 75Q9FN QLED |
10th October 2018, 18:38 | #53093 | Link | |
Registered User
Join Date: Aug 2016
Posts: 1,348
|
Quote:
your UB820 will be sending a limted signed to your TV where you PC will be sending FULL RGB, hence the difference. SamuriHL - sorry missed your reply
__________________
LG OLED EF950-YAM RX-V685-RYZEN 3600 - 16GBRAM - WIN10 RX 5700 - https://www.videohelp.com/software/madVR/old-versions |
|
10th October 2018, 18:42 | #53094 | Link |
Registered User
Join Date: Oct 2017
Posts: 331
|
Because a dedicated player uses YCbCr and a PC uses RGB. YCbCr does not use 0-255. It uses 16-235. This is why smart displays have an 'auto' setting. To detect the input and adjust the output. This 'auto' adjustment defaults to 16-235 on my panel. I think panels are programmed around dedicated players. So are 'devices'. This introduces the havoc we PC users face.
__________________
HOW TO-Kodi 2D-3D-UHD (4k) HDR Guide Internal & External Players W11 Pro 24H2 GTX960-4GB RGB 4:4:4 @Matched Refresh Rates 8,10,12bit KODI 22 MPC-HC/BE 82" Q90R Denon S720W |
10th October 2018, 19:19 | #53095 | Link |
Registered User
Join Date: May 2004
Posts: 5,351
|
To deal with that issue on your PC, you could set madvr to 16-235 (limited), the GPU to RGB FULL, and the TV to auto. It SHOULD show correctly in that configuration.
__________________
HTPC: Windows 11, AMD 5900X, RTX 3080, Pioneer Elite VSX-LX303, LG G2 77" OLED |
10th October 2018, 19:38 | #53096 | Link | ||
Registered User
Join Date: Oct 2012
Posts: 7,926
|
why should you even use auto if it doesn't work and just runs at limited.
Quote:
for what ever reason is looks like needs limited range for HDR. Quote:
if set your GPU to full range RGB it will send full range RGB if your end device like it or not. |
||
10th October 2018, 19:56 | #53097 | Link | |
Registered User
Join Date: Apr 2009
Posts: 42
|
Quote:
Using RGB it is easy to double the effect (not recommended) - set GPU to RGB "full" and TV to "HDMI Black Level - Low" resulting in "blacker then black" and "whiter than white". @ all Unfortunately TV manufacturers give their HDMI levels randomly changing phantasy names. The one that sounds somehow lower, weaker is mostly 0-255. To find out which is which a grayscale is helpful. Unfortunately2, if everything is set wrong some +/- ticks at TV's brightness/contrast and covered. Only the differences remain - e.g. if madVR is playing 16-235 at non-HDR (although set to 0-255) and playing real HDR in real 0-255. Yes beat me but to my excuse - the differences are somehow tiny.. |
|
10th October 2018, 19:59 | #53098 | Link |
Registered User
Join Date: Oct 2017
Posts: 331
|
I don't. I use RGB - 4:4:4 - 0-256 everything software and hardware.
__________________
HOW TO-Kodi 2D-3D-UHD (4k) HDR Guide Internal & External Players W11 Pro 24H2 GTX960-4GB RGB 4:4:4 @Matched Refresh Rates 8,10,12bit KODI 22 MPC-HC/BE 82" Q90R Denon S720W |
10th October 2018, 20:20 | #53100 | Link |
Registered User
Join Date: Oct 2017
Posts: 331
|
__________________
HOW TO-Kodi 2D-3D-UHD (4k) HDR Guide Internal & External Players W11 Pro 24H2 GTX960-4GB RGB 4:4:4 @Matched Refresh Rates 8,10,12bit KODI 22 MPC-HC/BE 82" Q90R Denon S720W |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
|
|