[WiP] madVR support in MP1 (8 Viewers)

[GeYe]

@joecrow Which color settings are right, is nearly a question after the right religion . In doom9 the most HTPC talk about Full RGB is right thing, in other parts of the internet ycbcr 4:4:4 is the best, especially for blue ray content. For me i tested and calibrated the picture on the LG with playing files by usb as best it can go without calibration hardware. And then looked which of the the modes is near that. To avoid a lot of conversions lav is set to pass through the color settings and madvr to 0-255. Would be a shame to loose black on an OLED

But it has nothing to do directly with HDR or 4k and is on my todo list, to investigate further if i have more time.

@Sebastiii here my test results:
Option not checked: flickering GUI, channel changes fast 2 - 3s
Option checked, 1 frame: no flickering GUI, channel changes fast 2 - 4s
Option checked, 2 frame: no flickering GUI, channel changes fast 2 - 4s
Option checked, 3 frame: no flickering GUI, channel changes 3 - 5s.
Option checked, 4 frame: no flickering GUI, rest quite similar to 3 frame.

Shortly after start channel changes are ok, the longer i look tv on a single channel (tested from 10 minutes to 1h), the longer the next change will last. And sound is coming often after the normal change time (2-5s) with black sceen and normal picture after 15s. Could realise the problem with setting 1 frame and 3,4 frame. 2 frame not checked long enough.

 

[Kotik]

If we trust madshi / nevcairel (i think we all do) then full rgb is the way to go. Both of them mentioned it in the past that if a tv supports full rgb input then this is the way to go for htpc users. The reasons are many but tldr is that with full rgb we avoid unnecessary conversions done by either our gpu or our tv (in both cases these conversions are poorly done) and let madvr do the conversion with high prescision.

Sent from my GT-I9100 using Tapatalk

 

[GeYe]

I trust madshi With my old amd i also had full rgb, with new one with ycbcr 4:4:4 the picture was for me a bit better, but will give full rgb a new try if i have a bit more time.

 

[Sebastiii]

@GeYe / @Kotik

I have asked Madshi for flickering and send some of my screenshot to him

So could be nice to have your screenshot too with madVR stats on screen (ctrl+J)

On my side, GPU is used like you explain @Kotik with 100% usage but i was able to trigger flickering with lower GPU usage too.

From Madshi answer, It's pretty simple: If the render queue is empty, that means that the GPU can't keep up with rendering.
That seems to be what's happening on my PC.
I was having some setting enable like 'Catmull-Rom' so i have changed to DXVA downscaling and it was better.

My source was 1080i50 source (TV one), when i have tested a 24fps Blu-Ray the flickering was near to be done.

Those tests was on my HD4000 and TVGuide flickering, i didn't try on my laptop for now.

So for testing and grab some screenshot, we need to have 'low latency option' checked :

So if i follow correctly flickering could be related to not enough power GPU (Video + GUI Engine).

 

[Kotik]

U are a beast @Sebastiii, i wanted to suggest to u yesterday to maybe send a report to him since it will be more official this way (from a dev to a dev) but then i thought that maybe u got other plans in ur head so i decided to create a bug report myself In any case i will wait with it now until @madshi replies to u (i hope with good news).

P.S. I will create screenshots i can even create a video if u want. It is not about render queues being empty, it is about power states jumping up and down. I can trigger it with DXVA aswell. So my render times are exetremely low, something like 4ms total with DXVA .

 

[daWooky]

radio fixed
and my problem wiht the subs where homemade -xysubfilter it was configured to always load

@rohnfe about 3d upscaled 4k input -im not sure but i remember vaguely only 2k is possible at present, maybe u ask the lg support
nice oled btw

 

[rohnfe]

@rohnfe about 3d upscaled 4k input -im not sure but i remember vaguely only 2k is possible at present, maybe u ask the lg support
nice oled btw

Right you cant pass 3D in 4k to the TV as HDMI does not support it by now and officialy there is no 4K 3D standard as far as i know but if you are using a 4K TV and pass 1080p 3D to that TV it will upscale to 4K as it would do with any other file as well. Thats why passive 3D for example on a LG OLED looks that fantastic because you wont notice the halved resolution as it is still 1080p:

PC: 1080p 3D -> TV: upscaled to 4K -> halved 4K throught passive 3D = 1080p 3D

At least it should work that way for LG OLED 4k passive 3D TV´s if i am not totaly wrong.
And you don´t have the disadvantages of active shutter 3D.

Btw. i already tried to have 3D upscaled to 4K using madvr but it will destroy 3D at least for framepacked files. It might/will work for SBS 3D i guess...

 

[Sebastiii]

Hey
V209 in first post, i have try to directly doing a stop when stopping maybe it will avoid the last frame showing when changing channel @Kotik but i'm not very sure of that

 

[Kotik]

Will test it after work and let u know.

 

[joecrow]

@Sebastiii v209 looks good so far but I have not noticed any improvement when changing TV channels, I do think OV looks cleaner on stop (the menu used to flash up briefly between black screens before eventually displaying normally).
I have been able to reproduce my non resetting 23hz refresh rate after playing 3D. After the clean install test of the RX 460 when I reinstalled my old HD 6670 I also installed the appropriate AMD Catalyst drivers (15.7.1) for it and the problem does not occurr. If, however, I install the AMD Crimson driver package (a beta) for the HD 6670 the problem happens every time, although I have again confirmed that MPC-HC (x64) does handle it correctly. The Crimson driver package is used on the newer AMD GPUs (e.g. RX series) and I did note that the package includes/installs a "Microsoft Visual C++ (2012) Redistributable (x86)". Uninstalling the Crimson drivers with DDU and re-installing the Catalyst drivers cleared the problem again.