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

[Zachs]

What did you select as the chroma scaler in the OclNNedi3 config dialog?

EDIT: NVM. I reproduced the problem here as well.

[Zachs]

build 3420 is still listed as 2.43.0 here in the about, is that right?

Did it prompt you to update when you were running 2.42.4 though?

[ryrynz]

Did it prompt you to update when you were running 2.42.4 though?

Nope. I was actually watching you upload it and installed it when it was done.

I have installed 2.42.4 and 2.42.3 with extensions 1.19 & 1.18 now to test and neither detect 2.43.0 I get "you have the latest release"

[Zachs]

Same here.

@Belphemur I have a feeling the MPDN Extensions API level check is preventing it from coming through?

[huhn]

What did you select as the chroma scaler in the OclNNedi3 config dialog?

EDIT: NVM. I reproduced the problem here as well.

is the problem from the fact that technically any file scaled with nnedi3 is first upsacel with NN and than treated as an interlaced frame and nnedi3 is used on it two times?

[aufkrawall]

It's most likely just a simple read-out bug.

[Belphemur]

Same here.

@Belphemur I have a feeling the MPDN Extensions API level check is preventing it from coming through?

Yep the logic applied when both Extension API changed in the same time ... was flawed. I corrected everything: https://github.com/zachsaw/MPDN_Extensions/pull/165

The problem was more deep than expected:
https://github.com/zachsaw/MPDN_Extensions/issues/164

[Dlget]

Offtopic:
Which things has significance for rendering time.

I'm using 2 video of same width,same fps.

one is 5500kbps bitrate with rendering time 35ms.
2nd one is 3000kbps bitrate with 46ms rendering time.

so mentioning bitrate,fps,width as condition is not enough to use particular script chain.(as 2nd video gave me dropped frame with same setting)
May be we need something more parameter in conditional chain.

EDIT:Can "Format profile High@L4.1 , High@L3.1 , Main@L2.1 etc" can significantly affect rendering time???

[aufkrawall]

You have to consider GPU stats like GPU usage and clock as well.
Driver doesn't always make the same decision which clock to use when there is low GPU load. If it chooses a lower clock, rendering times will go up.

[Zachs]

is the problem from the fact that technically any file scaled with nnedi3 is first upsacel with NN and than treated as an interlaced frame and nnedi3 is used on it two times?

Nah it's just a bug in the status reporting system.

[eX``]

Hi there =)

I'd like to report a crash I'm having regularly when trying to make comparison on fixed scenes. When I "CTRL+G" and enter a value, I have the following error message: Cannot seek with a negative value. Parameter name: usec. FYI, I also have it if I just click "GO" on the actual value, i.e. without actually writing any value but letting the one already called.

[Zachs]

I'll investigate. Cheers.

[ryrynz]

Received a reply regarding the Youtube Source.



I've tested MPDNx64 in several ways (including default settings) and I don't see any hangs. Though subtitles I also don't see. But according to log they definitely downloaded and downloaded without hang (for test used this clip with pt-BR subtitles). So it need more info to reproduce this issue.

All in all, need check more deeper. The way MPDN works (i.e. two graphs and thus two source filters within the same process) is not expected and thus not tested. Nice to know that it works.

Other (more important imho) thing relates to providing DASH streams. Highest quality on Youtube available only trough them and at current time, as far as I can check, they cannot be played in MPDN (at least video+audio, only audio is possible). DASH streams are disabled by default, to enable need check 'Quality -> Enable DASH streams' in filter properties, Options tab. Then at opening hold Shift key to make appear qualities dialog box and check out all available qualities (or select different variant in Quality -> Manual quality selection). My favorite example: DASH disabled (http://ys.3dyd.com/home/dash_disabled.png), DASH enabled (http://ys.3dyd.com/home/dash_enabled.png) (for this clip (https://www.youtube.com/watch?v=doZYHhF6YXI)). Of course usually there are less qualities but idea is the same.

In case of DASH streams each media stream (video and audio) provided by separated file. In this case filter creates two MEDIATYPE_Stream output pins, one for each file. And the fact that audio comes from second stream pin seems unexpected by MPDN. But anyway, this approach is not very good because each filter instance will download whole video+audio pair separately i.e. will be downloaded twice more data than needed. Btw, this also applies to playing regular qualities, MPDN uses two filter instances so the same file will be downloaded twice.

The better way would be to play video-only stream by one source filter and audio-only by other. But if manually select video-only stream for first filter instance at opening, usage of second filter will not be initiated because expected that it will give the same quality which does not contain audio. Also in current filter state, this cannot be done automatically: which quality to select currently can be configured only through filter properties i.e. it is the same for all filter instances. Need provide some configuration interface which then can be used by MPDN extension (YouTubeSourceProvider?). Need to discuss if this is interesting.

Of course, another variant, for which filter was originally projected, is to use one filter instance for both streams - no waste of data in this way, will be downloaded only data which will be used. But I don't know whether one source filter instance is allowed in MPDN. Also audio stream still will come from second pin which seems not supported at this moment.

My apologies if some of my assumptions about MPDN are wrong, I've meet it just now.

More info about pins. There can be media file data pins (MEDIATYPE_Stream) and subtitles pins (MEDIATYPE_Subtitle, MEDIASUBTYPE_UTF8, FORMAT_SubtitleInfo). Filter contains at least one media pin. In future can be more than two media pins (I want to add free streams selection in manual quality selection dialog box). More useful reason - this will be need for multi-angle (http://www.theverge.com/2015/2/4/7978427/youtube-experimenting-with-multiple-angle-videos) video clips if they will become widely used. Also I don't know why Youtube still haven't multiple audio tracks (e.g. for different languages), quite obvious idea and if it will be available, it also will need separated file streams for each track.

Subtitles are downloading at opening. Each subtitles track has its own pin. Max number of subtitles that I've ever seen is 58 (http://ys.3dyd.com/home/ss.png) (in this clip (http://www.youtube.com/watch?v=vfW5e6jVsMs)).

--
Regards, 3dyd

[ryrynz]

v2.43.1 Changelog:
Fixed URL drag-drop not working


I wondered why that wasn't working..I thought it hadn't been enabled. Thoughts on the auto copy paste?

Belphemur has fixed the updater, I get prompted to 2.43.1 now.

Zach could you have the installer check to see if the other filters are installed in the system and skip the installation of them?

[Zachs]

EDIT:Can "Format profile High@L4.1 , High@L3.1 , Main@L2.1 etc" can significantly affect rendering time???

With software decode it shouldn't affect render time as long as the input format and size are the same.

[Zachs]

It's most likely just a simple read-out bug.

Should be fixed with latest github. Can you check and see if there's anything else I've missed?

[edison]

how can I repeat play the current playing file?

[ryrynz]

how can I repeat play the current playing file?

Use the playlist. Select the repeat playlist icon (two arrows making a circle)
This will repeat everything in the playlist. If you have other files there you'll need to remove them.

[lanzorg]

I have strange issues with MPDN and the leshcat's amd/intel hybrid drivers. MPDN can't find my laptop amd graphic card, only the intel one. And if I set MPDN as an application that needs the powerful graphic card, MPDN uses the intel one (defined in the osd) but I have no video at all, black screen. In the MPDN's options there is only intel hd3000 gpu.

I tried with madvr and mpv, the amd dedicated gpu is used correctly, so I think it's not a driver's issue.

Is it a known issue? Is there a fix?

[aufkrawall]

Should be fixed with latest github. Can you check and see if there's anything else I've missed?
It shows it correctly now. :)
I think there's just one little glitch when opening a PNG image: The arrows of the OSD implicate that there is no chroma upscaling performed (which is correct), but it still shows the chroma scaler selected in MPDN next to it:
http://abload.de/img/1rgslf.png (http://abload.de/image.php?img=1rgslf.png)
I think it would be cleaner to show no chroma scaler if no chroma scaling is actually performed.

[Shiandow]

It shows it correctly now. :)
I think there's just one little glitch when opening a PNG image: The arrows of the OSD implicate that there is no chroma upscaling performed (which is correct), but it still shows the chroma scaler selected in MPDN next to it:
http://abload.de/img/1rgslf.png (http://abload.de/image.php?img=1rgslf.png)
I think it would be cleaner to show no chroma scaler if no chroma scaling is actually performed.

That's not a glitch. It tells you that while it isn't scaling the chroma, it is in fact still shifting the chroma (to correct the offset) using Sinc-Blackman.

[aufkrawall]

Oo, that's quite techie.
Maybe too techie, since chroma offset is usually not of interest?
I could imagine that there often will be questions about it because the main purpose of render script OSD is probably to just check if the render script is doing what the user has intended.

[Dlget]

<ListOfPreset xmlns:yaxlib="http://www.sinairv.com/yaxlib/">
<Preset Name="EWA Chroma Scaler" Guid="af9fde70-2a83-460b-89c0-8b7f2e54f1ba">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.EwaScaler.EwaScalerChromaScalerUi">
<Settings>
<TapCount>Six</TapCount>
<AntiRingingEnabled>True</AntiRingingEnabled>
<AntiRingingStrength>1</AntiRingingStrength>
<Scaler yaxlib:realtype="Mpdn.Extensions.CustomLinearScalers.SincHann" />
</Settings>
</Script>
</Preset>
<Preset Name="Deband" Guid="bf52b2f3-9452-4c70-9bbd-fea981c65c92">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.Deband.DebandUi">
<Settings>
<maxbitdepth>10</maxbitdepth>
<power>0.75</power>
<grain>False</grain>
</Settings>
</Script>
</Preset>
<Preset Name="OpenCL NNEDI3" Guid="9a5e5b59-c324-437b-8ede-90a30fd11bd6">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.OclNNedi3.OclNNedi3Scaler">
<Settings>
<Neurons1>Neurons64</Neurons1>
<Neurons2>Neurons32</Neurons2>
<ChromaScalers>
<ChromaScalerPreset Name="None" Guid="f204908b-1256-4e68-93d6-568cec967020">
<Script yaxlib:realtype="Mpdn.Extensions.Framework.RenderChain.RenderChainUi+IdentityRenderChainUi">
<Settings />
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="Bilateral" Guid="8356bb60-57ba-4f29-a57d-1690313b7f29">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.Bilateral.BilateralUi">
<Settings />
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="ChromaScaler" Guid="db16d7d7-6de8-43d3-858d-1cbe9e60ae38">
<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="9ed782fc-4c8d-4845-91ae-e266e818fdd8">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.EwaScaler.EwaScalerChromaScalerUi">
<Settings>
<TapCount>Four</TapCount>
<AntiRingingEnabled>True</AntiRingingEnabled>
<AntiRingingStrength>1</AntiRingingStrength>
<Scaler yaxlib:realtype="Mpdn.Extensions.CustomLinearScalers.SincHann" />
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="NNEDI3 Chroma Doubler" Guid="61f1486d-51f7-4b80-8b03-f6558e9711a6">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.NNedi3.Chroma.NNedi3ChromaScaler">
<Settings>
<Neurons1>Neurons16</Neurons1>
<Neurons2>Neurons16</Neurons2>
<CodePath>ScalarMad</CodePath>
<Structured>False</Structured>
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="OpenCL NNEDI3 Chroma Doubler" Guid="c3648a86-aba5-4281-844d-8bc11dc8dbbf">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.OclNNedi3.Chroma.OclNNedi3ChromaScaler">
<Settings>
<Neurons1>Neurons16</Neurons1>
<Neurons2>Neurons16</Neurons2>
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="SuperChromaRes" Guid="bc96da87-ff1e-4186-a39b-42762db557fd">
<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="Image Processor" Guid="56def538-6693-4e59-b69e-9e3e517d7b36">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.ImageProcessor.ImageProcessorScript">
<Settings>
<ShaderFileNames>
<String>AdaptiveSharpen\adaptive sharpen - 2015-08-19 - Pass one.hlsl</String>
<String>AdaptiveSharpen\adaptive sharpen - 2015-08-19 - Pass two.hlsl</String>
</ShaderFileNames>
<CompatibilityMode>True</CompatibilityMode>
</Settings>
</Script>
</Preset>
</ListOfPreset>

This is setting for 720p you gave in pastebin link.(i just modified tap count & neuron count for my use)
what does it do???
EWA croma scaler-->deband-->nnedi3 image doubler(with ewa as croma scaler)-->image processor --> & then required luma or croma scaler in option menu(not in scriptchain one)

what i understand from this- 1st croma is upscaled for target display size-->then image is doubled & then again croma is upscaled to match wih luma part-->image processor-->any scaler needed for making the video fit to target display size

why croma is upscaled twice?isn't image doubler is enough for requirement(as video width 1280 & display width 1920,image doubler would make it 2560 pixel & ewa croma scaler would make croma part near to it).at end required luma or croma scaler is used(downscaler)


Below one is setting for <720p
<ListOfPreset xmlns:yaxlib="http://www.sinairv.com/yaxlib/">
<Preset Name="OpenCL NNEDI3 Chroma Doubler" Guid="8d7e0110-9910-4f9c-95a7-aaef0292e552">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.OclNNedi3.Chroma.OclNNedi3ChromaScaler">
<Settings>
<Neurons1>Neurons32</Neurons1>
<Neurons2>Neurons16</Neurons2>
</Settings>
</Script>
</Preset>
<Preset Name="OpenCL NNEDI3" Guid="6fc6523a-1ad2-4a50-a750-41d750e63a09">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.OclNNedi3.OclNNedi3Scaler">
<Settings>
<Neurons1>Neurons64</Neurons1>
<Neurons2>Neurons32</Neurons2>
<ChromaScalers>
<ChromaScalerPreset Name="None" Guid="c6c5e8a1-d85d-402a-b86f-d2c3ec4d2824">
<Script yaxlib:realtype="Mpdn.Extensions.Framework.RenderChain.RenderChainUi+IdentityRenderChainUi">
<Settings />
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="Bilateral" Guid="1886fda1-1e2d-47fc-9278-29394a96d373">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.Bilateral.BilateralUi">
<Settings />
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="ChromaScaler" Guid="7a869184-7175-41bc-ae78-2a3642c02094">
<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="ffdb9baf-ed88-4eff-95fa-8052ffd3f2c4">
<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="277eff2a-151e-4f4c-b389-12b47c500a2f">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Shiandow.NNedi3.Chroma.NNedi3ChromaScaler">
<Settings>
<Neurons1>Neurons16</Neurons1>
<Neurons2>Neurons16</Neurons2>
<CodePath>ScalarMad</CodePath>
<Structured>False</Structured>
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="OpenCL NNEDI3 Chroma Doubler" Guid="007f58aa-7326-49fb-80f3-9993e89233a0">
<Script yaxlib:realtype="Mpdn.Extensions.RenderScripts.Mpdn.OclNNedi3.Chroma.OclNNedi3ChromaScaler">
<Settings>
<Neurons1>Neurons32</Neurons1>
<Neurons2>Neurons16</Neurons2>
</Settings>
</Script>
</ChromaScalerPreset>
<ChromaScalerPreset Name="SuperChromaRes" Guid="a63240c1-4c6a-4abc-82bb-ce28f40de23b">
<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>2b4780b6-7aa7-478b-be30-36eb5a92d296</ChromaScalerGuid>
</Settings>
</Script>
</Preset>
</ListOfPreset>

in this 1st croma is doubled.Then luma is doubled along with croma.
why croma is doubled twice? isn't luma more imp part?



I could not make sense of these setting.In madVR,it just use doubler ,then any scaling required.

[aufkrawall]

When NNEDI3 for luma is used, chroma has to be scaled again.
If you don't choose chroma doubling in madVR, it automatically falls back to the main chroma scaler. In MPDN, you have do define this scaler by yourself (but have freedeom of choice for it, apart from NNEDI3 and main chroma scaler).

[Shiandow]

Oo, that's quite techie.
Maybe too techie, since chroma offset is usually not of interest?
I could imagine that there often will be questions about it because the main purpose of render script OSD is probably to just check if the render script is doing what the user has intended.

Maybe it's a bit technical, but it's not like it isn't doing anything. Exactly which scaler is used is important for both the image quality and the performance. Besides I'd rather the OSD displays something unimportant than not display something important.

[Zachs]

in this 1st croma is doubled.Then luma is doubled along with croma.
why croma is doubled twice? isn't luma more imp part?

I could not make sense of these setting.In madVR,it just use doubler ,then any scaling required.

The choice is yours. By default, chroma in NNEDI3 image doubler is set to "None", which means only Luma is doubled (chroma is scaled with MPDN's internal scalers). If you want to use NNEDI3 for chroma all the way, then it has to be doubled twice since chroma is half (in each direction) the size of the luma for 4:2:0 sources.

[aufkrawall]

Maybe it's a bit technical, but it's not like it isn't doing anything. Exactly which scaler is used is important for both the image quality and the performance. Besides I'd rather the OSD displays something unimportant than not display something important.
What about adding information that it's regarding chroma offset, and not actually upscaling? Or do you think this is already covered by the two arrows?

[Shiandow]

What about adding information that it's regarding chroma offset, and not actually upscaling? Or do you think this is already covered by the two arrows?

Well I don't mind changing the symbol, but ideally the symbol should be enough to tell you that the image is interpolated in some way, but without upscaling or downscaling. The statuses aren't really meant to explain why it's doing something, they're just there to tell you that it is. We're probably going to need to put together a short explanation of all the symbols at some point (especially for scalers, which have become quite complex).

[ryrynz]

The statuses aren't really meant to explain why it's doing something, they're just there to tell you that it is. We're probably going to need to put together a short explanation of all the symbols at some point (especially for scalers, which have become quite complex).

Why not just list the chain vertically?
Offset =
First chroma resize =
Luma resize =
Post processing =

Something like that.

[Zachs]

It already does.

[ryrynz]

Oh yup, got the wrong idea from the offset screenshot, I see now.

I notice this OSD sits not far alongside the player OSD before entering FSE mode and then shifts to it's default far right position, can that be avoided?

[aufkrawall]

Another topic: With conditional render scripts there can be done almost everything even today.
But I think it would be much easier to use if we had variables like "scaling factor". When people share render scripts they would also be more applicable in a universal way.

[Zachs]

That's not a glitch. It tells you that while it isn't scaling the chroma, it is in fact still shifting the chroma (to correct the offset) using Sinc-Blackman.

Actually it is a bug. Even when ChromaOffset is Zero (e.g. PNG file with RGB input), the chroma convolver still gets shown, which is incorrect - I've committed a fix on GitHub.

[Zachs]

Another topic: With conditional render scripts there can be done almost everything even today.
But I think it would be much easier to use if we had variables like "scaling factor". When people share render scripts they would also be more applicable in a universal way.

Good idea. Can you add a request on GitHub please?

[Zachs]

Hi guys,

There's a new test build available: http://mpdn.zachsaw.com/Test%20Builds/3440/

With the latest MPDN Extensions source from GitHub, you should now be able to use youtube-dl (and similar utilities) with MPDN.

The major change to allow this to work required MPDN to use just a single DirectShow graph. This change unfortunately also means seamless track changes for video / subtitles can no longer function (hence removed). OTOH XySubFilter's tray icon menus now work as expected.

This change also allows the YouTube source filter to download just the one stream. Subtitles are now also supported (3DYD will be releasing the fixed version soon that no longer hangs when subtitles are enabled).

It's a major change so I'd appreciate it if you guys could give it a proper test!

Cheers,
Zachs

EDIT: Found a problem "pipe:0" (youtube-dl) isn't working so don't test that yet.

[Zachs]

Latest test build 3442 (http://mpdn.zachsaw.com/Test%20Builds/3442/) should now properly support streaming via stdin.

Usage example:

youtube-dl -o - https://www.youtube.com/watch?v=C0DPdy98e4c | MediaPlayerDotNet.exe --stdin


Note: stdin is non-seekable so if you try to seek the stream will terminate. You can't restart the stream either so you'll need to close MPDN and start it via the command line arguments again. I'll tidy up the GUI to make sure seeking has no effect and stopping the stream is equivalent to closing a media file.

[Shiandow]

Hi,

Just thought I should mention that the latest MPDN extensions also have a new system for displaying the render script status. In principle the OSD should be the same (or equivalent) to the old system, so you probably won't see any difference, but please report any unexpected behaviour or bugs. Especially things like doubly nested scripts (e.g. using SuperRes in a SuperRes prescaler), and the Scripted Render Chain might still need some testing.

In theory the new system should be more resistant to bugs than the old system, though, so feel free to really try to break it. Of course illegible, but technically correct, statuses don't count as "breaking" it.

[Anima123]

Could developers please offer other builds together with AnyCPU version for Test?

[Zachs]

I'll upload other builds later, probably after I'm done with polishing up the UI for streaming.

[trandoanhung1991]

Is it possible to allow configuring Navigation extension? I'd like to be able to change right/left to jump x second instead of 5 key frames.

Currently to do this I'd have to use the sources and modify them myself, correct?

[Zachs]

Yeah unfortunately a user friendly key mapper is still missing. If anyone feels like contributing we'd really appreciate it.

[Zachs]

Could developers please offer other builds together with AnyCPU version for Test?

You can give test build 3445 (http://mpdn.zachsaw.com/Test%20Builds/3445/) a go.

[elraffa]

Hi Zachs..I would like to ask if you could incorporate an option to stretch hardcoded videos in MPDN.. I have a small monitor and films with black bands are too small for me.. In potplayer there is an option to do this (frame height +), like the image
http://i.imgur.com/Rn5fd5h.jpg

[Zachs]

I'll add that to my todo list.

[Zachs]

Just a heads up. A new test build (3448 (http://mpdn.zachsaw.com/Test%20Builds/3448/)) is now available which fixes a number of bugs.

[japa]

I get one or more extensions failed to load with this latest version, is this expected ?

[Shiandow]

There have been some changes to the extension API, so you need to combine the right version of the extensions with the right version of MPDN.

The only supported combinations are:

-The last released versions of MPDN with the last released version of the extensions.

-The latest test version of MPDN with the latest extensions on github.

All other combinations are deprecated, or won't work.

[japa]

Thanks, all sorted now. :D

BTW I like the @elraffa's suggestion I used that in MPC-HC and I miss it here.

[aufkrawall]

Good idea. Can you add a request on GitHub please?
Shiandow did it.
Thanks, with intervals it should be fairly easy to use. However, I'm too lazy atm to change my current script building. :o
I think considering the total amount of pixels of a source is the much better way than having to define every single bit manually regarding certain source resolutions (e.g. when a video with vertical format shows up, you may have to add a rewritten version of every existing scripts if they were just applicable for 16:9).

[aufkrawall]

Double post time, isn't it? :D

Well, I rebuilt my scripts with ScalingFactor conditionals and it took just five minutes and it works already like a charm. :devil:
I spent hours on my previous scripts which are based on source and target resolutions. :o

Since they work in a universal way, maybe bundle some presets?
e.g. installer could ask wich preset to use (they'd differ in required GPU power) and also makes some adjustments to the internal MPDN scalers based on the choice (e.g. Spline for downscaling etc.). Of course this would be totally optional.

Advantage would be that also users who don't want to understand conditional render scripts could get "best" quality, so it would be more attractive to a wider audience. Also, users could learn by the render scripts templates and e.g. start with simple modifications of them.