Media Player .NET (MPDN) - D3D HQ GPU Video Renderer [v2.49.0/v1.31.0 27 Dec 2018]

[Zachs]

Originally Posted by huhn

i just wanted to test for audio differences.

but i run into my general audio issues again this time way worse than usually.
the first thing that changed is that the fullness is not the problem it is now staying at stable 90%.
but now i see the ref clock changing when i hear an audio issue and some times a frame is delayed at the same time. the refclk deviations is skyrocketing after that. i even saw numbers like 0.35 % after 60 sec playback.
that's without rate tuner. but i got this issue with it too.

of cause i don't have that issue with madVR.

Without the rate tuner, MPDN is a slave to the ref clock which is usually derived from the audio card by the audio renderer. As such, video smoothness is affected when you get an audio problem. TBH I'm not sure what could be the problem seeing as I can't replicate your problem even on my very low end Atom tablet, or my very old and dusty Core2Duo laptop with ATI Mobility Radeon X2300. My HTPC runs a Creative X-Fi and that has never encountered any problems too.

Originally Posted by kerimcem

mpdn+lav video intel quciksync hardware gpu deinterlacing mpeg2 vob files = image gets stuck..
mpc+madvr+lav video intel quciksync hardware gpu deinterlacing mpeg2 vob files =no problem......

I personally watch a lot of MPEG2 interlaced materials with MPDN and haven't had any problem. With madVR are you sure you're using LAV's quicksync decode+deint hardware and not madVR's DXVA decode?

[ryrynz]

I notice some render script examples get installed with the latest release, is that intentional? Could be tider if there was an option to install 'em.

[Zachs]

That wasn't intentional. I'll have a look!

EDIT: Extensions v1.6.1 should have the examples removed.

[Magik Mark]

Zachs,

How do i put 1080p & 720p videos both 24fps in the video type found in the rate tuner? Thanks

[Zachs]

24.000fps or 23.976?
If it's the latter it's "23p"

[Magik Mark]

Originally Posted by Zachs

24.000fps or 23.976?
If it's the latter it's "23p"

Is this the right format:

w1920 h1080 p23? Gives me an error

[Zachs]

There's no need to specify height or width if you want to match all p23 materials. If you want to match 1080p 23.976, use w1920p23. w1280p23 for 720p 23.976hz materials.

[Magik Mark]

Originally Posted by Zachs

There's no need to specify height or width if you want to match all p23 materials. If you want to match 1080p 23.976, use w1920p23. w1280p23 for 720p 23.976hz materials.

Thank you that did it for tv shows. I'm getting a lot of frame drops when watching movies. This is really odd. The frame rate & resolution are the same as that of tv shows. Its really moving a little bit fast for both audio & video. Like the chipmunks

[Zachs]

Check your render times. Are they the same between the two?

[Magik Mark]

Originally Posted by Zachs

Check your render times. Are they the same between the two?

There is a difference of 2ms. When I switch FSE tv shows are behaving the same as the movies. AUdio & video are moving fast. All I did is copy the speed% found in the calculator

[Zachs]

You can't simply copy the values. If you want it to match 23.976hz of your display refresh rate, you need to first switch to that mode. Otherwise you're asking it to play at whatever your refresh rate was when you opened the calculator.

I will write a guide on how to use it when I get some time.

[ryrynz]

Originally Posted by Magik Mark

Its really moving a little bit fast, like the chipmunks

Originally Posted by Zachs

You can't simply copy the values.

[Zachs]

A short guide using 23.976FPS materials, assuming you have a monitor / TV capable of 24 input.

First, set your display refresh rate to 24Hz.
Run your 23.976FPS video for 5 minutes (make sure you don't seek / pause -- just let it run continuously).
Once you have let it run for 5 minutes, open the calculator with the video still running.
At this point, the calculator will give you very accurate values which will make your 23.976FPS input run at exactly your display refresh rate.

If you have a display capable of 25Hz, you can use the same steps as above to run your 23.976FPS input as 25FPS so you don't get any dropped / repeated frames. Most TVs don't support 25Hz but can do 50Hz. In which case, all you have to do is manually divide your Display Rate value by 2 in the calculator. This will give you 25FPS on a 50Hz refresh rate.

What this means is, you can disable fluid motion and still have perfectly fluid video playback. For the 24Hz refresh rate case, you can now enable your TV's FRC feature. With absolutely no repeated / dropped frames, your TV's FRC feature won't interpolate the wrong frames - IOW the FRC feature will work in its most ideal manner.

[ryrynz]

Would it be perfectly? or could it stand to do an automatic correction every say 5/10 minutes or something, as going by the OSD the there is a bit of fluctuation going on.

[bacondither]

I have found a strange bug.

When testing my adaptive sharpen shader in a script chain with deband and the video was displayed at original size the image flickers heavy with a pattern of fast dark and normal frames.

I have located the core of the problem to outputting a float3 as a float4 with padding for the w component which results in flickering.

//"flicker.hlsl"
sampler s0 : register(s0);

float4 main(float2 tex : TEXCOORD0) : COLOR
{
	float3 c0 = tex2D(s0, tex).rgb;

	return c0.rgbb;
}

Example script chains with flickering:
deband --> flicker.hlsl
deband --> resizer --> flicker.hlsl
flicker.hlsl --> deband
chroma scaler --> flicker.hlsl

Flickering only occurs when the image is at the original size, if the image is scaled the flickering goes away.

"flicker.hlsl" by itself in the chain gives no problems at all.

Tested with MPDN v2.31.0 and extensions v1.6.1, all the settings in MPDN is the default.
AMD GPU running driver version 14.4.

[Anime Viewer]

Originally Posted by Zachs

You can't simply copy the values. If you want it to match 23.976hz of your display refresh rate, you need to first switch to that mode. Otherwise you're asking it to play at whatever your refresh rate was when you opened the calculator.

I will write a guide on how to use it when I get some time.

That might explain why when I originally tested Rate Tuner it was giving me reports of ~249%-250% even when I clicked the calculator and input 23.976 and 24 in the display rate section of the calculator.

This raises a problem I've noticed. I have two displays: one that is the default notebook screen which supports 59hz and 60hz only, the other is a TV that supports 23hz,24hz, 59hz, and 60hz. I used to be able to go into Windows screen resolution, pick the TV under display, click the Advanced Settings link, List All Modes, select the mode I want to run in (ex: 1920x1080, True Color (32bit), 23Hertz, click ok and it would switch the tv screen to that setting which I could confirm with the CTRL+J listing for display as the video would run. However now while it looks like it took the setting in Windows display modes (if I go back in the one I chose is still highlighted/selected MPDN CTRL+J inside the video reports the display as 59hz regardless. The videos I've tested are 23.976hz source files. I've tested with and without Display Changer Activate automatic display refresh rate changer checked, and still MPDN OSD is reporting the display as 59hz.
Any thoughts as to why the OSD is reporting 59hz when playing videos on the TV regardless or what hz I've selected for the screen to run in? (I have both "Use highest" and "Activate only" both unchecked when testing in Display Changer). Is it possible the screen is changing, but the OSD isn't reporting it right?

[Shiandow]

Originally Posted by bacondither

I have found a strange bug.

When testing my adaptive sharpen shader in a script chain with deband and the video was displayed at original size the image flickers heavy with a pattern of fast dark and normal frames.

I have located the core of the problem to outputting a float3 with padding for the z component which results in flickering.

[...]

Example script chains with flickering:
deband --> flicker.hlsl
deband --> resizer --> flicker.hlsl
flicker.hlsl --> deband
chroma scaler --> flicker.hlsl

Flickering only occurs when the image is at the original size, if the image is scaled the flickering goes away.

"flicker.hlsl" by itself in the chain gives no problems at all.

Tested with MPDN v2.31.0 and extensions v1.6.1, all the settings in MPDN is the default.
AMD GPU running driver version 14.4.

That's probably caused by the alpha channel. MPDN doesn't like it when it is not 1. Some processing fixes the alpha channel again so it only causes problems sometimes.

[bacondither]

Originally Posted by Shiandow

That's probably caused by the alpha channel. MPDN doesn't like it when it is not 1. Some processing fixes the alpha channel again so it only causes problems sometimes.

Thanks! Setting the w channel to 1 seems to work.

[huhn]

Originally Posted by Zachs

Without the rate tuner, MPDN is a slave to the ref clock which is usually derived from the audio card by the audio renderer. As such, video smoothness is affected when you get an audio problem. TBH I'm not sure what could be the problem seeing as I can't replicate your problem even on my very low end Atom tablet, or my very old and dusty Core2Duo laptop with ATI Mobility Radeon X2300. My HTPC runs a Creative X-Fi and that has never encountered any problems too.

i only have this problem with MPDN. EVR, foobar2000, computer games and web browser they all work totally fine.

and the next thing is if MPDN is the slave to the audio clock why is audio distorted and not a frame repeated/dropped? in best case i get a frame delay with audio distortion in most cases just audio distortion even through MPDN shows a frame repeat of a couple of secs with clock deviations of 0.35 %.

and of cause is no real work for my HTPC to use MPDN.

[Magik Mark]

Originally Posted by Zachs

A short guide using 23.976FPS materials, assuming you have a monitor / TV capable of 24 input.

First, set your display refresh rate to 24Hz.
Run your 23.976FPS video for 5 minutes (make sure you don't seek / pause -- just let it run continuously).
Once you have let it run for 5 minutes, open the calculator with the video still running.
At this point, the calculator will give you very accurate values which will make your 23.976FPS input run at exactly your display refresh rate.

If you have a display capable of 25Hz, you can use the same steps as above to run your 23.976FPS input as 25FPS so you don't get any dropped / repeated frames. Most TVs don't support 25Hz but can do 50Hz. In which case, all you have to do is manually divide your Display Rate value by 2 in the calculator. This will give you 25FPS on a 50Hz refresh rate.

What this means is, you can disable fluid motion and still have perfectly fluid video playback. For the 24Hz refresh rate case, you can now enable your TV's FRC feature. With absolutely no repeated / dropped frames, your TV's FRC feature won't interpolate the wrong frames - IOW the FRC feature will work in its most ideal manner.

I have 60hz Monitor. Does it mean I have to divide the refresh rate in the calculator by 2.5 in order to play 23.976hz or 24 hz video smoothly?