Media Player Classic Home Cinema (MPC-HC) - DXVA!

[6205]

Why a new icon for the x64 version "is bad"?
As you can see many other people (everybody else) seems to think that "is good" cause as I've said many, many, times we need to easily distinguish between the two version (file format association ) on systems with both x86 and x64 version

Uhm, no. This is nonsense. A icon represents a branding. Give me a example of different branding of 32 vs 64bit application somewhere else. Both version should use the same icons. End of discussion. You may have your own opinion, but it's wrong :)

Ability to distinguish between the two versions on systems with both versions should be done differently. As an example should MPC-HC developers take Microsoft approach. Has 64 bit Internet Explorer or Windows Media Player different icons?

[Mercury_22]

Uhm, no. This is nonsense. A icon represents a branding. Give me a example of different branding of 32 vs 64bit application somewhere else. Both version should use the same icons. End of discussion. You may have your own opinion, but it's wrong :)

Ability to distinguish between the two versions on systems with both versions should be done differently. As an example should MPC-HC developers take Microsoft approach. Has 64 bit Internet Explorer or Windows Media Player different icons?

So you're happy you can't distinguish between the two version of Internet Explorer or Windows Media Player ? and you think that approach is making things easier for the user ? Really ?
In your logic the mpc-hc64.exe should also be renamed to mpc-hc.exe too NO?

[Underground78]

We plan to make the x86 and x64 builds totally independent at least settings-wise and for the context menu entries (which means that there will be MPC-HC and MPC-HC x64). I don't know what is planned for icons but I understand your point.

[Px]

My 5 cents on 32 vs 64 icons: they must be generally same, but have small difference, so user can understand that this is one application and easily distinguish different bitness versions

[v0lt]

I forgot why you need two versions of the player at the same time? Do not have enough x86 version?

[pankov]

Guys,
I have a problem with VSFilter and more precisely with it's ability to delay the subtitles and even more precisely the way ZoomPlayer controls it in real time to change the delay value. I guess ZoomPlayer uses some kind of interface to do it but I'm not sure.
The latest version that I've found on xvidvideo.ru to be working is 1.5.2.3251 and the next one there (1.5.2.3314) is broken. Sadly there are ~60 versions in between but I can't find any of them so I can't narrow it down more.
Also I apologize for not being able to explain the problem more technically but I hope you'll be able to understand.

[betaking]

can not compiled last mpc-hc svn
1>DSUtil.cpp : warning C4819: 该文件包含不能在当前代码页(936)中表示的字符。请将该文件保存为 Unicode 格式以防止数据丢失
FontInstaller.cpp
1>DSUtil.cpp(1955): warning C4819: 该文件包含不能在当前代码页(936)中表示的字符。请将该文件保存为 Unicode 格式以防止数据丢失
1>DSUtil.cpp(2412): error C2001: 常量中有换行符
1>DSUtil.cpp(2413): error C2001: 常量中有换行符
1>DSUtil.cpp(2412): fatal error C1057: 宏扩展中遇到意外的文件结束
GolombBuffer.cpp
H264Nalu.cpp
HdmvClipInfo.cpp
MediaTypeEx.cpp
MediaTypes.cpp
NullRenderers.cpp
text.cpp
vd.cpp
vd_asm.cpp
1>已完成生成项目“C:\mpc-hc\src\DSUtil\DSUtil.vcxproj”(build 个目标)的操作 - 失败。

[betaking]

{&DXVA_Intel_H264_ClearVideo, _T("H.264 bitstream decoder, ClearVideo?)},// Intel ClearVideo H264 bitstream decoder
{&DXVA_Intel_VC1_ClearVideo, _T("VC-1 bitstream decoder, ClearVideo?)},// Intel ClearVideo VC-1 bitstream decoder
change to
{&DXVA_Intel_H264_ClearVideo, _T("H.264 bitstream decoder, ClearVideo")},// Intel ClearVideo H264 bitstream decoder
{&DXVA_Intel_VC1_ClearVideo, _T("VC-1 bitstream decoder, ClearVideo")},// Intel ClearVideo VC-1 bitstream decode
compiled is ok!

[JanWillem32]

It's probably the locational ANSI-Unicode conversion that's giving you problems. I'll correct it. Thanks for noticing.

[betaking]

It's probably the locational ANSI-Unicode conversion that's giving you problems. I'll correct it. Thanks for noticing.

Thanks, and UDPReader.cpp have this problem too! so i conver UDPReader.cpp to Unicode too!

[JanWillem32]

Interesting, can you test if saving UDPReader.cpp as UTF-8 does solve your problem? It can be done with the normal notepad, with "Save as". The developers can later on take a look at some other files that include the somewhat code page sensitive characters for conversion and prevent problems like this from happening again.

[betaking]

Interesting, can you test if saving UDPReader.cpp as UTF-8 does solve your problem? It can be done with the normal notepad, with "Save as". The developers can later on take a look at some other files that include the somewhat code page sensitive characters for conversion and prevent problems like this from happening again.

test if saving UDPReader.cpp as UTF-8 does solve your problem? It can be done with the normal notepad, with "Save as".
test not solve my problem!
saving UDPReader.cpp as Unicode solve my problem!

[Underground78]

I forgot why you need two versions of the player at the same time? Do not have enough x86 version?

Some people want to use the x64 version but some DS filters still only exist on x86 I guess.

Guys,
I have a problem with VSFilter and more precisely whit it's ability to delay the subtitles and even more precisely the way ZoomPlayer controls in real time it to change the delay value. I guess ZoomPlayer uses some kind of interface to do it but I'm not sure.
The latest version that I've found on xvidvideo.ru to be working is 1.5.2.3251 and the next one there (1.5.2.3314) is broken. Sadly there are ~60 versions in between but I can't find any of them so I can't narrow it down more.
Also I apologize for not being able to explain the problem more technically but I hope you'll be able to understand.

If you don't want your issue to be lost, you will need to report it on Trac.

Between does someone know if some graphic cards support DXVA for video resolution higher than 1080p ?

[betaking]

Some people want to use the x64 version but some DS filters still only exist on x86 I guess.



If you don't want your issue to be lost, you will need to report it on Trac.

Between does someone know if some graphic cards support DXVA for video resolution higher than 1080p ?

GeForce 410M, GT 520 GF119

VP5

D

April 2011

Introduced 4k x 2k video decoding

[GTPVHD]

http://www.anandtech.com/show/4380/discrete-htpc-gpus-shootout/11

The GT 520 is the first (and only GPU as of now) to support the VDPAU Feature Set D.

We asked NVIDIA about the changes in the new VDPAU feature set and what it meant for Windows users. They indicated that the new VPU was a faster version, also capable of decoding 4K x 2K videos. This means that the existing dual stream acceleration for 1080p videos has now been bumped up to quad stream acceleration.

3488 needs to be changed to allow 4k x 2k DXVA decoding on GT 520 and future Nvidia Kepler GPUs(GeForce 600 series) with the new Feature Set D hardware decoder.

[G_M_C]

@ GTPVHD & betaking
Anadtecht's article also mentioned that the 520 doesnt have a way of inputting 4K resolutions (over HDMI). The connection is 1.4, but Nv hasnt implemented the 4k part of the specification.

So despite (techically)beeing able to decode a 4K video, there is no way to get it done in reality (anyway as far as i understand Anandtech's article :p)

[nevcairiel]

You can decode the 4k x 2k just fine, the problem it talks about is actual output of anything higher then 1080p over HDMI. But of course, you can still down-scale the decoded result. :)

[hoborg]

Hi.
I am using MPC-HC only as a player, all internall filters are disabled.
For decoding i use LAV splitter + audio decoder + FFDshow for video.

The problem i have is that MPC-HC freeze randomply when opening .MPG files if is use libmpeg2 as a decoder in ffdshow.

There is no such issue if i open MPG directly in graphstudio. So can this be problem of MPC-HC player?

[v0lt]

It's probably the locational ANSI-Unicode conversion that's giving you problems. I'll correct it. Thanks for noticing.
_T("©") -> _T('\xA9')
_T("™") -> _T('\x99')
In this way we can solve the problem?
(I can not test right now)

[JanWillem32]

The trade mark sign is officially located at U+2122.
Using numerical references to characters should work, but there's also a problem in UDPReader.cpp with the common character é (U+00E9). ANSI encoding of characters common to the code page I'm using might not work for other code pages. The solution of converting to UTF-8 would be rather painless. Unfortunately, it doesn't work, only UTF-16LE does. The problem with that encoding is that it takes twice the space for each file, and mostly stores zeroes for the characters contained in the [0, 127] interval.
I can understand the compiler having problems with the code page mess, but the fact that it fails on UTF-8 needs some investigating. We might need to change a compiler setting or something to make it work.

[Underground78]

3488 needs to be changed to allow 4k x 2k DXVA decoding on GT 520 and future Nvidia Kepler GPUs(GeForce 600 series) with the new Feature Set D hardware decoder.

Yes, that's why I asked.

Hi.
I am using MPC-HC only as a player, all internall filters are disabled.
For decoding i use LAV splitter + audio decoder + FFDshow for video.

The problem i have is that MPC-HC freeze randomply when opening .MPG files if is use libmpeg2 as a decoder in ffdshow.

There is no such issue if i open MPG directly in graphstudio. So can this be problem of MPC-HC player?

It can be, when you say randomly, how often is it ?

[hoborg]

It can be, when you say randomly, how often is it ?

Well, often. Lets say it is 1:1 - one time it is working, second not.
It happend with all MPEG including VOBs.

I tested the same on slow computer (atom) and by some reason i was not able to reproduce it, but opening the video is much slower.
Here i have i5 2400S and opening is nearly instant - can be the CPU speed source of the issue? Maybe it need some delay?

BTW, i try to set MPC-HC internal MPEG splitter instead of LAV splitter and crash no longer happend.
So it must be something with LAV spliter + MPC-HC combination.

[VipZ]

The problem i have is that MPC-HC freeze randomply when opening .MPG files if is use libmpeg2 as a decoder in ffdshow.


I found libmpeg2 to be very unstable, soon as I switched to libav, all issues disappeared.

[hoborg]

I found libmpeg2 to be very unstable, soon as I switched to libav, all issues disappeared.

Well, some DVDs are not working correctly (navigation) with libav, no problem with libmpeg2.

[Px]

I forgot why you need two versions of the player at the same time? Do not have enough x86 version?
Well, I use three players :D, bsplayer as main, to view video on TV, mpc x32 to view video on main display, and mpc x64 when "something is wrong" :rolleyes:

[v0lt]

3488 needs to be changed to allow 4k x 2k DXVA decoding on GT 520 and future Nvidia Kepler GPUs(GeForce 600 series) with the new Feature Set D hardware decoder.
Has anyone tested it?

There are few other data.
http://en.wikipedia.org/wiki/Nvidia_PureVideo
The fifth generation of PureVideo HD, introduced with the Geforce GT 520, has significantly improved performance when decoding H.264 (and, from an already much higher level, other codecs), it is also capable of decoding 4K x 2K videos.

The fifth generation PureVideo HD is sometimes called "PureVideo HD 5" or VP5, although this is not an official Nvidia designation. This generation of PureVideo HD corresponds to Nvidia VDPAU Feature set D which due to limitations in all current VDPAU drivers does not support decoding higher resolutions than 2048x2048.
Therefore need the real tests.

[GTPVHD]

Ignore the wiki, it's written by a clueless person. If Anandtech, which is always in contact with Nvidia says it supports it, it supports it. The documentation cited by the wiki article is outdated.

Anyone can edit Wikipedia and post unverified and false info. Anandtech's reviewer for the article confirmed it with Nvidia the company themselves.

[nevcairiel]

The Hardware supports it, but i don't think the software (the driver) properly exposes it through DXVA yet.

[VipZ]

Well, some DVDs are not working correctly (navigation) with libav, no problem with libmpeg2.

True, I don't play DVD's with navigation so didn't come across this potential bug.

[Rectal Prolapse]

I've just noticed that this ticket has been closed:

http://sourceforge.net/apps/trac/mpc-hc/ticket/71

Congratulations on fixing this long-standing issue that has been a part of mpc-hc for 2 years! Kudos to v0lt for the fix - you will be remembered always.

[Toddler Naruto]

I do NOT recommend to do that. Icons will not fit to correct file type. Many things have changed since revision 3088 - last revision with old icons. Since then MPC-HC supports many new formats and new icons has been added to icon library, therefore old mpciconlib.dll file will not work properly. Also ordering is different.

For some file types will be icons missins, for some will MPC-HC display wrong icon. For example(when you see linked image) for MKV file will MPC-HC show D2V icon (no. 22) from old icon library. http://oi54.tinypic.com/ly91j.jpg

Anyway, if you wanna keep at least some old icons, i have deleted entire mpciconlib.dll and made afterward re-association process. This way i have all icons the same for all file types which are now taken from mpc-hc.exe file directly.

Hi, I already deleted the new mpciconlib.dll file, then I moved/copied the old mpciconlib.dll file to where the new version used to be, and finally I re-associated the icons.

Thanks for the help, though I did not need it, the old icons are working fine for me.

[ceb]

I have an ATI 5770 and use EVR CP, is the "YV12 Chroma Upsampling" shader still needed?
What is the difference between pre-resize and post-resize pixel shaders? I tried both but I hardly see any difference, post-resize seems slightly better (I use Sharpen Complex 2 and YV12 Chroma Upsampling). Which one should I use?

[fairchild]

I have an ATI 5770 and use EVR CP, is the "YV12 Chroma Upsampling" shader still needed?
What is the difference between pre-resize and post-resize pixel shaders? I tried both but I hardly see any difference, post-resize seems slightly better (I use Sharpen Complex 2 and YV12 Chroma Upsampling). Which one should I use?

I've asked this several times and never have gotten an answer. From what I've read if you use say ffdshow video decoder and set it to output RGB32 and have High Quality YV12 to RGB Conversion and Dithering checked, then the chroma upsampling bug won't affect you.

For sharpening, you want to generally use the post-resize pixel shader. For YV12 chroma upsampling I don't know if you should use post or pre-resize pixel shaders.

[leeperry]

I've asked this several times and never have gotten an answer.
how about comparing it yourself using this test pattern (http://www.mediafire.com/?7cjlfuid35u1hbe).

[fairchild]

how about comparing it yourself using this test pattern (http://www.mediafire.com/?7cjlfuid35u1hbe).

I've run that clip and I can't really notice much of a difference between different renderers and decoder combos. Is there a particular letter that I should be focussing on or something? I understand that if chroma isn't upsampling correctly then the red letters can blur into the black?

[leeperry]

I've run that clip and I can't really notice much of a difference between different renderers and decoder combos. Is there a particular letter that I should be focussing on or something? I understand that if chroma isn't upsampling correctly then the red letters can blur into the black?
You need to magnify a lot, the point resizing of the old ATi drivers would make big squares...but you don't want the chroma to be too blurry either IMHO. You could compare to what mVR does, personally my fav chroma upsampler in mVR is Softcubic80...100 is too blurry.

[JohnLai]

Problem Event Name: APPCRASH
Application Name: mpc-hc64.exe
Application Version: 1.5.3.3497
Application Timestamp: 4e31d056
Fault Module Name: mpc-hc64.exe
Fault Module Version: 1.5.3.3497
Fault Module Timestamp: 4e31d056
Exception Code: c0000005
Exception Offset: 00000000006583aa
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 151d
Additional Information 2: 151d52bb7e837a966a10eaa9d53f8929
Additional Information 3: 53c2
Additional Information 4: 53c2c7d603524dfaff1d0d80dcf60c81

Crashes still happen.....when exiting from D3D mode. If I played any media without D3D mode, no crash.

[v0lt]

@JohnLai
A long time is it? Which version is right?

[JohnLai]

If you want the exact version of non-crash, I dont know. However, built 3267 was fine.

Ever since modification 3286 onwards, kept getting stackhash error and I stopped to test at version 3329. Only recently, I started to test again and mpc keeps getting APPCRASH after exiting D3D mode since 3485.

[pancserzso]

Some mp4 files trigger a hard restart on my computer using DXVA!

1. first play, AMD graphics driver stops working if I continue working after this, but without graphic activities, then everything works ok.
2. if I start one of those files AGAIN, when MPC-HC opens then 2nd time, enlarges the window and in a second my system restarts!

I am using these versions:
x264 build 1995
MPC-HC build 1.5.2.3423
EVR Custom default, only using internal filters
AMD Radeon 5650M, Catalyst 11.3
Win 7 64

Here is one of the files which gives me this "instant restart":
http://ifile.it/2tawgez

Can you tell me what could be wrong? Could you test the mp4 movie on your system?

[JanWillem32]

Confirmed BSOD because of driver failure. This sample is 3840×2160 and that's why it doesn't work with DXVA. (I don't know why it should crash, though.)

[Aleksoid1978]

Some mp4 files trigger a hard restart on my computer using DXVA!

1. first play, AMD graphics driver stops working if I continue working after this, but without graphic activities, then everything works ok.
2. if I start one of those files AGAIN, when MPC-HC opens then 2nd time, enlarges the window and in a second my system restarts!

I am using these versions:
x264 build 1995
MPC-HC build 1.5.2.3423
EVR Custom default, only using internal filters
AMD Radeon 5650M, Catalyst 11.3
Win 7 64

Here is one of the files which gives me this "instant restart":
http://ifile.it/2tawgez

Can you tell me what could be wrong? Could you test the mp4 movie on your system?

Get latest version from www.xvidvideo.ru
after 3488 DXVA is off for more then FullHD resolution.

[ceb]

I've asked this several times and never have gotten an answer. From what I've read if you use say ffdshow video decoder and set it to output RGB32 and have High Quality YV12 to RGB Conversion and Dithering checked, then the chroma upsampling bug won't affect you.

For sharpening, you want to generally use the post-resize pixel shader. For YV12 chroma upsampling I don't know if you should use post or pre-resize pixel shaders.
Yeah post-resize seems slightly better, to me it looks like it has less artifacts (I hope this is the correct term).
Thanks for your answer. :)
how about comparing it yourself using this test pattern (http://www.mediafire.com/?7cjlfuid35u1hbe).
I tried it but don't see any difference (perhaps because I'm using a 'recent' video card and latest drivers [11.7]), so I guess I'm fine without it. :thanks:

[Underground78]

If you want the exact version of non-crash, I dont know. However, built 3267 was fine.

Ever since modification 3286 onwards, kept getting stackhash error and I stopped to test at version 3329. Only recently, I started to test again and mpc keeps getting APPCRASH after exiting D3D mode since 3485.

You mean a build between rev 3267 and 3286 added the bug ?

[JohnLai]

Correct, except errors are different after exiting D3D mode. Stackhash (3286-3329,stopped test) and Appcrash (3485 - ?). I am using xhmikosr's builds for testing.

[Underground78]

Correct, except errors are different after exiting D3D mode. Stackhash (3286-3329,stopped test) and Appcrash (3485 - ?). I am using xhmikosr's builds for testing.

Can you try narrowing down the range of revisions where the bug was introduced using the builds from here http://www.xvidvideo.ru/media-player-classic-home-cinema-x86-x64/ ?

[Silent Rain]

The video freezes while jumping on the timeline!
Tested on LAV Video Decoder (http://files.1f0.de/lavf/LAVFilters-video3.zip) & MPC-HC 1.5.3.3497 (http://xhmikosr.1f0.de/index.php?folder=bXBjLWhj). Connected to the player all three .ax-files (http://jpegshare.net/a5/32/a53226be9609ecee3fd45ff2011dd6e0.png.html) in external filters (http://postimage.org/image/8p3z7db8/). All the internal decoders and splitters disabled in the settings (http://postimage.org/image/8pfjysro/) of MPC-HC.


Bleeding Through - Orange County Blonde And Blue (Shock Session).mp4: (http://www.mediafire.com/?imhgm8wobdzc2so)

http://jpegshare.net/thumbs/b4/72/b4721f8c91a9ea7eedad4f93bb1da5bf.jpg (http://jpegshare.net/b4/72/b4721f8c91a9ea7eedad4f93bb1da5bf.jpg.html) http://jpegshare.net/thumbs/30/e8/30e8b1e4952b2b7205c4f9c1b117dcac.jpg (http://jpegshare.net/30/e8/30e8b1e4952b2b7205c4f9c1b117dcac.jpg.html) http://jpegshare.net/thumbs/5e/72/5e720798a2285998b5b59fa169cf169f.jpg (http://jpegshare.net/5e/72/5e720798a2285998b5b59fa169cf169f.jpg.html)


Bleeding Through - Death Anxiety.mkv: (http://www.mediafire.com/?tfbjtlic22ycuma)

http://jpegshare.net/thumbs/f6/f9/f6f90f065b893d3b9856987b28a5a5d9.jpg (http://jpegshare.net/f6/f9/f6f90f065b893d3b9856987b28a5a5d9.jpg.html) http://jpegshare.net/thumbs/4e/21/4e21c07c91e5d7ab617ba15492ae94dd.jpg (http://jpegshare.net/4e/21/4e21c07c91e5d7ab617ba15492ae94dd.jpg.html) http://jpegshare.net/thumbs/1f/64/1f64725768a1b0de889ddad3f324a262.jpg (http://jpegshare.net/1f/64/1f64725768a1b0de889ddad3f324a262.jpg.html)


Especially well seen these freezing, if you turn off DXVA (http://postimage.org/image/2q5bgnosk/) and Fast seek (on keyframe) (http://postimage.org/image/2q5d471ac/).

[JohnLai]

Can you try narrowing down the range of revisions where the bug was introduced using the builds from here http://www.xvidvideo.ru/media-player-classic-home-cinema-x86-x64/ ?

Which bug? Stackhash or Appcrash?

[Underground78]

Let's start with the first one to appear so the "Stackhash".

[JohnLai]

Strange, xvidvideo's builds didn't have stackhash error, instead BEX64 error came up. Below are the list:
3268 = no problem
3337 = BEX64
3338 = BEX64
3357 = BEX64
3363 = BEX64
3391 = APPCRASH
3403 = APPCRASH
3423 = APPCRASH
3432 = APPCRASH
3436 = BEX64
3446 = APPCRASH
3462 = BEX64
3471 = BEX64
3488 = BEX64
3491 = APPCRASH
3509 = BEX64