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

[Zachs]

Yeah the "black band" is actually part of your video!

[elraffa]

than they are hard coded

Yeah the "black band" is actually part of your video!

:/ Thanks..

[x7007]

Thanks for reply.. Script chain like the image, it´s ok?
http://i.imgur.com/x0v2Axp.jpg



What did you set in Deband and Chroma Upscaler ? does EWA and all the rest that you set there has effect on 1080p and 720p ?

If I choose the scripted, what happens in the MPDN Luma,Chroma,Downscaling,Upscaling options ?

[Braum]

Hi ! :)

First of all thank you a lot Zachs for this awesome media player !

I have a question about Conditional render script and Script Group.

I've made a Script Group with three conditional render scripts for High/Medium/Low encoding quality and the problem is they don't seem to work.

So here's the conditional statements :

SourceSize.Width == 1920 and SourceSize.Height == 1080. use Script Chain
SourceSize.Width < 1900 and SourceSize.Height < 1080 and SourceSize.Width >= 920 and SourceSize.Height >= 720. use Script Chain
SourceSize.Width <= 1280 and SourceSize.Height <= 720. use Script Chain

Exemple :
http://reho.st/self/84573b60b730faf34ddcf166c07af73727c4218b.png

When I play a movie in 3 different encoding quality the conditional render scripts doesn't auto select like it should.
So for the moment I use the Hotkey and it does the trick.

Did I do something wrong ? How do I get this to work ?

:thanks:

[Zachs]

If I choose the scripted, what happens in the MPDN Luma,Chroma,Downscaling,Upscaling options ?

Just a little comment on that screenshot. If you want to sharpen at target size (i.e. post scale), you should add a resizer to make it "resize to 100% of target size" before adding the adaptive sharpen scripts. In the case where 1080p is viewed on 1080p screens, this is not necessary since post scale size is the same as pre scale size.

Now to answer your question. In that screenshot, MPDN's internal scalers are completely bypassed, because the only thing that would've been active anyway would be the chroma upscaler. However, this has been replaced by the EWA chroma scaler.

For lower res video (e.g. 720p) on 1080p screens, the resizer script as mentioned above would still use MPDN's luma upscaling option to scale from 720p to 1080p, unless of course if you choose to use NNEDI3, then it would use MPDN's luma downscaling option to scale from 1440p to 1080p. In those cases, the "luma" scaling options double as "image" scalers.

[Zachs]

Hi ! :)

First of all thank you a lot Zachs for this awesome media player !

I have a question about Conditional render script and Script Group.

I've made a Script Group with three conditional render scripts for High/Medium/Low encoding quality and the problem is they don't seem to work.

So here's the conditional statements :

SourceSize.Width == 1920 and SourceSize.Height == 1080. use Script Chain
SourceSize.Width < 1900 and SourceSize.Height < 1080 and SourceSize.Width >= 920 and SourceSize.Height >= 720. use Script Chain
SourceSize.Width <= 1280 and SourceSize.Height <= 720. use Script Chain

Exemple :
http://reho.st/self/84573b60b730faf34ddcf166c07af73727c4218b.png

When I play a movie in 3 different encoding quality the conditional render scripts doesn't auto select like it should.
So for the moment I use the Hotkey and it does the trick.

Did I do something wrong ? How do I get this to work ?

:thanks:

You need to put the conditionals in a "Script Chain", not script group (a script group is to enable hotkey toggling), and make sure you have the script chain selected as the active render script.

Your last conditional conflicts with your second one, so you'll need to correct that as well. The second one becomes active when width is between 920 and 1900 and height is between 720 and 1080. However, the last one also gets activated when the width is between 920 and 1280 and height is 720.

[Braum]

You need to put the conditionals in a "Script Chain", not script group (a script group is to enable hotkey toggling), and make sure you have the script chain selected as the active render script.

Your last conditional conflicts with your second one, so you'll need to correct that as well. The second one becomes active when width is between 920 and 1900 and height is between 720 and 1080. However, the last one also gets activated when the width is between 920 and 1280 and height is 720.

Ah my bad ! Indeed I've also made an error with my conditional !

Thank you a lot it works like a charm now ! :D

When using a sweetfx shader, do we need to use Linear&Gamma Light converter script ?

Like this :

ConvertToLinearLight
Shader
ConvertToGammaLight

[Zachs]

No there's no need to.

[Braum]

Okay http://reho.st/gif/65c89cd03a632899b5df556da5d65f11ca058dc2.gif

[elraffa]

What did you set in Deband and Chroma Upscaler ? does EWA and all the rest that you set there has effect on 1080p and 720p ?
In deband are the default options. In EWA chroma scaler I set Sinc-blackman - 8 taps - AR enabled - strenght 1.
Yes, all the scripts render that I set has effect in 1080p and 720p.

[diimaan]

With the test version MediaPlayerDotNet_AnyCPU_2_42_0_3375

I get the error "Video graph failed to render"

Hint
Make sure video filters are installed and configured properly.

I have LAV Filters 0.65 x64 version installed. Not the MPDN installer. LAV filters from the separate thread.

Also DynamicRangeCompressor extension fails to load in the test version.

[diimaan]

Updated to this version MediaPlayerDotNet_AnyCPU_2_42_0_3380

And still the same results.

But the installer version works fine on playback...

[Magik Mark]

zachs what is the functional difference between script chain & script group? Which scenario is best suited for each ?

[x7007]

In deband are the default options. In EWA chroma upscaler I set Sinc-blackman - 8 taps - AR enabled - strenght 1.
Yes, all the scripts render that I set has effect in 1080p and 720p.
You forgot the ChromaScaler, can you tell me the settings to this too .
If you select Video Renderer Script then the options Chroma,Luma Scaler - Downscaling are disabled and the script has the priority ? In shortcut, in NONE the normal MPDN Scaler,Downscaling works and if renderer selected then they are disabled.


I don't what settings to use then in the Chorma,Luma Upscaling and the Downscaling , EWA , Debanding.


couple of questions.

How come x86 doesn't manage to work CUVID ? it freezes when you try to open the movie. and you need to End the software from Task manager.
x64 works fine with CUVID

How can I use or enable Chroma NNEDI3 + AR + Debanding like MadVr ?

Does anyone uses FluidMotion with nvidia card ? it works the same like the Amd control panel option?

For some reason I have 2 Lav Filter Splitter tray icons, and checking the filters in MPDN it shows 2 Lav Filter Source, any idea why this could happen ?

[Zachs]

How come x86 doesn't manage to work CUVID ? it freezes when you try to open the movie. and you need to End the software from Task manager.
x64 works fine with CUVID

How can I use or enable Chroma NNEDI3 + AR + Debanding like MadVr ?

Does anyone uses FluidMotion with nvidia card ? it works the same like the Amd control panel option?

For some reason I have 2 Lav Filter Splitter tray icons, and checking the filters in MPDN it shows 2 Lav Filter Source, any idea why this could happen ?

LAV Filter with CUVID works fine for me on both x86 and x64... anyone else having this problem?

Chroma NNEDI3: read the posts on the previous page.

FluidMotion is not AMD's FluidMotion.

LAV Filter Splitter will show up twice because MPDN uses two separate graphs (use search next time please).

[Zachs]

zachs what is the functional difference between script chain & script group? Which scenario is best suited for each ?

Does no one ever read the thread before asking questions, even just one page back? http://forum.doom9.org/showthread.php?p=1736232#post1736232

[Zachs]

Updated to this version MediaPlayerDotNet_AnyCPU_2_42_0_3380

And still the same results.

But the installer version works fine on playback...

Did you extract all the files in the zip archive?

[elraffa]

You forgot the ChromaScaler, can you tell me the settings to this too .
Those settings are EWA chroma scaler from script render.
If you select Video Renderer Script then the options Chroma,Luma Scaler - Downscaling are disabled and the script has the priority ? In shortcut, in NONE the normal MPDN Scaler,Downscaling works and if renderer selected then they are disabled.
This was replied by Zachs in post #3156..If you use script render for both scalers, MPDN´s internal scaler will not work. The scalers will work depending on resolution of the movie and resolution of the monitor.

[aufkrawall]

Btw: You don't have to define Sinc-Blackman for chroma via render script if you want to use it all the time anyway.
Then it's enough to simply set it in main MPDN's chroma scaler settings (under "custom").

[diimaan]

Did you extract all the files in the zip archive?

I just extracted the entire zip to folder and tried to run from the extracted location. It does not see the LAV Filter install. I installed the x86 and x64, x86 alone, x64 alone all after a fresh install.

[Zachs]

Do you get the same problem with the released AnyCPU edition?

[diimaan]

Do you get the same problem with the released AnyCPU edition?

I am using the AnyCPU release only.

[Braum]

I'm trying to find a way to have a clean audio gain because I can't bring my DAC/AMP where I'll live. So one of the things I've tried is your exemple of Audio Script : Gain.cs ( https://github.com/zachsaw/MPDN_Extensions/blob/600ef8f1b20bdfc6dcf58e2c01fa68edfd47cdb1/Examples/AudioScripts/Gain.cs)

Alas the script failed to load :

http://reho.st/self/b6c22e1f9f3bb3520ab287ce13bea19804d04293.png


Maybe I've done something wrong ?

Is there a way to have an audio gain script ?

I was using a VST/DSP plugin before but it's not compatible with MPDN yet.

[Zachs]

I am using the AnyCPU release only.
So you're saying the AnyCPU release version is working but not the test builds?

[Zachs]

I'm trying to find a way to have a clean audio gain because I can't bring my DAC/AMP where I'll live. So one of the things I've tried is your exemple of Audio Script : Gain.cs ( https://github.com/zachsaw/MPDN_Extensions/blob/600ef8f1b20bdfc6dcf58e2c01fa68edfd47cdb1/Examples/AudioScripts/Gain.cs)

Alas the script failed to load :

http://reho.st/self/b6c22e1f9f3bb3520ab287ce13bea19804d04293.png


Maybe I've done something wrong ?

Is there a way to have an audio gain script ?

I was using a VST/DSP plugin before but it's not compatible with MPDN yet.
The gain example is an example written to show developers how they can write their own audio scripts. It clips anything that is over amplified. Are you sure you know what you want?

[Zachs]

Btw: You don't have to define Sinc-Blackman for chroma via render script if you want to use it all the time anyway.
Then it's enough to simply set it in main MPDN's chroma scaler settings (under "custom").
Actually just to clarify, the EWA version is different to the MPDN internal scaler. They use the same kernel function but they'll give you different results.

[Braum]

The gain example is an example written to show developers how they can write their own audio scripts. It clips anything that is over amplified. Are you sure you know what you want?
Well if it clip then no, my bad.
Actually I think the low audio ouput problem come from the downmix of DTS 7.1 to Stereo.

Do you see a solution ? Or a clue/lead ?

:thanks:

[huhn]

if your output is low think about DRC. AC3 filter can do thsi and it should work totally fine with MPDN.

DRC is bad for audio quality just to make that clear the other way would be a audio system with a proper amp.

[Braum]

if your output is low think about DRC. AC3 filter can do thsi and it should work totally fine with MPDN.

DRC is bad for audio quality

DRC isn't what I'm looking for as it reduce dynamic range (which I want to conserve).
just to make that clear the other way would be a audio system with a proper amp
Indeed, so I'll need to keep my DAC/AMP with me.

Thank you for your answer !

[huhn]

is not possible to boost audio digital without lowering the dynamic range.

different headphones and USB DAC can easily have a higher max volume and there are mobile headphone amps...

[Braum]

is not possible to boost audio digital without lowering the dynamic range.

different headphones and USB DAC can easily have a higher max volume and there are mobile headphone amps...

I got a Burson HA160DS

Measurements:
Input impedance: 36.5 KOhms
Frequency response: ± 1 dB 0 – 20Khz
Signal to noise ratio: 110dB
THD: <0.12% at 150mW , 0.06% at 100mW
Channel separation: <54dB
Output power: 250mW (less than 1% distortion)
Output impedance: phones out 5.6 Ohms
Power dissipation: >20W, internal, regulated power supply

With an orthodynamic (high impedance) headphone (ZMF x Vibro).

With DTS (downmix to stereo) and high impedance headphone I need to put the volume near to the max. The signal is clean but the DAC/AMP is very hot and during summer that's no good ^^

[huhn]

a normal sound card isn't made to feed headphones with more than 32 OHM. and that can't be fixed with digital processing.
these headphones are simply not made to run without AMP or an really good soundcard.

the strange thing is that these are just listed with 50 ohm so they shouldn't get in trouble except for mobile devices. for mobile use a headphone should be at 16-32 ohm or even lower.
on the other hand even my 16 ohm t5p gets into trouble with an source device like an 3ds.

what so ever nothing a software should be used for if audio quality matters.

btw. it would be nice if you could can MPDN with an video file and check the latency with latencymon: http://www.resplendence.com/latencymon

i would really like to know if i'm the only one with issues thanks to my DACs.

[Zachs]

if your output is low think about DRC. AC3 filter can do thsi and it should work totally fine with MPDN.

DRC is bad for audio quality just to make that clear the other way would be a audio system with a proper amp.

Oh btw the next version of MPDN will have a DRC audio script too with pretty extensive settings that you can tune to your liking.

[diimaan]

So you're saying the AnyCPU release version is working but not the test builds?

I am sorry for not being clear. The release edition 64 bit(installer version) runs fine.

But when I try the Latest test version(zip files from here (http://mpdn.zachsaw.com/Test%20Builds/3380/)) of AnyCPU/x86/x64 versions all were not able to find the LAV filters.

While trying test versions, I uninstalled the release version and cleared the folder from %appdata%\local\mpdn.
Then Installed the LAV filters separately.

Still the test versions (zip versions) were not able to locate the LAV filters. I tried installing and uninstalling various versions of LAV filters. (0.65/0.64/0.63) etc.

[Anime Viewer]

I updated to Windows 10 this morning, and I was pleasantly surprised to find that that when I launched a video in MPDN fullscreen I no longer have high present times when using my Optimus Nvidia GTX 680M as the gpu. My present times are now 0.30ms. MPDN coding seems to have something to do with it, for when I tested with MPC-HC and madVR I still get 9ms present times.

[aufkrawall]

I rather suppose the reported low rendering time is far off from any reality.

[huhn]

he is talking about present times.

there where always pretty high present times issue with optimus system.
if they are high enough to cause problems is another story.

[aufkrawall]

Whoops, I wanted to recheck if it was about present times, but forgot it. :)

[Braum]

a normal sound card isn't made to feed headphones with more than 32 OHM. and that can't be fixed with digital processing.
these headphones are simply not made to run without AMP or an really good soundcard.

That's why I got a Burson HA160DS
http://reho.st/self/ecce65b87a58146ab4e7ebc3c16f5413fdbb4908.jpg (http://reho.st/view/self/ecce65b87a58146ab4e7ebc3c16f5413fdbb4908.jpg)

the strange thing is that these are just listed with 50 ohm so they shouldn't get in trouble except for mobile devices. for mobile use a headphone should be at 16-32 ohm or even lower.
on the other hand even my 16 ohm t5p gets into trouble with an source device like an 3ds.

what so ever nothing a software should be used for if audio quality matters..

When I listen to music my DAC/AMP is at low volume but when I Watch movies (mainly DTS audio) I need to put the volume near to the maximum.

btw. it would be nice if you could can MPDN with an video file and check the latency with latencymon: http://www.resplendence.com/latencymon

i would really like to know if i'm the only one with issues thanks to my DACs.

Will do, I'm moving to a new place so I'll check it later this week. ;)

[huhn]

That's why I got a Burson HA160DS
http://reho.st/self/ecce65b87a58146ab4e7ebc3c16f5413fdbb4908.jpg (http://reho.st/view/self/ecce65b87a58146ab4e7ebc3c16f5413fdbb4908.jpg)

and i'm happy that i didn't need my headphone AMP at all.


When I listen to music my DAC/AMP is at low volume but when I Watch movies (mainly DTS audio) I need to put the volume near to the maximum.

that normal music is DRC to death all ready on the disc/dl/streaming while a movies isn't DRC or at least not as hard.

i usually watch movies at 30-45 % while i hear music at 10-20%

Will do, I'm moving to a new place so I'll check it later this week. ;)

thanks

[aufkrawall]

:thanks: for making render script chroma scalers compatible with NNEDI3, it really looks better in cartoons with resolution doubling now.

[Zachs]

No problem. That was always in the plan. And once we sort out the basic chroma scaling framework, NNEDI3 chroma will follow.

[aufkrawall]

I will test it. :cool:
Will both also be possible with OpenCL NNEDI3?

Btw: Maybe it will make sense to completely replace main MPDN scalers by render script ones in future, or at least remove some of them?
I could imagine that new users might gonna panic if they see all those options. :)
Of course MPDN is mainly for advanced users, but there are really quite some buttons now. :D

[Zachs]

Ah well to cater for those non-advanced users, I'll keep the internal scalers there just so they could use it if render script is a little too much for them.

EDIT: Yes the OpenCL and shader version will work the same. Just haven't had the time to bring the chroma scaler across to the OpenCL version.

[ryrynz]

Ah well to cater for those non-advanced users, I'll keep the internal scalers there just so they could use it if render script is a little too much for them.


And for people not using extensions..or would that somehow work?

[Zachs]

And for people not using extensions..or would that somehow work?

Yes it would be needed for those who're not using extensions too.

[Zachs]

Time flies and it's been a year since MPDN was first released. Happy Birthday MPDN!

Just wanted to take the opportunity to thank all the hard work from the devs and all the testers in helping to make MPDN a great media player that it is today. Thank you!

MPDN v2.42.0 has been released with two key features you've been asking for: Custom chroma scaler in NNEDI3 (both shader and OpenCL) and Dynamic Range Compressor AudioScript.

It remains our top priority to bring you the following features:
Chaining of AudioScripts
NNEDI3 Chroma Scaler

Cheers!

[Anima123]

Congratulations all the developers who dedicated your enthusiasm into this great project.

Your attitudes are cautious yet open, solved one issue and another either implicitly or explicitly. That's what we called professional.

[Anima123]

I don't really understand the new NNEDI3 Chroma Scaler, what it do and when to trigger it.

Previously we can use render script chain to invoke EWA Chroma Scaler, what's the difference between that and the new NNEDI3 Chroma Scaler? And why it's still be activated when playing a 1080p video with native target resolution and the rendering time is high?

[Zachs]

EWA Chroma Scaler in the render script scales the initial chroma to luma size. NNEDI3's custom chroma scaler then doubles the chroma alongside the luma which is being doubled with NNEDI3. Previously it is not possible to use any custom chroma scaler alongside NNEDI3 (it used to scale with MPDN's internal scalers only).