madVR - high quality video renderer (GPU assisted)

[chros]

Originally Posted by j82k

Why would it even make a difference regarding HDR triggering or not what bitdepth I have selected in madVR?

Maybe it's a hardcoded limitation to do not screw up other stuff?

[huhn]

Originally Posted by kitame

i see, however RTX cards are currently way overpriced, and there were rumors that it was intentionally so to get rid of Pascal cards.

edit: speaking of benchmarks though, i wonder if Madshi is interested in making a benchmark on MadVR.

this has come up a couple of time and can't be reliable done.

turing cards are similar price as pascal cards in the same performance range at least before pascal was sold off. not a nice situation to say it friendly but it is time to stop cry about it that's just how a monopole works.

i'm personally not a fan of the current situation but AMD has to be blamed for this too.

[SweetLow]

Originally Posted by madshi

However, during playback/rendering, the whole chain is fully lossless. There's no lossy compression going on anywhere in between madVR and TV. So every dithered bit should reach the display untouched. As a result, bitdepth is much less important, because madVR's dithering is of very high quality.

We have VESA DSC on the horizon.

[x7007]

Originally Posted by j82k

Ok so with newer nvidia drivers (tested with 417.35) when starting an HDR movie:

madVR native display bitdepth set to 8-bit --> nothing happens, TV stays in SDR mode
madVR native display bitdepth set to 10-bit --> HDR triggers correctly

After starting a movie with 10-bit I can change it back to 8-bit and HDR stays active but when closing mpc-hc it doesn't return to SDR mode. Only closing it with 10-bit selected returns the TV to SDR mode.

Doesn't this point to it being a madVR problem then?
Why would it even make a difference regarding HDR triggering or not what bitdepth I have selected in madVR?

I just use AUTO .... it detect properly every time with NV Mode if with proper drivers and OS HDR when I manually change to 10 bit in NVCP drivers .

HDR supposed to be 10 bit always in games and movies right ? but how do we know how much depth is it using when it auto detect in a game ? because when you enable it from OS HDR it's only 8 bith + dithering , it messes up my DreamScreen color signal .

Is there any app to tell us how much depth is it using?

[nevcairiel]

Originally Posted by SweetLow

We have VESA DSC on the horizon.

HDMI 2.1 still has enough bandwidth for the forseeable future without needing compression, unless you want to get into 8K, which is probably beyond the point of diminishing returns in quality.
HDMI 2.1 should be able to transport 4K, 12-bit, 120Hz at full bandwidth, thats plenty for the next couple years.

[SweetLow]

Originally Posted by nevcairiel

HDMI 2.1 still has enough bandwidth for the forseeable future without needing compression, unless you want to get into 8K

I know. It's just little clarification that some things can change.
P.S. I remember you were talking about the "noise floor" before madshi's post

[kitame]

Originally Posted by nevcairiel

unless you want to get into 8K, which is probably beyond the point of diminishing returns in quality.

actually that would depend on it's purpose.
like those examples they use to showcase how much better 4K is than 1080P, they could fit in a wider scene without compromising the quality and clarity.



to point out, this would be way better with a large format display, completely replacing triple monitor with one gigantic screen.
and on that note, 8K is equivalent to 3 2560x1600 monitors, with 2720 extra vertical pixels.

[Mykola]

Originally Posted by madshi

B) FreeSync / G-SYNC

Games create a virtual world in which the player moves around, and for best playing experience, we want to achieve a very high frame rate and lowest possible latency, without any tearing. As a result with FreeSync/G-SYNC the game simply renders as fast as it can and then throws each rendered frame to the display immediately. This results in very smooth motion, low latency and a very good playability.

Video rendering has completely different requirements. Video was recorded at a very specific frame interval, e.g. 23.976 frames per second. When doing video playback, unlike games, we don't actually render a virtual 3D world. Instead we just send the recorded video frames to the display. Because we cannot actually re-render the video frames in a different 3D world view position, it doesn't make sense to send frames to the display as fast as we can render. The movie would play like fast forward, if we did that! For perfect motion smoothness, we want the display to show each video frame for *EXACTLY* the right amount of time, which is usually 1000 / 24.000 * 1.001 = 41.708333333333333333333333333333 milliseconds.

FreeSync/G-SYNC would help with video rendering only if they had an API which allowed madVR to specify which video frame should be displayed for how long. But this is not what FreeSync/G-SYNC were made for, so such an API probably doesn't exist (I'm not 100% sure about that, though). Video renderers do not want a rendered frame to be displayed immediately. Instead they want the frames to be displayed at a specific point in time in the future, which is the opposite of what FreeSync/G-SYNC were made for.

If you believe that using FreeSync/G-SYNC would be beneficial for video playback, you might be able to convince me to implement support for that by fulfilling the following 2 requirements:

1) Show me an API which allows me to define at which time in the future a specific video frame gets displayed, and for how long exactly.
2) Donate a FreeSync/G-SYNC monitor to me, so that I can actually test a possible implementation. Developing blindly without test hardware doesn't make sense.

Any news about that? How about creating your own timer? Something like spin wait? Modern systems can easily sacrifice one CPU core. And what about modern DirectCompute? Does it have enough features, to trigger frame swap without switching to userland code?

[Olivier C.]

madshi,

May I ask if you could at least add a font size parameter in IMadVRTextOsd::OsdDisplayMessage (not needed in madVR GUI nor settings atm) in order to display some easily readable messages on UHD displays (especially when screen size / distance is quite critical).

Thanks a lot

Originally Posted by madshi

madVR currently does not allow you to specify OSD size or font. I might add such features into a future version. But for now my priority is making madVR feature complete first. Cosmetical things like changing OSD looks is pretty low on my priority list right now. You'll have to wait a while until I get to these things, I'm sorry.

[madFloyd]

Originally Posted by Manni

As Asmodian said, MadVR doesn't use any of the new features yet, but when/if it does it should make a significant difference.

FYI Madshi himself doesn't advise buying GTX GPUs anymore at this stage but recommends RTX instead. He has made no promises or committed to anything, but it's most likely his intention to take advantage of the new architecture in the future with MadVR.

So no differences now, but down the line possibly a significant one.

If you want best possible PQ in HDR using MAdVR's excellent HDR tonemapping with all options/features available, I wouldn't buy anything below a 2080 (roughly equal to 1080ti), and I recommend a 2080ti if you can afford it to have some headroom. My 1080ti is struggling with the latest HDR test algos and I have to use it in D3D11 native as Copyback isn't up to the task without degrading quality. That means I lose black bar detection with D3D11 native, or have to lower the quality of chroma upscaling (using NGU AA High at the moment, so it's possible to downgrade without too much of a downside visually).

My plan is to upgrade the 1080ti as soon as nVidia releases a model supporting HDMI 2.1 and 7nm, at some point in 2019.

Manni, where does one choose between native and copyback? Is this a madVR setting or a LAV setting?

[Asmodian]

It is a LAV setting.

[madFloyd]

Originally Posted by Asmodian

It is a LAV setting.

Thanks. I've installed the latest LAV filters but can't seem to access them. I see that there is a desktop app for each of the filters but when I try to launch the LAV Video app nothing happens.

Any ideas?

[Damien147]

If the display is calibrated in target peak nits we put the calibrated peak nits or generally display's peak nits?

Does anyone have issues with NVidia latest drivers on Win10 1607 and Exclusive Full screen mode? I get tearing near the top in fast-paced scenes and that's with madVR-set custom resolution.

[x7007]

Originally Posted by XMonarchY

Does anyone have issues with NVidia latest drivers on Win10 1607 and Exclusive Full screen mode? I get tearing near the top in fast-paced scenes and that's with madVR-set custom resolution.

Why do you guys need Exclusive Full Screen mode ( FSE ) ? Windowed mode works better an faster.

[huhn]

i highly doubt windowed is faster than FSE.

@XMonarchY
does the display rate match the composition rate?
how high is the present time.
maybe add an screen of the OSD.

[Asmodian]

The switch into FSE is obviously slower than into fullscreen windowed.

[Rectal Prolapse]

Originally Posted by XMonarchY

Does anyone have issues with NVidia latest drivers on Win10 1607 and Exclusive Full screen mode? I get tearing near the top in fast-paced scenes and that's with madVR-set custom resolution.

I've had that problem before - on my system with a Sony 1080p projector, it was because the custom resolution I let MadVR pick is not compatible with the projector, leading to exactly what you are seeing. I had to pick a different one that is closer to specifications (I ended up trying 5 of them) and then it worked.

In the end I just manually create a custom resolution in the NVIDIA control panel instead of using MadVR's optimized ones. I already know what the settings should be so it saves me a lot of time doing that.

[giulianoprs]

even I do not need to use "Exclusive Full Screen mode" !!!
Windowed mode works better for me too, with no problems in playback, no dropped, repeated or delayed frames.
"Exclusive Full Screen mode" is more problematic.

[austinminton]

FSE is needed for the new rtx cards, definitely for my 2080 ti.