Media Player Classic - BE Win32/x64

[huhn]

can you please add more information on what is new/different?

do i interpret this correctly that it is the first d3d11 renderer that can use d3d11 native without an interop?

[v0lt]

can you please add more information on what is new/different?
This is the first release. It is completely new.

[huhn]

silently crashes with a 16b grandiant test: http://www.bealecorner.org/red/test-patterns/Gradient-16bit.png

OSD doesn't scale with image size problematic at UHD.

what is the moving box at the end of the OSD ? GOP indicator?

This is the first release. It is completely new.

i totally understand that it is new but there has to be some new feature like d3d11 native support that i found.

i'm currently getting these informations here: https://mpc-be.org/forum/viewtopic.php?id=381
and i can't read a single word Russian.
and what is planned?

is there something spacial you want us to test.

[v0lt]

silently crashes with a 16b grandiant test: http://www.bealecorner.org/red/test-patterns/Gradient-16bit.png
Thank. I confirm this. Fixed in r662 (git-4610122).
OSD doesn't scale with image size problematic at UHD.
This is not a bug, so specially made.
what is the moving box at the end of the OSD ? GOP indicator?
This is a simple frame rendering indicator. When a new frame is rendered, the rectangle shifts by 1 pixel.
i totally understand that it is new but there has to be some new feature like d3d11 native support that i found.
This open source video renderer does not use system EVR (here you can recall the EVR-CP and Sync VR). It is somewhat similar to Haali VR and madVR, but open source. Our renderer uses Direct3D 9/11, DXVA2 VP and D3D11 VP.
is there something spacial you want us to test.
I do not ask for anything yet. I just announced the release.

[chros]

This open source video renderer does not use system EVR (here you can recall the EVR-CP and Sync VR). It is somewhat similar to Haali VR and madVR, but open source. Our renderer uses Direct3D 9/11, DXVA2 VP and D3D11 VP.

Sounds interesting, you are amazing, guys! :)

[huhn]

because it is open source is it theoretical possible to support the MPDN extension at one point? or is it just to different?

https://github.com/zachsaw/MPDN_Extensions

[v0lt]

because it is open source is it theoretical possible to support the MPDN extension at one point? or is it just to different?
Open source doesn’t have to do anything for you. Do not invent support for anything, it is not. You can simply read open source code at any time (because it is open).

[ryrynz]

Huhn saying MPDN extensions (https://github.com/zachsaw/MPDN_Extensions) are open source, is it possible to support them?

[Aleksoid1978]

Huhn saying MPDN extensions (https://github.com/zachsaw/MPDN_Extensions) are open source, is it possible to support them?

Maybe, as example resizers - if somebody rewrite it :)

[huhn]

thanks for the info.

as a small thing that should be easy to add bicubic 150 is considered to be the "best" simple downscaler can you add it?

[Aleksoid1978]

thanks for the info.

as a small thing that should be easy to add bicubic 150 is considered to be the "best" simple downscaler can you add it?

"Bicubic" already is present.

[ryrynz]

"Bicubic" already is present.

Specifically he wants Bicubic 150.

[Aleksoid1978]

Specifically he wants Bicubic 150.

So what ?? Why ?? :)

[ryrynz]

So what ?? Why ?? :)

It's the sharpest of all the available Bicubic options. It's well known to be one of the lightest and best quality downscalers available.

[v0lt]

We use cubic convolution with a = -0.5.
// bicubic
#define filter_support (2.0)
inline float filter(float x)
{
/* https://en.wikipedia.org/wiki/Bicubic_interpolation#Bicubic_convolution_algorithm */
#define a -0.5
if (x < 0.0)
x = -x;
if (x < 1.0)
return ((a + 2.0) * x - (a + 3.0)) * x*x + 1;
if (x < 2.0)
return (((x - 5) * x + 8) * x - 4) * a;
return 0.0;
#undef a
}
What it does not suit you? Please give real examples.

[huhn]

i'm going to research the different weight and make an example but this will take sometime

[kb968]

Could you make local time a toggle on/off just like remaining time which is CTRL+I..
I like it that way so I can see what is left to play and what the actual time is

Thanks in advanced

MPC-BE (Build 4488)

[ryrynz]

Could you make local time a toggle on/off

It already is.

OSD: Local Time. Key = i

I press i and the time comes up, I press i again and the time goes away.

[Aleksoid1978]

i'm going to research the different weight and make an example but this will take sometime

Where can get it's "Bicubic150" shader ?

[kb968]

Ok, it would be nice to have local time on screen all of the time just like remaining time..

Exit out of mpc-be, then go back into mpc_be and start another movie, one has to turn local time back on again..
Whera as time remaning is there permanent..

[Aleksoid1978]

Local time in OSD is not remember after close.

[huhn]

ok it's just a -1.5.

i changed it and build it on my PC.
i couldn't figure out how to add one more filter to the list and name it so i just change bicubic a to -1.5.

screens:
madVR bicubic 150: https://abload.de/img/madvrbicubic150rmjc8.png
mpcVR bicubic 150: https://abload.de/img/mpcvrudjok.png

source: http://vah.dy.fi/testcard/3840x2160.png

my recommendation would be bicubic 60 (same as in mpc-be) and bicubic 150 downscale only so -0.6 and -1.5.

another real world example:
mpcVRbicubic50: https://abload.de/img/bicubic60n7kpj.png
mpcVRbicubic150: https://abload.de/img/bicubic150fvkhe.png

source: http://uhd-wallpapers.net/images/venice-grand-canal_542.jpeg

[Aleksoid1978]

You are right - 150 is more "Sharper" then 50.

[huhn]

it rings a lot that's why it is only recommended for downscaling while sharp upscaling looks really bad.

of cause there is another one even better algorithm ssim: https://github.com/zachsaw/MPDN_Extensions/tree/master/Extensions/RenderScripts/SSimDownscaler

but bicubic 150 should be good enough for most user.

[Anima123]

MPC Video Renderer v0.2.0.658 (https://github.com/Aleksoid1978/VideoRenderer/releases/tag/0.2.0). The first official release.
Information (https://github.com/Aleksoid1978/VideoRenderer/blob/0.2.0/Readme.md).
Test builds (https://yadi.sk/d/X0EVMKP4TcmnHQ).

How's the MPC Video Renderer handle chroma upscaling (to luma resolution), and can it be customized or will you consider customizing it?

[BetA13]

MPC Video Renderer v0.2.0.658.

tested it, really like it.. Only thing is that it does not support shaders?
If i use teh MPC Video Renderer v0.2.0.658 and enable my deband shader it wont work.. is there a reason for that?

THX..

[v0lt]

How's the MPC Video Renderer handle chroma upscaling (to luma resolution), and can it be customized or will you consider customizing it?
To convert YUV 4:2:0/4:2:2 to RGB, use the DXVA2 or D3D11 video processor.

If you have examples that show the difference between bilinear and bicubic/lanczos chroma upscaling, then I will ask you to provide it to us.

If i use teh MPC Video Renderer v0.2.0.658 and enable my deband shader it wont work.. is there a reason for that?
MPC VR does not support external shaders.

[huhn]

chroma scaler had been check a countless time in the madVR but i can do you another test with it.

the biggest problem is nvidia right now there DXVA chroma scaler is moving the chroma which can results in a lot of aliasing. this has been tested with EVR and madVR. even a simple bicubic 60 should be far better.

[chros]

Image from here (https://www.videohelp.com/software/madVR/old-versions#download).

https://www.videohelp.com/softwareimages/madvr_1196.jpg

[v0lt]

chroma scaler had been check a countless time in the madVR but i can do you another test with it.
I repeat. I need a test file where people can see the difference between bilinear and bicubic/lanczos chroma upscaling.

the biggest problem is nvidia right now there DXVA chroma scaler is moving the chroma which can results in a lot of aliasing. this has been tested with EVR and madVR. even a simple bicubic 60 should be far better.
You are exaggerating the problem. When the driver has an error and simply duplicates the color values (nearest neighbor), users quickly notice this. But in other cases, people do not see the difference in their video.

PS: I talked to users who install madVR, put up heavy settings, and then can’t answer the question "What did not suit you in the standard settings?". They just read one of the stupid instructions from the Internet.

[huhn]

I repeat. I need a test file where people can see the difference between bilinear and bicubic/lanczos chroma upscaling.
as i said i will provide this but this will take sometime i want to do it properly.

You are exaggerating the problem. When the driver has an error and simply duplicates the color values (nearest neighbor), users quickly notice this. But in other cases, people do not see the difference in their video.
i can not disagree that the normal user don't see it but this doesn't change that nvidia is doing it wrong.

PS: I talked to users who install madVR, put up heavy settings, and then can’t answer the question "What did not suit you in the standard settings?". They just read one of the stupid instructions from the Internet.
happens all the time. and other user have to fix it in the madVR thread...
but i can answer your question what doesn't suite me and i'm able to make samples to show the differences. but this needs time.

@chros this image very outdated.

[chros]

Asmodian's chroma omparison (https://forum.doom9.org/showthread.php?p=1817934#post1817934) from 2 years ago, maybe it helps.

[beter]

Update of translation for Chinese Traditional and Dutch:
https://www.sendspace.com/file/d12puh

[Grimsdyke]

@devs. Is there any way to make the OSD bigger in MPC Video Renderer ??

[Aleksoid1978]

@devs. Is there any way to make the OSD bigger in MPC Video Renderer ??

Current - no. In feature - yes :)

[Asmodian]

Asmodian's chroma omparison (https://forum.doom9.org/showthread.php?p=1817934#post1817934) from 2 years ago, maybe it helps.

I did not go all the way down to bilinear, bicubic was the fastest option I demoed. I should probably add nearest neighbor and bilinear.

[huhn]

this test pattern shows obvious difference between chroma scaler accessible for everyone: https://www.youtube.com/watch?v=cSxz1HYhzys

not a friend of these so here is a image from a show:
mpcVR: https://abload.de/img/mpcvrlastsongfyjpr.png (broke nvidia driver?)
madVR:
bicubic 60: https://abload.de/img/bicubic60lastsong5xjnm.png
bilinear: https://abload.de/img/nilinearlastsongnlkzd.png
NN: https://abload.de/img/nnlastsongxyjds.png (reminds me of nvidia)
super xbr 100: https://abload.de/img/superxbr100lastsongijkvr.png

edit: EVRCP for control: https://abload.de/img/evrcpmmkl3.png

[Aleksoid1978]

not a friend of these so here is a image from a show:
mpcVR: https://abload.de/img/mpcvrlastsongfyjpr.png (broke nvidia driver?)
madVR:
bicubic 60: https://abload.de/img/bicubic60lastsong5xjnm.png
bilinear: https://abload.de/img/nilinearlastsongnlkzd.png
NN: https://abload.de/img/nnlastsongxyjds.png (reminds me of nvidia)
super xbr 100: https://abload.de/img/superxbr100lastsongijkvr.png

Original image ?

[huhn]

is h264 lossless fine?
if yes i will encode this frame like that and upload it.

[Aleksoid1978]

is h264 lossless fine?
if yes i will encode this frame like that and upload it.

You can upload video file and show timestamp for test.

[huhn]

http://s000.tinyupload.com/index.php?file_id=07841984126818673936
does this work?

38, 23.976

[Aleksoid1978]

http://s000.tinyupload.com/index.php?file_id=07841984126818673936
does this work?

38, 23.976

Good test.
My result:
EVR - bad
EVR-CP -good(if use 16-bit float surface), bad if 8
madVR(bicubic60) - good
MPC VR DX9 -good(if use 16-bit float surface), bad if 8
MPC VR DX11 - good.

P.S. Verdict - EVR-CP/MPC VR DX9 with 16-bit float surface and MPC VR DX11 is the same quality as madVR bicubic60. So - we don't need to process chromium ourselves, DXVA2/D3D11 Video processor do it not bad :)

[huhn]

i can confirm that MPCVR d3d11 is not broken and looks more like bicubic 60.
super xbr still looks a lot better.

EVR CP mpc-hc is broken for me.

sadly there is an issue with d3d11 it is incorrectly rendering colors they are to "dark" but it is not an level issue.

d3d9: https://abload.de/img/d3d9zxku0.png
d3d11: https://abload.de/img/d3d11mzjog.png

d3d9 looks similar to madVR so it should be correct.

edit: found the source of the issue.
it is p010 input forcing nv12 as input fixes the issue.

[v0lt]

@beter
Thanks. Updated in r4597.

http://s000.tinyupload.com/index.php?file_id=07841984126818673936
Good test video. :thanks:
mpcVR: https://abload.de/img/mpcvrlastsongfyjpr.png (broke nvidia driver?)
Yes, it looks like a bug. This file is played normally by me. On my system (GTX 950) there is a similar problem with the YUY2 format.

[Anima123]

Good test.
My result:
EVR - bad
EVR-CP -good(if use 16-bit float surface), bad if 8
madVR(bicubic60) - good
MPC VR DX9 -good(if use 16-bit float surface), bad if 8
MPC VR DX11 - good.

P.S. Verdict - EVR-CP/MPC VR DX9 with 16-bit float surface and MPC VR DX11 is the same quality as madVR bicubic60. So - we don't need to process chromium ourselves, DXVA2/D3D11 Video processor do it not bad :)

How about MPC VR DX9 10 bit?

[Aleksoid1978]

So - it's bug(at last Nvidia) when convert 10bit 4:2:0 to 8bit RGB using DXVA2 VP. Fix using 16bit RGB output in DXVA2 VP.

[Aleksoid1978]

EVR CP mpc-hc is broken for me.


Check EVR-CP in MPC-BE with Surface format: 16-bit Floating Point.

[huhn]

the bug that NN is used with p010 and 8/10 bit surfaces was just a by product that wasn't planned at all.

my plan was to show the difference between bilinear and bicubic 60.
but there are sadly more DXVA processing issues.

try frame 51, 23.976 you can see black parts in the red text now. this issue comes from not moving the chroma when it is upscaled.

you can test this with madVR using default settings by going to this frame and by pressing control+shift+alt+d to toggle through deinterlancing where madVR usess DXVA by default and where it moves the chroma to the wrong position.

it can be far worse then this example.

[raymondjpg]

Does Encode to AC-3 work in Windows 10? I cannot see it working in MPC-BE 1.5.3 (build 4488).

Does it need an AC3 encoder to be installed in Windows 10? I have the fccHandler AC-3 ACM Codec 2.2 (32 bit and 64 bit) installed, but see no AC-3 encoding.

Can someone point me to a combination of settings in MPC-BE that will enable Encode to AC-3 work in Windows 10?

[ryrynz]

Raymond, you can use AC3Ffilter. Nevermind, use internal filters.