madVR - high quality video renderer (GPU assisted)

[huhn]

it will be in sync cause it really doesn't care what madVR is doing.to do changes to the speed you need VRR.

with SM you actually get always no matter what double the source frame rate as long as that fids changed by the audio clocks speed.
and SM takes the speed of the audio where other algorithm do not matter only audio speed matters. and that's why it can change speed by syncing it to audio something a scaler can not do.

if you could slightly change speed with a scaler the A/V be so far off after just mins it would be utterly unwatched able.

and yes SM changes stuff and why couldn't that happen without cause VSYNC. to get difference you need to get tearing and if you have that you really messed up!

and if the "AI" says a vsync frame send to GPU for presentation can have a different "timing" based on the rendertime of "heavy" algorithm then the AI is not the only one imagination right now.

yes let GPU load change the frame duration on an HDMI signal what could possible go wrong the AI said that's possible... why couldn't that happen? cause a render pipeline is not blending. audio video just stays in sync using MAGIC.
why would older hardware have different smaller buffer? the presentation queue is a buffer we set that up not by hand.
the only difference you can get is an entire VSYNC and if that is "slightly" different i'm lost.

[utz]

I have a problem with madVR. Every recent Nvidia driver (latest I tried without problems was 581.80) causes madvr to have washed out colors and raised black. As if gamma was suddenly incorrect? Adjusting gamme setting in madvr doesn't fix it however. I've been using madvr for over 10 years now on a variety of systems and never experienced that before. Reverting back to 581.80 fixed the problem but that's not a permanent solution.

Help??

[Sunspark]

Sounds like a PC 0-255/video 16-235 levels mismatch. Look in the madvr settings for display and see if changing that does anything.

[clsid]

Either a driver bug, or the display output settings in driver settings were changed to incorrect value.

[utz]

Originally Posted by Sunspark

Sounds like a PC 0-255/video 16-235 levels mismatch. Look in the madvr settings for display and see if changing that does anything.

That's what I tried first. Doesn't dix it. It's not just levels it looks like a gamma issue.

Something that madvr uses must have changed in the driver. Does nobody else have this problem?

Originally Posted by clsid

Either a driver bug, or the display output settings in driver settings were changed to incorrect value.

Nothing changed, everything default. When reverting back to the old driver everything is fixed.

[huhn]

are you using anything related to DXVA2?
if yes stop that.

[doffen]

What about DXVA2 (copy-back)?

[huhn]

if you have that problem yes also that while that will be the last place i expect to fix that but still yes.

[doffen]

I haven't noticed that problem, the question was about avoiding anything related to DXVA2, and alternatives to DXVA2 copy-back.
My settings have been the same for years with no apparent need to change anything, and I'm still using windows 10 for media playback. Although I might have to update to windows 11 in the end.

[huhn]

if you see no issue DXVA2 copyback should be bit perfect. but that is something that can break with a GPU driver update

[doffen]

Perfect, thanks!