madVR - high quality video renderer (GPU assisted)

[Siso]

Originally Posted by huhn

as long as you are not dropping frames just ignore it.

Thanks for the info, huhn.

[clsid]

Originally Posted by Morku

I also noticed, that when it changes from "fullscreen windowed" and "windowed" also changes between 10 bit and 8 bit. Maybe this is also causing the lag? There is no bit information in D3D9 (new path).
Any way to keep it 10 bit in windowed? Or 8 bit in fullscreen windowed to test?

In the devices section of madVR settings you can specify the native bitdepth of the screen. Try setting that to 8-bit.

[Ejziponken]

@madshi any chance we get an update that fixes the new Nivida API and HDR?

[Morku]

@clsid

Ah, found it. It stays in 8 bit when fullscreen windowed or just windowed. Okay, but unfortunately this is not the root of my issue, the frame drops are still. So the change between 8 bit and 10 bit is not the issue :\

[huhn]

try to disable the IGPU in the bios for a test if that system allows that.

your system may just switch between the GPU when the 3D application stops using full screen.

another thing you can try is forcing a GPU to run with MPC-HC.

what so ever you get rendertimes that are clearly not normal and that may explain it.

[SamuriHL]

Originally Posted by Ejziponken

@madshi any chance we get an update that fixes the new Nivida API and HDR?

That is extremely unlikely any time soon. He is focused on launching the Envy. He had popped into the AVS thread a few weeks ago and said a new build was maybe going to drop "in a few weeks" but then came back and said he was being overly optimistic. And that new beta build is very unlikely to fix this problem even when it does eventually drop. So, we either live with the problem or stick with older drivers for now.

[Morku]

@huhn
The BIOS allows me to disable the Intel GPU. But the result... is the same.

I also tried to set MPC-HC to use only Intel GPU, but the result is even worse with AMD. Still, I think AMD is always responsible for video out. You can't disable it. So at least one more confirmation that I think it is a AMD hardware/driver bug in relation to Windows OS.

Sure, with high rendertimes, the result are frame drops. But I still don't know what's the cause (and why there is no issue in Vista mode...).

When I set the task-manager on front, there is also no issue. So to fix the issue, "something" have to be displayed to keep Windows GUI busy (a 1x1 invisible pixel would be nice...?).
And since the issue is also with other videoplayers, like the Netflix App (navigation bar fade in and out) or with Microsoft Movies & TV, it is unrelated to a software or madVR. But all have "something" in common.

I created a new short video to summarize and show a little more detailed (with OSD): https://www.dropbox.com/s/axk0p9ois7...oppy5.mp4?dl=0

[Dogway]

What is the meaning of HDR peak white for an SDR HDTV calibrated to 48nits? Does that mean diffuse white is 48nits, or is that the peak white?

[Alexkral]

Originally Posted by Dogway

What is the meaning of HDR peak white for an SDR HDTV calibrated to 48nits? Does that mean diffuse white is 48nits, or is that the peak white?

For SDR diffuse white and peak white mean the same.

[Dogway]

Originally Posted by Alexkral

For SDR diffuse white and peak white mean the same.

Is that how the BT2390 tonemapper works? compressing peak white to diffuse white?

EDIT: So where it says Target Peak Nits I should input 48nits? It doesn't allow any lower than 100nits which is only valid for surrounds of 5 nits -not dark surrounds-.

[Obveron]

Hi there, I'm wondering if someone might be able to point me in the right direction here. I'm trying to get 3d framepacking working.
I have Nvidia 3d 1080p/24 framepacking mode automatically being enabled when I start a 3d file. However the content is being displayed in Side-by Side mode rather than frame alternating.

my display output is set to auto, the renderer settings are set to output 3d. I'm definitely using the LAV MVC filter.
It seems to be actually mostly working, my TV is going into 1080p framepacking mode properly, the MVC stream must be decoded properly but it's showing in side-by-side mode for some reason. I can select other display outputs like over under etc and they work too, but I can't get it to output as framepacked even though my TV is going into framepacked mode just fine.


one thing to note, I had to uncheck 'use DX11 for presentation' or it would outright crash the player when opening the file.

Windows 10 1803
MPC-HC 1.9.6.7
LAV Filters 0.74.1
madVR 0.92.17
Nvidia 441.08 with 3D vision injected
RTS 2060 Super
9700k


Thanks.

[Alexkral]

Originally Posted by Dogway

Is that how the BT2390 tonemapper works? compressing peak white to diffuse white?

EDIT: So where it says Target Peak Nits I should input 48nits? It doesn't allow any lower than 100nits which is only valid for surrounds of 5 nits -not dark surrounds-.

SDR should be calibrated to 100-120 nits, this way with BT.2390 a 10000 nits HDR peak white is mapped to 100 nits, and 100 nits are mapped to around 48 nits. If the HDR peak white is less than 10000 nits the compression is also less, for example, if it equals 1000 then 100 nits are mapped to around 69 nits.

[JarrettH]

Interesting measurements!

Where did the idea of using NGU AA for chroma originate? It was so long ago. I remember it reportedly still being very sharp.

[huhn]

it comes from testing images.

NGU AA super seeded nnedi3 by been mostly faster and better with similar strong points and weak points.

[Dogway]

Originally Posted by Alexkral

SDR should be calibrated to 100-120 nits, this way with BT.2390 a 10000 nits HDR peak white is mapped to 100 nits, and 100 nits are mapped to around 48 nits. If the HDR peak white is less than 10000 nits the compression is also less, for example, if it equals 1000 then 100 nits are mapped to around 69 nits.

That means I need two calibrations one for SDR content (48 nits) and another for HDR (100 nits), and play with TV brightness settings... Not convenient. Also films mastered at 10000 nits are rare, specially < 2010 titles.

If you are in a black box (dark surround) diffuse white should map to 48 nits, 100 nits is for mastering or dim surrounds (link1, link2).

I will ask madshi if he can allow lower target peaks, or better yet allow diffuse white mapping instead of target peak. This way we can lower SDR content from 100 nits to 48 within madVR, and do the same (via a profile group) with HDR content.

[Siso]

Is upgrading from GTX 1050 Ti to GTX 1660 Ti a good option for madvr?

[Obveron]

Originally Posted by Obveron

Hi there, I'm wondering if someone might be able to point me in the right direction here. I'm trying to get 3d framepacking working.
I have Nvidia 3d 1080p/24 framepacking mode automatically being enabled when I start a 3d file. However the content is being displayed in Side-by Side mode rather than frame alternating.

my display output is set to auto, the renderer settings are set to output 3d. I'm definitely using the LAV MVC filter.
It seems to be actually mostly working, my TV is going into 1080p framepacking mode properly, the MVC stream must be decoded properly but it's showing in side-by-side mode for some reason. I can select other display outputs like over under etc and they work too, but I can't get it to output as framepacked even though my TV is going into framepacked mode just fine.


one thing to note, I had to uncheck 'use DX11 for presentation' or it would outright crash the player when opening the file.

Windows 10 1803
MPC-HC 1.9.6.7
LAV Filters 0.74.1
madVR 0.92.17
Nvidia 441.08 with 3D vision injected
RTS 2060 Super
9700k


Thanks.

So madvr 3d still works well with Nvidia's last official 3d vision driver, 425.31. If you use a newer driver with 3d vision injected it breaks madvr framepacking support. It will kick the output into framepacking just fine, but it renders as side-by-side despite the output being in framepacked. I suspect there's something wrong in how madvr detects the output is in 3d framepacked, it may be as simple as that new nvidia driver versions are wrongly ignored by madvr (maybe an assumption that the new drivers don't support 3d, which they do fine if you inject 3d vision into the driver)

FYI, new nvidia drivers with 3d vision works excellent in 3d games, and 3d framepacked MVC players like Stereoscopic player and PowerDVD also work fine. (but can't compare to madvr quality!)

[ryrynz]

Originally Posted by Siso

Is upgrading from GTX 1050 Ti to GTX 1660 Ti a good option for madvr?

Yes, should be almost twice as capable and you'd be able to unlock much better settings.

[Siso]

Originally Posted by ryrynz

Yes, should be almost twice as capable and you'd be able to unlock much better settings.

Sounds good, thank you.

[tp4tissue]

Originally Posted by Siso

Is upgrading from GTX 1050 Ti to GTX 1660 Ti a good option for madvr?

It should work fine, but if it was me, I'd rather get a used 1080, as they're still more compatible, who knows when Madshi will fix all the bugs for Turing series cards.