Log in

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

Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 [65] 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96
Anima123
2nd September 2015, 06:29
It might be a false alarm.

The only thing that I can't figure out is why playing back a low-resolution file, which formerly takes far less rendering time than now.
Zachs
2nd September 2015, 06:29
I have to disagree, SuperChromaRes can brighten up colors.
And with NNEDI3 for chroma, you wouldn't have to run an AR filter.
Chroma can also have hard structures, at least with artificial content (which is not fully unrealistic to appear "in the wild", like pixel art).
I'd really appreciate it if NNEDI3 for chroma would get some higher priority. :)

I've just committed NNEDI3 chroma scaler (shader version only for now). If you like you can test it out with the latest source on GitHub.
Zachs
2nd September 2015, 06:30
It might be a false alarm.

The only thing that I can't figure out is why playing back a low-resolution file, which formerly takes far less rendering time than now.

Are you using the same settings as before?
Anima123
2nd September 2015, 07:27
Are you using the same settings as before?

Solved. It seems that the new version need a clean installation.
burfadel
2nd September 2015, 07:53
The first post links to extensions version v1.17.0, however I downloaded and installed both the new MPDN and the extensions, and the update check came up with extensions version v1.17.1. I noticed this a little while ago, I thought I'd give time in case it happened to be between the time of the update and the post being updated :).
Zachs
2nd September 2015, 07:56
The first post links to extensions version v1.17.0, however I downloaded and installed both the new MPDN and the extensions, and the update check came up with extensions version v1.17.1. I noticed this a little while ago, I thought I'd give time in case it happened to be between the time of the update and the post being updated :).

Ah thanks for that. Totally forgot to update the first post.
LDD9O
2nd September 2015, 12:19
Comodo reporting that there is a trojan in one of your files. Can you submit it for analysis or write them an email/ticket.
aufkrawall
2nd September 2015, 13:19
I've just committed NNEDI3 chroma scaler (shader version only for now). If you like you can test it out with the latest source on GitHub.
Thanks. Is a new MPDN test build required for this? With 2.42 I get an error that it couldn't load extensions when using Github version.
Zachs
2nd September 2015, 13:21
Hmm I'll have a look. BTW I'm still working on it so the GitHub master might not work properly.
Zachs
2nd September 2015, 13:53
I've just committed what I believe should be the working version of the NNEDI3 chroma scalers for both shader and OpenCL.
I also verified that it runs without a problem with MPDN 2.42.0.3380.
Zachs
2nd September 2015, 13:56
Comodo reporting that there is a trojan in one of your files. Can you submit it for analysis or write them an email/ticket.

Can you let me know what the full false-positive name of that trojan is? And which files did it report the false-positive?

I'm trying to submit it using this link: https://www.comodo.com/home/internet-security/submit.php
aufkrawall
2nd September 2015, 13:57
What kind of crazy service is this? :D

But somehow it still refuses with this error :confused: :
http://abload.de/img/erroru5suh.jpg (http://abload.de/image.php?img=erroru5suh.jpg)
Deleting MPDN's config doesn't help.
Zachs
2nd September 2015, 14:01
Can you try deleting the extensions cache by issuing a flush cache command line argument?
Zachs
2nd September 2015, 14:02
And make sure you're not unzipping it into a non empty extensions folder.
aufkrawall
2nd September 2015, 14:11
Everything's in the right folder and I did flushcache, doesn't help.
Somehow non-binary scripts here stopped working with the recent changes.
Two days ago it was just working fine.
Zachs
2nd September 2015, 14:31
That's strange. I just tested it again, this time with the zip file downloaded from GitHub directly - it still works fine...

EDIT: I see the problem now. For some reason with the AnyCPU edition it works fine...
Zachs
2nd September 2015, 14:56
Right. Can you try test build 3382 to see if it fixes the problem?
aufkrawall
2nd September 2015, 15:03
Fixed. :)
Will test NNEDI3 chroma soon, I'll first have to do some gardening. :o
aufkrawall
2nd September 2015, 18:04
It seems to be working well, except if MPDN's internal luma scalers are used at the same time. Then aliasing is introduced.
However, it works fine in conjunction with any kind of render script luma upscaling.

NNEDI3 for chroma looks as good as I have hoped: black lines crossing red mostly don't show any aliasing and are clearly defined. There is no nasty ringing boosted with low quality sources either.
:cool:
elraffa
2nd September 2015, 20:12
If I want to use NNEDI3 chroma scaler, how do I configure script render?
http://i.imgur.com/to08rlo.jpg
aufkrawall
2nd September 2015, 20:25
It is not yet officially released in a stable version, you have to grab the latest render scripts from Github.
But I rather recommend to wait until it is in final binary, usually things get there very quickly.
Shiandow
2nd September 2015, 20:52
By the way, this was already announced before, but with the latest extensions you can now copy settings from the Script Chain dialog to clipboard. It stores these settings as text, so you can then paste them into a doom9 comment, and someone else could copy this text and paste it into MPDN as a RenderScript. For technical reasons this only works in the Script Chain and Script Group dialogs, though.

This makes it significantly easier to share your settings with someone else. Which, with the complexity MPDN allows, could save a lot of time (I think MPDN might be the only video player with a Turing complete settings dialog).

For example, here is a script which combines a Script Group and a Deband script to make a debanding script which can be toggled on and off by pressing "Ctrl+Shift+D":


<ListOfPreset xmlns:yaxlib="http://www.sinairv.com/yaxlib/">
<Preset Name="Debanding" Guid="2eedac80-a1d3-4ad9-a8e6-027464debb1c">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.ScriptGroup.ScriptGroupScript">
<Settings>
<SelectedIndex>1</SelectedIndex>
<Hotkey>Ctrl+Shift+D</Hotkey>
<Options>
<Preset Name="Off" Guid="aecfa54b-7ac8-4f37-a2b5-ad68a482c9f0">
<Script yaxlib:realtype="Mpdn.Extensions.Framework.RenderChain.RenderChainUi+IdentityRenderChainUi">
<Settings />
</Script>
</Preset>
<Preset Name="On" Guid="5508d6a2-9ec8-4b0d-8c11-22f2c96d406e">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.Deband.DebandUi">
<Settings>
<maxbitdepth>8</maxbitdepth>
<power>0.5</power>
<grain>False</grain>
</Settings>
</Script>
</Preset>
</Options>
</Settings>
</Script>
</Preset>
</ListOfPreset>
aufkrawall
2nd September 2015, 21:16
Neat. I also noticed that you can do copy&paste now in the settings dialogs themselves, which is also a cool thing (e.g. to clone script chains or groups).
Anima123
3rd September 2015, 00:11
It seems to be working well, except if MPDN's internal luma scalers are used at the same time. Then aliasing is introduced.
However, it works fine in conjunction with any kind of render script luma upscaling.

NNEDI3 for chroma looks as good as I have hoped: black lines crossing red mostly don't show any aliasing and are clearly defined. There is no nasty ringing boosted with low quality sources either.
:cool:

Do I have to add a resizer at the end of Script chain to use luma upscaling?

What's your configuration for NNEDI3 chroma scaling, 16 or 32 neurons?
Zachs
3rd September 2015, 02:54
It seems to be working well, except if MPDN's internal luma scalers are used at the same time. Then aliasing is introduced.

That's because there's a bug in the framework that causes it to stretch the resulting NNEDI3 chroma. I'll see if I can fix it, if not I'll get Shiandow to have a look.

EDIT: This should be fixed with the latest commits, but make sure you don't use NNEDI3 chroma with non 4:2:0 sources yet. I'll need to check with Shiandow to see how we're going to handle it in the framework.

EDIT2: Non 4:2:0 sources should now work.
Zachs
3rd September 2015, 03:18
I think MPDN might be the only video player with a Turing complete settings dialog.

In case anyone's wondering what "Turing complete" means: https://en.wikipedia.org/wiki/Turing_completeness
Zachs
3rd September 2015, 03:27
And here's another decent script I like to use:


<ListOfPreset xmlns:yaxlib="http://www.sinairv.com/yaxlib/">
<Preset Name="SuperChromaRes" Guid="16227e78-1997-460b-bd78-f76b332237e7">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.SuperRes.SuperChromaResUi">
<Settings>
<Passes>1</Passes>
<Strength>1</Strength>
<Softness>0</Softness>
<Prescaler>True</Prescaler>
</Settings>
</Script>
</Preset>
<Preset Name="Debanding" Guid="2eedac80-a1d3-4ad9-a8e6-027464debb1c">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.ScriptGroup.ScriptGroupScript">
<Settings>
<SelectedIndex>1</SelectedIndex>
<Hotkey>Ctrl+Shift+D</Hotkey>
<Options>
<Preset Name="Off" Guid="aecfa54b-7ac8-4f37-a2b5-ad68a482c9f0">
<Script yaxlib:realtype="Mpdn.Extensions.Framework.RenderChain.RenderChainUi+IdentityRenderChainUi">
<Settings />
</Script>
</Preset>
<Preset Name="On" Guid="5508d6a2-9ec8-4b0d-8c11-22f2c96d406e">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.Deband.DebandUi">
<Settings>
<maxbitdepth>8</maxbitdepth>
<power>0.5</power>
<grain>False</grain>
</Settings>
</Script>
</Preset>
</Options>
</Settings>
</Script>
</Preset>
<Preset Name="NNEDI3" Guid="bae19540-a4d6-49af-ad00-194a19de9c0e">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.NNedi3.NNedi3Scaler">
<Settings>
<Neurons1>Neurons32</Neurons1>
<Neurons2>Neurons32</Neurons2>
<CodePath>UnrolledVectorDot</CodePath>
<Structured>False</Structured>
<ChromaScalers>
<ChromaScalerPreset Name="None" Guid="6aa7ce83-40c6-4af3-932e-442fad3449bc">
<Script yaxlib:realtype="Mpdn.Extensions.Framework.RenderChain.RenderChainUi+IdentityRenderChainUi">
<Settings />
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="ChromaScaler" Guid="52c90742-3348-41b2-917d-70b77246db3c">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.Chroma.ChromaScaler">
<Settings>
<B>0.3333333</B>
<C>0.3333333</C>
<Preset>MitchellNetravali</Preset>
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="EWA Chroma Scaler" Guid="770eb8ed-bede-4c35-a15c-a115693f0abe">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.EwaScaler.EwaScalerChromaScalerUi">
<Settings>
<TapCount>Eight</TapCount>
<AntiRingingEnabled>True</AntiRingingEnabled>
<AntiRingingStrength>1</AntiRingingStrength>
<Scaler yaxlib:realtype="Mpdn.Extensions.CustomLinearScalers.SincBlackman" />
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="SuperChromaRes" Guid="926e48ac-220e-4d17-9d28-64028740bb74">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.SuperRes.SuperChromaResUi">
<Settings>
<Passes>1</Passes>
<Strength>1</Strength>
<Softness>0</Softness>
<Prescaler>True</Prescaler>
</Settings>
</Script>
</ChromaScalerPreset>
</ChromaScalers>
<ChromaScalerGuid>d93e8c6f-1a4c-40d2-913a-3773c00d1541</ChromaScalerGuid>
</Settings>
</Script>
</Preset>
<Preset Name="EWA Scaler" Guid="d8eeb145-35fe-461a-b3dd-29f99f68240a">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.EwaScaler.EwaScalerScaler">
<Settings>
<TapCount>Eight</TapCount>
<AntiRingingEnabled>True</AntiRingingEnabled>
<AntiRingingStrength>1</AntiRingingStrength>
<Scaler yaxlib:realtype="Mpdn.Extensions.CustomLinearScalers.SincBlackman" />
</Settings>
</Script>
</Preset>
</ListOfPreset>


EDIT: There's a bug that if you clear the list and paste again you'll get an error. The workaround for now is clear then hit OK to close the dialog and reopen before you paste again. This has been fixed in the GitHub repository.
Zachs
3rd September 2015, 13:53
If I want to use NNEDI3 chroma scaler, how do I configure script render?

NNEDI3 Chroma Scaler is now available.

Usage example:


<ListOfPreset xmlns:yaxlib="http://www.sinairv.com/yaxlib/">
<Preset Name="NNEDI3 Chroma Doubler" Guid="a9367f14-7dd3-4b69-8e4f-9edee4a7db8e">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.NNedi3.Chroma.NNedi3ChromaScaler">
<Settings>
<Neurons1>Neurons32</Neurons1>
<Neurons2>Neurons32</Neurons2>
<CodePath>UnrolledVectorDot</CodePath>
<Structured>False</Structured>
</Settings>
</Script>
</Preset>
<Preset Name="NNEDI3" Guid="434cca2b-f1c2-4ef9-ada8-a78c1e437fc8">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.NNedi3.NNedi3Scaler">
<Settings>
<Neurons1>Neurons32</Neurons1>
<Neurons2>Neurons32</Neurons2>
<CodePath>UnrolledVectorDot</CodePath>
<Structured>False</Structured>
<ChromaScalers>
<ChromaScalerPreset Name="None" Guid="0715cc9b-43c5-4890-96cc-6e24efb3ed61">
<Script yaxlib:realtype="Mpdn.Extensions.Framework.RenderChain.RenderChainUi+IdentityRenderChainUi">
<Settings />
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="ChromaScaler" Guid="8d6c6371-ea0d-4c5b-b789-6f7516983408">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.Chroma.ChromaScaler">
<Settings>
<B>0.3333333</B>
<C>0.3333333</C>
<Preset>MitchellNetravali</Preset>
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="EWA Chroma Scaler" Guid="309ae2b6-a5d2-43f0-9bca-fd4f633a4b63">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.EwaScaler.EwaScalerChromaScalerUi">
<Settings>
<TapCount>Four</TapCount>
<AntiRingingEnabled>False</AntiRingingEnabled>
<AntiRingingStrength>0.85</AntiRingingStrength>
<Scaler yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.EwaScaler.EwaScaler+JincScaler" />
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="NNEDI3 Chroma Doubler" Guid="976ea251-25dd-4eef-a5a6-58e4244c954f">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.NNedi3.Chroma.NNedi3ChromaScaler">
<Settings>
<Neurons1>Neurons32</Neurons1>
<Neurons2>Neurons32</Neurons2>
<CodePath>UnrolledVectorDot</CodePath>
<Structured>False</Structured>
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="OpenCL NNEDI3 Chroma Doubler" Guid="dc47c5e5-abc6-4f01-b211-f28f056e2eca">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.OclNNedi3.Chroma.OclNNedi3ChromaScaler">
<Settings>
<Neurons1>Neurons16</Neurons1>
<Neurons2>Neurons16</Neurons2>
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="SuperChromaRes" Guid="e4cc356c-5e8d-4cb3-94e6-e1650f75e3b0">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.SuperRes.SuperChromaResUi">
<Settings>
<Passes>1</Passes>
<Strength>1</Strength>
<Softness>0</Softness>
<Prescaler>True</Prescaler>
</Settings>
</Script>
</ChromaScalerPreset>
</ChromaScalers>
<ChromaScalerGuid>994c176f-ab9f-47e0-81fe-dc20609a40c2</ChromaScalerGuid>
</Settings>
</Script>
</Preset>
</ListOfPreset>
Shiandow
3rd September 2015, 14:00
By the way, this is a somewhat minor issue, but would it be possible to make the OSD work when no videos are being played?
Zachs
3rd September 2015, 14:02
By the way, this is a somewhat minor issue, but would it be possible to make the OSD work when no videos are being played?

I'll see what I can do but I remember it would involve a fair bit of changes the last time I looked at it.
Zachs
3rd September 2015, 14:04
Similar to Render Script Chain, Audio Chain allows you to chain multiple audio scripts for audio processing.

Example (DRC --> Reclock):

<ListOfIExtensionUi xmlns:yaxlib="http://www.sinairv.com/yaxlib/">
<DynamicRangeCompressor yaxlib:realtype="Mpdn.Extensions.AudioScripts.Mpdn.DynamicRangeCompressor">
<Settings>
<ThresholddB>-15</ThresholddB>
<Ratio>3</Ratio>
<MakeupGaindB>3</MakeupGaindB>
<AttackMs>100</AttackMs>
<ReleaseMs>200</ReleaseMs>
</Settings>
</DynamicRangeCompressor>
<Reclock yaxlib:realtype="Mpdn.Extensions.AudioScripts.Mpdn.Reclock">
<Settings />
</Reclock>
</ListOfIExtensionUi>
Zachs
3rd September 2015, 14:10
@Shiandow BTW there seems to be a bug in NNEDI3 chroma scaler when used as NNEDI3's chroma scaler. It would seem the chroma scaler is active anyway even when we're downscaling (i.e. NNEDI3 Luma itself is inactive).
Anyway I'm going call it a night!
Zachs
3rd September 2015, 14:19
Just a quick heads up. There's a bug in the release where audio scripts won't run for some reason - it's complaining that Cudafy.NET cannot be resolved. It's late here so I'll try to fix it some other time. In short, you can't use audio scripts yet.
Shiandow
3rd September 2015, 14:30
@Shiandow BTW there seems to be a bug in NNEDI3 chroma scaler when used as NNEDI3's chroma scaler. It would seem the chroma scaler is active anyway even when we're downscaling (i.e. NNEDI3 Luma itself is inactive).
Anyway I'm going call it a night!

That's odd, as far as I can tell it shouldn't even reach that part of the code. In fact, I don't seem to be able to reproduce the problem.

Oh well, we'll figure it out tomorrow.
aufkrawall
3rd September 2015, 14:39
Do I have to add a resizer at the end of Script chain to use luma upscaling?

No, it will automatically use chosen upscalers if upscaling is needed.


What's your configuration for NNEDI3 chroma scaling, 16 or 32 neurons?
16 neurons should be enough. Maybe it can make sense to use 32 neurons for first pass if you're watching lots of cartoons, but in most cases 16 should be sufficient.
And even if there are artifacts due to low count of neurons, they are probably harder to spot than with luma.
16 neurons are already more expensive than 8 taps of EWA scalers.
Dlget
3rd September 2015, 16:38
And here's another decent script I like to use:

As i can't use that setting for all sources [sd rendering time was 10-15ms but hd content took nearly 35-40ms & same for 10bit anime 35-40ms]
So i wanted to make different script groups & toggle between them & use best suited script group for individual content[instead of using condition,i wanted to select groups manually by hotkey].
I created a script group using your script.But when i toggle,i see no change in rendering time.[i hoped it'll increase].


<ListOfPreset xmlns:yaxlib="http://www.sinairv.com/yaxlib/">
<Preset Name="Max" Guid="4bea4c95-b0c7-451d-9486-fc53892ff16f">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.ScriptGroup.ScriptGroupScript">
<Settings>
<SelectedIndex>1</SelectedIndex>
<Hotkey>Ctrl+Shift+D1</Hotkey>
<Options>
<Preset Name="Off" Guid="e6bb7235-c6fa-4685-9167-328881496139">
<Script yaxlib:realtype="Mpdn.Extensions.Framework.RenderChain.RenderChainUi+IdentityRenderChainUi">
<Settings />
</Script>
</Preset>
<Preset Name="On" Guid="3115834f-ba83-4be2-9066-2e29f93d19b7">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.ScriptGroup.ScriptGroupScript">
<Settings>
<SelectedIndex>1</SelectedIndex>
<Hotkey></Hotkey>
<Options>
<Preset Name="SuperChromaRes" Guid="16227e78-1997-460b-bd78-f76b332237e7">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.SuperRes.SuperChromaResUi">
<Settings>
<Passes>1</Passes>
<Strength>1</Strength>
<Softness>0</Softness>
<Prescaler>True</Prescaler>
</Settings>
</Script>
</Preset>
<Preset Name="Debanding" Guid="2eedac80-a1d3-4ad9-a8e6-027464debb1c">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.ScriptGroup.ScriptGroupScript">
<Settings>
<SelectedIndex>-1</SelectedIndex>
<Hotkey>Ctrl+Shift+D</Hotkey>
<Options>
<Preset Name="Off" Guid="aecfa54b-7ac8-4f37-a2b5-ad68a482c9f0">
<Script yaxlib:realtype="Mpdn.Extensions.Framework.RenderChain.RenderChainUi+IdentityRenderChainUi">
<Settings />
</Script>
</Preset>
<Preset Name="On" Guid="5508d6a2-9ec8-4b0d-8c11-22f2c96d406e">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.Deband.DebandUi">
<Settings>
<maxbitdepth>8</maxbitdepth>
<power>0.5</power>
<grain>False</grain>
</Settings>
</Script>
</Preset>
</Options>
</Settings>
</Script>
</Preset>
<Preset Name="NNEDI3" Guid="bae19540-a4d6-49af-ad00-194a19de9c0e">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.NNedi3.NNedi3Scaler">
<Settings>
<Neurons1>Neurons32</Neurons1>
<Neurons2>Neurons32</Neurons2>
<CodePath>UnrolledVectorDot</CodePath>
<Structured>False</Structured>
<ChromaScalers>
<ChromaScalerPreset Name="None" Guid="6aa7ce83-40c6-4af3-932e-442fad3449bc">
<Script yaxlib:realtype="Mpdn.Extensions.Framework.RenderChain.RenderChainUi+IdentityRenderChainUi">
<Settings />
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="ChromaScaler" Guid="52c90742-3348-41b2-917d-70b77246db3c">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.Chroma.ChromaScaler">
<Settings>
<B>0.3333333</B>
<C>0.3333333</C>
<Preset>MitchellNetravali</Preset>
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="EWA Chroma Scaler" Guid="770eb8ed-bede-4c35-a15c-a115693f0abe">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.EwaScaler.EwaScalerChromaScalerUi">
<Settings>
<TapCount>Eight</TapCount>
<AntiRingingEnabled>True</AntiRingingEnabled>
<AntiRingingStrength>1</AntiRingingStrength>
<Scaler yaxlib:realtype="Mpdn.Extensions.CustomLinearScalers.SincBlackman" />
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="SuperChromaRes" Guid="926e48ac-220e-4d17-9d28-64028740bb74">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.SuperRes.SuperChromaResUi">
<Settings>
<Passes>1</Passes>
<Strength>1</Strength>
<Softness>0</Softness>
<Prescaler>True</Prescaler>
</Settings>
</Script>
</ChromaScalerPreset>
</ChromaScalers>
<ChromaScalerGuid>d93e8c6f-1a4c-40d2-913a-3773c00d1541</ChromaScalerGuid>
</Settings>
</Script>
</Preset>
<Preset Name="EWA Scaler" Guid="d8eeb145-35fe-461a-b3dd-29f99f68240a">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.EwaScaler.EwaScalerScaler">
<Settings>
<TapCount>Eight</TapCount>
<AntiRingingEnabled>True</AntiRingingEnabled>
<AntiRingingStrength>1</AntiRingingStrength>
<Scaler yaxlib:realtype="Mpdn.Extensions.CustomLinearScalers.SincBlackman" />
</Settings>
</Script>
</Preset>
</Options>
</Settings>
</Script>
</Preset>
</Options>
</Settings>
</Script>
</Preset>
</ListOfPreset>

In OSD we can't see which scripts are active or which upscaling algo is used.It should be implemented so that we can know that selected script is working[like in madVR]
Shiandow
3rd September 2015, 16:57
As i can't use that setting for all sources [sd rendering time was 10-15ms but hd content took nearly 35-40ms & same for 10bit anime 35-40ms]
So i wanted to make different script groups & toggle between them & use best suited script group for individual content[instead of using condition,i wanted to select groups manually by hotkey].
I created a script group using your script.But when i toggle,i see no change in rendering time.[i hoped it'll increase].


[...]



For whatever reason the "EWA" scaler seems to be disabling NNEDI3 somehow. That shouldn't happen. I also noticed some minor bugs that lowered the performance a bit.

Edit: Oh nvm, I misdiagnosed the problem.

You're using a Script Group instead of a Script Chain, which means that it doesn't do chroma scaling, then debanding, then NNEDI3, then EWA. But it only does one of those.

If you copy paste the things in your "On" preset to a Script Chain then it should work.
aufkrawall
3rd September 2015, 17:18
MPDN is somehow wasting lots of GPU power when doing downscaling.
I'm downscaling 4k 60fps down to WQHD with just bilinear scaling for chroma and luma, and GPU usage is at 70% with full clocks.
In madVR with the same settings (I checked them twice, no dithering etc., same queue lengths...), GPU usage is only at 30% with lower clocks.
So something weird must be going on.
Sample:
http://distribution.bbb3d.renderfarming.net/video/mp4/bbb_sunflower_2160p_60fps_normal.mp4

With the latest MPDN versions, I also noticed that video input colorimetric often sets itself to PC BT.601 and improve chroma reconstruction turns itself off. I suppose this randomly happens when changing other settings.
Dlget
3rd September 2015, 17:33
Thanks for fast reply.Now it's working fine.Time to make more Script chain & test them.
still script group & script chain is still bit confusing
Shiandow
3rd September 2015, 19:44
With the latest MPDN versions, I also noticed that video input colorimetric often sets itself to PC BT.601 and improve chroma reconstruction turns itself off. I suppose this randomly happens when changing other settings.

Hmm, sounds like issue #142 (https://github.com/zachsaw/MPDN_Extensions/issues/142)might still not be completely solved after all. Although, did you check if the settings returned to the proper values when the playback has ended?
aufkrawall
3rd September 2015, 19:50
Haven't watched for this yet, but I suppose the settings stayed wrong between several sessions.
I think it also occured when I was playing around with render scripts or at least MPDN scalers.

Edit: Yes, settings stay wrong between different MPDN process sessions.
Shiandow
3rd September 2015, 22:56
Haven't watched for this yet, but I suppose the settings stayed wrong between several sessions.
I think it also occured when I was playing around with render scripts or at least MPDN scalers.

Edit: Yes, settings stay wrong between different MPDN process sessions.

Yeah, I think I just saw something similar. No clue how it happened though. If you've found any way to reproduce it that isn't entirely random then that would help a lot.

I fear that it could be random though, caused by some weird race condition...
Zachs
3rd September 2015, 23:00
MPDN is somehow wasting lots of GPU power when doing downscaling.
I'm downscaling 4k 60fps down to WQHD with just bilinear scaling for chroma and luma, and GPU usage is at 70% with full clocks.
In madVR with the same settings (I checked them twice, no dithering etc., same queue lengths...), GPU usage is only at 30% with lower clocks.
So something weird must be going on.
Sample:
http://distribution.bbb3d.renderfarming.net/video/mp4/bbb_sunflower_2160p_60fps_normal.mp4

MPDN uses a box filter when you do bilinear downscaling. Hardware bilinear is similar to MPDN's nearest neighbour. Not sure if madVR does the same thing now but the last I checked it didn't so they are completely different scalars.
Zachs
3rd September 2015, 23:02
Hmm, sounds like issue #142 (https://github.com/zachsaw/MPDN_Extensions/issues/142)might still not be completely solved after all. Although, did you check if the settings returned to the proper values when the playback has ended?
I did notice this too. I think I know what is causing it. MPDN seems to crash occasionally when you close it not it doesn't show up as a crash. And it had to happen in between the settings commit event pairs.
aufkrawall
3rd September 2015, 23:16
MPDN uses a box filter when you do bilinear downscaling. Hardware bilinear is similar to MPDN's nearest neighbour. Not sure if madVR does the same thing now but the last I checked it didn't so they are completely different scalars.
When I choose Lanczos with 4 taps for both chroma and luma in madVR, I only have 55% GPU usage.
So there simply must be something going wrong in MPDN's downscaling.
Even with nearest neighbor I get 70% usage in MPDN...
Zachs
3rd September 2015, 23:18
What do you get with MPDN's 4 tap downscaler?

Edit: do you have render script chroma scaler active?
aufkrawall
3rd September 2015, 23:32
I forgot to disable frame blending and dithering in madVR.
New results:

Lanczos 4 taps w.o. AR for luma & chroma:
madVR: 46% gpu usage@1126Mhz
MPDN: 75%@1421Mhz

Of course render scripts are completely disabled. Image quality mode is "image quality".
When doing upscaling or no luma scaling, MPDN and madVR pretty much have the same GPU load amount. Just with downscaling there is this huge difference.
Zachs
3rd September 2015, 23:41
Something is definitely wrong. 4 taps and 2 taps can't only give you a difference of 5%. Also with nearest neighbour you should be getting way less since you're not downscaling much at all. Only at higher downscaling factors it would behave differently to madVR hardware bilinear. BTW you haven't got improve chroma enabled have you?

I'll take a look anyway.
aufkrawall
3rd September 2015, 23:43
BTW you haven't got improve chroma enabled have you?

I already checked this to be sure, it was disabled for the numbers above.

Will do some more checks and report if I find anything noteworthy.
Zachs
3rd September 2015, 23:58
Can you also try downscaling other sources? With different resolutions?