Devices > Video Cards, Monitors, Televisions, and Projectors
JRiver x64 + madVR: Wrong Video Levels [Solved]
tij:
Alright ... which version of MadVR you are using?
Also ... are you using RO HQ or Custom for video mode.
Only thing I can think of happening is you were using Custom mode in x32 and use external MadVR (not one that packaged with MC) ... and your Custom setting did not transfer to your x64 install.
MC has no control over MadVR ... it cannot force MadVR to output in 0-255 if MadVR setting are 16-235
I admit I was a bit lazy ... but will try to reproduce your problem on my TV (will have to switch my HDMI on TV to limited)
If6was9:
OK thanks,
If you can replicate the problem, I can understand better ...
madVR latest 0.92.17 + latest build 113.
I use JRiver's internal madVR, in Red October HQ.
With the same settings and JRiver x32 no problem.
P.s.
Please also try FSE On/Off and Pause/Play
Thank you
tij:
Ok ... I am on Win10 1809 (17763.973) ... Nvidia driver 425.31 ... MC26 x64 ver 26.0.22 ... LG OLED E6 with HDMI set to BluRay (limited range)
I use d3d11 full windowed mode in MadVR
GPU set on full ... MadVR on full ... crushed black as expected (I use a greyscale pattern and large potion of dark parts are just black)
GPU set on full ... MadVR on limited ... greyscale pattern shows normal (no crushed blacks) ... pausing and resuming with keyboard has no effect on this ... pausing and resuming with mouse (brings MC OSD) has no effect on this
If I double click to make video play in detached window ... if window large enough no black crushing ... if I start to reduce window size, at certain point black become crushed (likely not MC problem but due to downscaling of MadVR)
In short, I cannot reproduce your problem.
Now ... I try to take a wild guess at your problem ... as I stopped using latest MadVR (not due to lack of knowledge but too lazy) ... my MadVR is what is provided with MC, which is 0.92.16.
As you using 0.92.17 and even latest 113 (which MC officially do not support) ... my guess is you did not replace copy of MadVR in MC folder, but running latest version separately (with MadVR icon in the system tray).
MC has it’s own MadVR copy that it uses and does not share with other programs. Only way to force MC to use latest MadVR is to replace MC copy of MadVR with latest.
Option for MadVR copy under MC is ONLY accessible from MC [option]->[video]->[MadVR setting (advance users only) ... or something like that] ... you must set limited range for MadVR there for MC
If you setting MadVR settings via tray icon, that’s MadVR that MC does not use (unless you use Custom video mode instead of RO HQ)
If6was9:
I think I found the problem!!! (at least I hope):
in madVR, Devices ---> Properties I have always set the bitdepth display to 8bit (my TV is native 8bit)
Moving it to "Auto" the problem disappears. ?
Even with FSE On / Off,
now the levels remain correctly fixed in 16-235
Edit:
The problem has disappeared permanently :)
Something has probably changed in madVR or in the replacement of the GPU with the new RX580.
The settings in madVR "devices" have always been the same for years.
Thanks again
henkeli:
Just want to share that I was having really annoying problems with RGB range changes & blacks/shadows being crushed and decided to set the GPU (5500XT) to YCbCr at 10bpc (PJ is 10-bit) which is the default Radeon SW setting for my rig: HTPC -> AVR -> PJ
Playing around with RGB Full all the way down the chain caused way more problems than the potential for color issues or banding or whatever as indicated in all the madVR advice threads. I have not noticed any such issues with my current setup of: madVR 0-255 -> GPU YCbCr 10bpc -> PJ HDMI Range Standard. As a bonus, I no longer have to restart movies or play around endlessly with gamma levels and HDR nits and on and on.
Something to note - when I connect my HTPC to my computer monitor (1440p 8-bit) the Radeon SW auto configures the GPU to be RGB Full 0-255.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version