madVR - high quality video renderer (GPU assisted)

[Asmodian]

Originally Posted by madshi

What is this log for exactly? I can't see the decoder even trying to activate D3D11 DXVA decoding?

How odd, I did have it enabled in LAV and if I simply close and reopen the player madVR reported DXVA2n in the OSD. It may be a non-issue; once I stop changing the timings for a custom mode it stops happening.

[FDisk80]

Originally Posted by madshi

Double click "activate debug mode.bat", then reproduce the problem, then stop the media player, then zip the "madVR - log.txt" file on your desktop and upload it somewhere and link to it here. Then double click "activate release mode.bat".

ok, done, here you go.
https://drive.google.com/file/d/0B7b...ew?usp=sharing

[huhn]

i can clearly see the blended frames. i'm pretty sure that i was unable to see them in the past but i don't use this screen to watch stuff. the OSD doesn't show issues.

on my TV SM at 60 Hz is totally fine.

[aufkrawall]

Do we know which scaler is used for madVR's smooth motion?

[huhn]

no scaler.

[aufkrawall]

And the interpolated data originates from where?

[mogli]

The last and the next frame are blended like e.g. 0.3*f_last + 0.7*f_next.

[mparade]

In case of HDR10 sources what are the data madVR would need as HDR metadata to passthrough to the HDR10 compatible display?

Color primaries, transfer characteristics, color matrix, range of black level and range of luma and chroma signals would be enough? Or such data as well like:

- maximum content light level (MaxCLL) and maximum frame average light level (MaxFALL);

- SMPTE ST 2086 mastering display color volume SEI info;

- HDR parameters in SEI packets;

[Asmodian]

Originally Posted by huhn

i can clearly see the blended frames. i'm pretty sure that i was unable to see them in the past but i don't use this screen to watch stuff. the OSD doesn't show issues.

on my TV SM at 60 Hz is totally fine.

Hmm. Did G-sync get enabled? That messes up smooth motion a lot. I just retested and 23.976 fps @ 144 Hz seems very good, it actually seems slightly less blended than 60 Hz (though the dangers of placebo are strong with this). Definitely not worse.

[Matching_Mole]

Originally Posted by madshi

Does your HTPC have a single or dual monitor setup?

Single display correctly recognized in Madvr. When I play a video in 1080/23p, Madvr indicate correctly the resolution as active in the custom rez screen.

[huhn]

Originally Posted by Asmodian

Hmm. Did G-sync get enabled? That messes up smooth motion a lot. I just retested and 23.976 fps @ 144 Hz seems very good, it actually seems slightly less blended than 60 Hz (though the dangers of placebo are strong with this). Definitely not worse.

it should be better at 144 hz and no the screen is older then g-sync. it is one of the first 144 hz screens if not the first.

[madshi]

Originally Posted by huhn

can someone else test smoothmotion at 144 hz with a 23p source?

i see some really big issues on that screen right now and i don't know why.

FSE mode? 144hz is difficult for windowed mode. Another possible issue could be that the display accepts 144hz but might internally render at a slower speed. I don't know...

Originally Posted by FDisk80

ok, done, here you go.
https://drive.google.com/file/d/0B7b...ew?usp=sharing

According to the log D3D11 DXVA decoding is active the whole time. Are you sure that LAV showed "D3D11cb" while creating this log?

Originally Posted by mparade

In case of HDR10 sources what are the data madVR would need as HDR metadata to passthrough to the HDR10 compatible display?

Color primaries, transfer characteristics, color matrix, range of black level and range of luma and chroma signals would be enough? Or such data as well like:

- maximum content light level (MaxCLL) and maximum frame average light level (MaxFALL);

- SMPTE ST 2086 mastering display color volume SEI info;

- HDR parameters in SEI packets;

SMPTE 2086 mastering display information (gamut, min + max luminance), MaxCLL and MaxFALL. Stuff like the video's color primaries, matrix, transfer etc are usually "assumed" and not transported, AFAIK.

Originally Posted by Matching_Mole

Single display correctly recognized in Madvr. When I play a video in 1080/23p, Madvr indicate correctly the resolution as active in the custom rez screen.

Ok. Did you create the custom modes with madVR? Or manually by using an external tool or the GPU custom res control panel? The measurements currently only work for custom modes you created by using madVR, sadly. And you need to run the measurements for more than 10 minutes.

[huhn]

Originally Posted by madshi

FSE mode? 144hz is difficult for windowed mode. Another possible issue could be that the display accepts 144hz but might internally render at a slower speed. I don't know...

yes i'm using windowed it's a dual screen gaming PC FSE on the second screen gaming is a huge problem. the OSD doesn't show glitches, drops or repeats shouldn't this be shown if something goes wrong?

it's a native 144 Hz gaming screen it can for sure show them. it can do perfect 120 HZ + BFI too.

10 bit window mode was something like "FSE" as good as it maybe this helps but it is a 6 bit tn panel...

[Asmodian]

I was testing with the 144 Hz display as the primary monitor. I can test with it as the secondary when I get home but I wouldn't expect it to be an issue if no drops or presentation glitches are reported.

[madshi]

Originally Posted by huhn

yes i'm using windowed it's a dual screen gaming PC FSE on the second screen gaming is a huge problem. the OSD doesn't show glitches, drops or repeats shouldn't this be shown if something goes wrong?

it's a native 144 Hz gaming screen it can for sure show them. it can do perfect 120 HZ + BFI too.

10 bit window mode was something like "FSE" as good as it maybe this helps but it is a 6 bit tn panel...

madVR can only report what D3D says. Maybe DWM is dropping frames behind madVR's back without saying so. I'd strongly suggest you test FSE. Everybody who has problems with juddering playback should always test FSE as the first thing, IMHO. FSE has always been the most reliable playback mode - especially for very high refresh rates like 144hz.

[nevcairiel]

I use overlay mode on my 144Hz screen, because its the only reliable mode on that which isn't FSE (since FSE is too disruptive if you do things on the side - which is the only time I even watch things on my desktop anyway)
Although windowed D3D11 presentation mode with present one frame every refresh enabled is also almost good.

[arrgh]

Originally Posted by madshi

"Also"? So this is not a new problem?

Can you create a freeze report by pressing Ctrl+Alt+Shift+Break/Pause in the situation where the hang occurs? After having pressed the keys, a few seconds later hopefully a freeze report will appear on your desktop. If that doesn't work, let me know.

About judder: Please show a screenshot of the Ctrl+J OSD while the judder occurs.

Ctrl+Alt+Shift+Break/Pause does unfortunately not work (not in Win10 nor in Win81);
for the judder Problem I have made two Screen shots. one for 2D (both on Win81)


one for 3D


best regards

[FDisk80]

Originally Posted by madshi

According to the log D3D11 DXVA decoding is active the whole time. Are you sure that LAV showed "D3D11cb" while creating this log?

You misread my post. D3D DXVA is active, the problem is that when in native mode the video freezes each time for 3 seconds after refresh rate is switched.

It does not have this problem in D3D11 CB mode.

[huhn]

Originally Posted by nevcairiel

I use overlay mode on my 144Hz screen, because its the only reliable mode on that which isn't FSE (since FSE is too disruptive if you do things on the side - which is the only time I even watch things on my desktop anyway)
Although windowed D3D11 presentation mode with present one frame every refresh enabled is also almost good.

i will try it not an AMD GPU in this system anymore. can only get better.

For me Custom Refresh tool and settings only work if DSR is disabled... Has anyone managed to get both working?