View Full Version : Media Player Classic Home Cinema (MPC-HC) - DXVA!
o770
28th December 2010, 07:41
I'd do everything except...
What about the compatibility check? Should everything be skipped, should checking everything also work?
Thanks a lot!
ranpha
28th December 2010, 07:45
What about the compatibility check? Should everything be skipped, should checking everything also work?
Thanks a lot!
The compatbility check doesn't really apply if you use third-party codecs.
o770
28th December 2010, 08:06
What about it if I use the filters? For intel core i3...
ranpha
28th December 2010, 08:11
What about it if I use the filters? For intel core i3...
Skip reference frame check.
nevcairiel
28th December 2010, 11:52
Question:
Is the internal software h264 filter multithreaded?
I have advised someone to install ffdshow for ffmpeg mt, but I'm wondering if this is redundant.
The internal h264 decoder does currently not use ffmpeg-mt, you need ffdshow for that.
dbone1026
28th December 2010, 14:29
What about it if I use the filters? For intel core i3...
For my core i5 I use the MS Video Decoder for h264 and Arcsoft Video Decoder for VC1. The internal MPC video decoders do not work well with core i3/i5 (for h264 you can get some serious blocking and for VC1 you lose DXVA). Using the MS Video Decoder for h264 takes care of the blocking/green banding issue and the arcsoft video decoder gives full DXVA for VC1. I just set both as prefer in the external filters section of MPC
Thunderbolt8
28th December 2010, 14:39
how can I change the default folder when I click on quick open file? dont want to start in the mpc-hc program directory each time anew.
LigH
28th December 2010, 17:19
Possibly by changing the "Start in folder" property of the link to MPC-HC? At least I hope so...
mindbomb
28th December 2010, 18:41
For my core i5 I use the MS Video Decoder for h264 and Arcsoft Video Decoder for VC1. The internal MPC video decoders do not work well with core i3/i5 (for h264 you can get some serious blocking and for VC1 you lose DXVA). Using the MS Video Decoder for h264 takes care of the blocking/green banding issue and the arcsoft video decoder gives full DXVA for VC1. I just set both as prefer in the external filters section of MPC
i have a nvidia gtx 260, which only supports idct for vc-1 much like intel hd graphics.
I tried the arcsoft video decoder, but i found that I was getting many blocky artifacts when using dxva. I was using EVR CP and mpc's internal splitter. what do you do to get it working properly?
dbone1026
28th December 2010, 18:55
i have a nvidia gtx 260, which only supports idct for vc-1 much like intel hd graphics.
I tried the arcsoft video decoder, but i found that I was getting many blocky artifacts when using dxva. I was using EVR CP and mpc's internal splitter. what do you do to get it working properly?
I cant speak about the NVIdia GPU as I don't have one, I use just Intel on my HTPC. I didn't make any changes to the default MPC Settings, just added MS Video Decoder and Arcsoft Video Decoder to the External Filters (and set to Prefer with the MS Video Decoder listed first). I followed this for using the Arcsoft Video Decoder - http://forum.doom9.org/showthread.php?t=154070
mindbomb
28th December 2010, 22:18
you find no problems with artifacts when you use arcsoft video decoder in mpc hc?
what tmt version are you using dbone?
edit:
registered the asvid.ax from tmt 5, it seems to be working actually. The last time I tried with tmt2 I think, and that resulted in tons of artifacts.
Now, this isn't scientific or anything, but I feel like libavcodec was actually producing smoother results, despite no dxva.
o770
28th December 2010, 22:24
MS decoder makes many irregular encodes I tested play too fast although blockiness was indeed gone. Haven't you experienced that?
Found this (http://forum.doom9.org/showpost.php?p=1398564) about the compatibility check. Should I really skip reference frame check?
No problem caused by 10-bit RGB Output and Full floating point processing. Force 10-bit RGB input creates artifacts.
I can't verify the first two settings actually do anything. Do the stats show? This (http://img.photobucket.com/albums/v110/anitadark/snap.png) snapshot shows the configuration I intend to maintain - is it good?
dbone1026
28th December 2010, 23:20
you find no problems with artifacts when you use arcsoft video decoder in mpc hc?
what tmt version are you using dbone?
edit:
registered the asvid.ax from tmt 5, it seems to be working actually. The last time I tried with tmt2 I think, and that resulted in tons of artifacts.
Now, this isn't scientific or anything, but I feel like libavcodec was actually producing smoother results, despite no dxva.
I used the TMT3 decoders (I own a license for TMT3 so it was easy to grab)
dbone1026
28th December 2010, 23:22
MS decoder makes many irregular encodes I tested play too fast although blockiness was indeed gone. Haven't you experienced that?
Found this (http://forum.doom9.org/showpost.php?p=1398564) about the compatibility check. Should I really skip reference frame check?
No problem caused by 10-bit RGB Output and Full floating point processing. Force 10-bit RGB input creates artifacts.
I can't verify the first two settings actually do anything. Do the stats show? This (http://img.photobucket.com/albums/v110/anitadark/snap.png) snapshot shows the configuration I intend to maintain - is it good?
No, I have had zero issues with MS Video Decoder for h264 and core i5 (tested on both my core i5 HTPC and core i5 laptop). This is for 1:1 BluRay mkvs which is a large majority of my content and using MPC HC for playback
xiulet
29th December 2010, 00:08
xhmikosr , a new update for catalan translation!
https://sourceforge.net (https://sourceforge.net/apps/phpbb/mpc-hc/viewtopic.php?f=5&t=41&p=217#p217)
:thanks: adéu.
Thunderbolt8
29th December 2010, 02:04
Possibly by changing the "Start in folder" property of the link to MPC-HC? At least I hope so...
doesnt work, unfortunately (although it did with the older version I had installed, but it doesnt work any more now with the latest)
mindbomb
29th December 2010, 02:34
I used the TMT3 decoders (I own a license for TMT3 so it was easy to grab)
I've been playing around with the vc-1 decoder from tmt3 and tmt 5, and in both, im finding that i run into problems with audio video sync upon seeking occasionally, and I'm also getting dropped frames, especially in There Will Be Blood, where i was getting about one per second through any particular scene.
Idk have you experienced anything like this, or does this only affect nvidia cards?
I love the idea of hardware acceleration, but I think im going to have to go back to libavcodec.
edit: also, when i tried to play the movie Greenberg, i just get a black screen.
dbone1026
29th December 2010, 02:42
I've been playing around with the vc-1 decoder from tmt3 and tmt 5, and in both, im finding that i run into problems with audio video sync upon seeking occasionally, and I'm also getting dropped frames, especially in There Will Be Blood, where i was getting about one per second through any particular scene.
Idk have you experienced anything like this, or does this only affect nvidia cards?
I love the idea of hardware acceleration, but I think im going to have to go back to libavcodec.
I have only tested the arcsoft video decoder (TMT3) with my core i5 and have had none of those issues you describe. For my ATI GPU HTPCs I just use the internal MPC filters. I don't have a NVidia GPU so cannot confirm what you are seeing.
alexins
29th December 2010, 04:01
Media Player Classic HomeCinema (x86/x64), 1.4.2808 (http://www.xvidvideo.ru/media-player-classic-home-cinema-x86-x64/media-player-classic-homecinema-x86-x64-1-4-2808.html)
Changes (2801-2808):
Another update for 2798 rev;
rename Belarus.isl to Belarusian.isl, update changelog;
update ffmpeg;
Fix: playback seamless BD;
Add: PGS subtitles name and language;
Patch by Sebastiii;
update MediaInfoLib to r3620;
update Compilation.txt. Patch by thevbm;
updated translations, catalan by xiulet, ukrainian by arestarh;
Revert rev. 2684, because it's broken play subtitle in single MPEG file (*.m2ts).
LigH
29th December 2010, 09:47
@ alexins, Thunderbolt8:
How about adding some kind of "Preferred directory", or even "Media library" (quick access to a few directory tree branches), to MPC-HC?
__
Oops ... there are already "Favourites". Sounds useful for you, Thunderbolt8, if they could be extended by "Folders" too, in addition to "Files" and "DVDs".
SamuriHL
29th December 2010, 14:53
Fix: playback seamless BD;
Add: PGS subtitles name and language;
Patch by Sebastiii;
Way to go Seb! I hope the seamless branching stuff is finall fixed for good. Awesome!!
dleach
29th December 2010, 15:08
What does "Fix: playback seamless BD" mean?
Media Player Classic HomeCinema (x86/x64), 1.4.2808 (http://www.xvidvideo.ru/media-player-classic-home-cinema-x86-x64/media-player-classic-homecinema-x86-x64-1-4-2808.html)
Changes (2801-2808):
Another update for 2798 rev;
rename Belarus.isl to Belarusian.isl, update changelog;
update ffmpeg;
Fix: playback seamless BD;
Add: PGS subtitles name and language;
Patch by Sebastiii;
update MediaInfoLib to r3620;
update Compilation.txt. Patch by thevbm;
updated translations, catalan by xiulet, ukrainian by arestarh;
Revert rev. 2684, because it's broken play subtitle in single MPEG file (*.m2ts).
mark0077
29th December 2010, 17:15
What does "Fix: playback seamless BD" mean?
For me it seems to fix this audio desync problem with multi m2ts blu-ray playlist files, eg Toy Story 3. Thanks a million guys!
http://sourceforge.net/apps/trac/mpc-hc/ticket/1010
tetsuo55 can this ticket be closed please? Perhaps devs could have a quick search through the bug tracker after they provide a fix, to see if any bug reports can be closed?
vBm
29th December 2010, 17:57
For me it seems to fix this audio desync problem with multi m2ts blu-ray playlist files, eg Toy Story 3. Thanks a million guys!
http://sourceforge.net/apps/trac/mpc-hc/ticket/1010
tetsuo55 can this ticket be closed please? Perhaps devs could have a quick search through the bug tracker after they provide a fix, to see if any bug reports can be closed?Thanks, closed #1010
In last few days namaiki closed several forgot-to-close fixed tickets. There are couple of 'easy' to implement tickets but we need someone to step up and do it :P
rica
30th December 2010, 02:30
Hi guys,
shall i hope MPC-HC will support 3D BD play in 2011?
Happy new year btw.
stasi
30th December 2010, 16:08
What about an option to show the cover of a MKV file in the main window for a few seconds when starting playback? And an option to darken the picture when a movie is paused for ~5 minutes?
leeperry
30th December 2010, 21:14
shall i hope MPC-HC will support 3D BD play in 2011?
What about an option to show the cover of a MKV file in the main window for a few seconds when starting playback? And an option to darken the picture when a movie is paused for ~5 minutes?
patches are welcome http://forum-images.hardware.fr/icones/smilies/sol.gif
Steveo08
30th December 2010, 21:19
i have a question to this ticket:
http://sourceforge.net/apps/trac/mpc-hc/ticket/589
is a fix possible?
god_md5
31st December 2010, 11:03
i try this ver ,the dvb subtitles can't work
Media Player Classic HomeCinema (x86), 1.4.2808, MSVC2010 (SSE2)
sample
http://www.mediafire.com/?1m52gp7imo1ua7c
Aleksoid1978
31st December 2010, 15:46
Happy new 2011 YEAR to ALL
joe42
31st December 2010, 18:29
http://forum.doom9.org/showpost.php?p=1466560&postcount=15548
I haven't gotten much feedback on the issue I've had where some MKVs from MakeMKV crash MPC-HC. Has no one seen anything like this before? Or is this sort of thing common?
I was experimenting with the Spider-Man 3 MKV from MakeMKV that was crashing MPC-HC, trying to find out why some clips I created with MKVMerge would crash MPC-HC, and other clips would not. I finally narrowed it down to some relatively short clips that do crash MPC-HC! Here are two sequential 20 second clips, the first one (313) plays fine in MPC-HC, while the second one (314) crashes MPC-HC:
http://www.mediafire.com/file/algrzw0ti8yi547/sm3_clip1_crash_part-313.mkv
http://www.mediafire.com/file/wv6qg766y7t17cy/sm3_clip1_crash_part-314.mkv
I used MKVMerge to split the problematic MKV up into 406 clips of 74MB each. I found that clips 314 - 319 all crashed MPC-HC but played fine in VLC. All the other clips that I tried played fine in MPC-HC (I did not try all 406, but I tried a number of them from different times).
It turns out that all 6 crashing clips contain the time (in the original MKV) from 1:47:20 to 1:49:10 which is, I believe, from the beginning of chapter 41 to the beginning of chapter 42. Something in that chapter creates clips that crash MPC-HC.
Any idea why that is?
clsid
31st December 2010, 20:48
The internal Matroska splitter is what crashes. Clip 314 plays fine with Haali splitter.
Polcius
1st January 2011, 02:11
Color management is completely broken.
I've done an ICC profile with an i1-Pro sensor. Obviously, this profile is applied "system-wide", since the desktop colors change from when I didn't have a profile.
I ran two measurements with the ColorHFCR soft, using a DVD with test patterns (grayscale, primaries...), playing it in MPC-HC.
First measurement, without color-management enabled (perceptual, 2.2, auto-detect) in MPC-HC. Everything flawless. Excellent grayscale tracking, dead on gamma.
Second, with color management enabled. A complete failure. Messes up the gamma, changes the grayscale...
I don't know what color management does, and yes, it alters the primaries, but messes up grayscale & gamma wich is more important.
tetsuo55
1st January 2011, 02:15
The guy who wrote that tried to explain to me how it works.
1. Your display itself (using the knobs) gets some basic configuration
2. For each colorspace you need you create a profile using the sensor
3. mpc-hc colorspace management can load the correct profile for each type of video and make sure the colors etc.. are always a correct match for the capabilities of your display.
The reason it works like this is because no 1 gamut will fit perfectly in another, this is the only way to ensure each gamut gets displayed as accurate as it can.
What i think is happening on your system. You have a global profile loaded and then load another one on top of that from mpc-hc, causing a double correction and incorrect colors etc..
You should disable all other corrections when using mpc-hc afaik.
joe42
1st January 2011, 05:04
The internal Matroska splitter is what crashes. Clip 314 plays fine with Haali splitter.
That is interesting. I had thought that it was best to use MPC-HC's internal splitter. But if the problem I am seeing (quite a few MakeMKV files I have tried crash MPC-HC) is not experienced by many people, are most people using Haali?
In general, do you think it is a better idea to use the Haali splitter with MPC-HC?
Also, does anyone know where best to point the finger here? Is MakeMKV generating MKV files that are out of spec, or is this just a bug in the Matroska splitter? I guess even if the files were out of spec, the splitter should fail gracefully, not crash.
mindbomb
1st January 2011, 06:22
The internal h264 decoder does currently not use ffmpeg-mt, you need ffdshow for that.
thanks nev.
the mpeg 4 part 2 and mpeg 2 decoders are multithreaded though, right?
sansnom05
1st January 2011, 07:00
http://forum.doom9.org/showpost.php?p=1466560&postcount=15548
I haven't gotten much feedback on the issue I've had where some MKVs from MakeMKV crash MPC-HC. Has no one seen anything like this before? Or is this sort of thing common?
I was experimenting with the Spider-Man 3 MKV from MakeMKV that was crashing MPC-HC, trying to find out why some clips I created with MKVMerge would crash MPC-HC, and other clips would not. I finally narrowed it down to some relatively short clips that do crash MPC-HC! Here are two sequential 20 second clips, the first one (313) plays fine in MPC-HC, while the second one (314) crashes MPC-HC:
http://www.mediafire.com/file/algrzw0ti8yi547/sm3_clip1_crash_part-313.mkv
http://www.mediafire.com/file/wv6qg766y7t17cy/sm3_clip1_crash_part-314.mkv
I used MKVMerge to split the problematic MKV up into 406 clips of 74MB each. I found that clips 314 - 319 all crashed MPC-HC but played fine in VLC. All the other clips that I tried played fine in MPC-HC (I did not try all 406, but I tried a number of them from different times).
It turns out that all 6 crashing clips contain the time (in the original MKV) from 1:47:20 to 1:49:10 which is, I believe, from the beginning of chapter 41 to the beginning of chapter 42. Something in that chapter creates clips that crash MPC-HC.
Any idea why that is?
Check the mediainfo of your 314 clip, the reported duration of video is different (longer) than the duration in General. 313 clip is the same for both. Maybe that's the reason for internal Matroska filter crashed? Please check your other clips too.
joe42
1st January 2011, 10:16
Check the mediainfo of your 314 clip, the reported duration of video is different (longer) than the duration in General. 313 clip is the same for both. Maybe that's the reason for internal Matroska filter crashed? Please check your other clips too.
I did not follow that. What is "the duration in General"? What two durations are you comparing? The duration in mediainfo is one, I gather. What is the other?
tetsuo55
1st January 2011, 10:55
Haali usually has better support for MKV than the internal splitter.
SamuriHL
1st January 2011, 15:13
That is interesting. I had thought that it was best to use MPC-HC's internal splitter. But if the problem I am seeing (quite a few MakeMKV files I have tried crash MPC-HC) is not experienced by many people, are most people using Haali?
In general, do you think it is a better idea to use the Haali splitter with MPC-HC?
Also, does anyone know where best to point the finger here? Is MakeMKV generating MKV files that are out of spec, or is this just a bug in the Matroska splitter? I guess even if the files were out of spec, the splitter should fail gracefully, not crash.
I'm using Haali to split my MakeMKV made MKV's. My guess would be a bug in the internal splitter which eventually will be replaced.
Polcius
1st January 2011, 17:05
The guy who wrote that tried to explain to me how it works.
1. Your display itself (using the knobs) gets some basic configuration
2. For each colorspace you need you create a profile using the sensor
3. mpc-hc colorspace management can load the correct profile for each type of video and make sure the colors etc.. are always a correct match for the capabilities of your display.
The reason it works like this is because no 1 gamut will fit perfectly in another, this is the only way to ensure each gamut gets displayed as accurate as it can.
What i think is happening on your system. You have a global profile loaded and then load another one on top of that from mpc-hc, causing a double correction and incorrect colors etc..
You should disable all other corrections when using mpc-hc afaik.
I don't understand... :confused:
EDIT: Ok, I think I know what you mean. Tonight I will try disabling the "general" Windows color correction.
clsid
1st January 2011, 17:16
thanks nev.
the mpeg 4 part 2 and mpeg 2 decoders are multithreaded though, right?
None of the internal decoders are multithreaded.
Xorp
1st January 2011, 17:23
2011 bump: http://sourceforge.net/apps/trac/mpc-hc/ticket/71
Let's see how many years we can keep it going
JanWillem32
1st January 2011, 18:41
@Polcius The general Windows color system has to be configured so that the profile is installed and marked as default system-wide, but without directly applying it. You can do that by accessing the color configuration panel in the Windows Control Panel. Change the system-wide settings under the "advanced" tab. Under the next "advanced" tab untick the the checkbox, and make sure you use the installed profile as default, with ICC display conditions. If your profile isn't present in the drop-down menu, you can install it in the "devices" tab. Make sure your user settings are merged with the system defaults, you can merge them in the "device" tab of the first screen under "profiles".
To save on resources, you can additionally disable the Windows Color System service. You can access it by running "services.msc" .
There are additional guides for this item if you search for Windows color solutions for Photoshop.
dansrfe
1st January 2011, 21:10
1 feature request:
In the playback tab under "Output" can there be an option to manually define rules for resizing. Such as "Half resolution if input resolution above a certain resolution" or "increase resolution by 1 1/3 if below a certain resolution". I'm sure this would help a lot of people.
clsid
1st January 2011, 21:29
This is an automated response from the MPC-HC feature request server:
CODE 37: Request queued at position 1109. Estimated implementation time August 15th, 2026. Thanks for your submission.
clsid
1st January 2011, 21:31
In ffdshow you can define custom settings profiles and different resizing settings.
You don't use ffdshow and prefer the inferior internal decoders?
Well that is too bad if you want the desired functionality.
Polcius
1st January 2011, 22:58
@Polcius The general Windows color system has to be configured so that the profile is installed and marked as default system-wide, but without directly applying it. You can do that by accessing the color configuration panel in the Windows Control Panel. Change the system-wide settings under the "advanced" tab. Under the next "advanced" tab untick the the checkbox, and make sure you use the installed profile as default, with ICC display conditions. If your profile isn't present in the drop-down menu, you can install it in the "devices" tab. Make sure your user settings are merged with the system defaults, you can merge them in the "device" tab of the first screen under "profiles".
To save on resources, you can additionally disable the Windows Color System service. You can access it by running "services.msc" .
There are additional guides for this item if you search for Windows color solutions for Photoshop.
Can you make a screencap of how it should look, please?
Thanks, I will look for info.
dansrfe
1st January 2011, 23:45
I'm not talking about true resizing. I'm talking about telling the renderer to downscale on initial launch of the file. Kind of like what Haali did, except with a custom rule setup for under what restrictions to resize how much.
JanWillem32
2nd January 2011, 00:15
@Polcius The setup I described is valid for Vista and 7 only. For windows XP the color control is quite a bit different:
http://articles.techrepublic.com.com/5100-22_11-5965505.html
For screenshots, that will be a problem, unless you can read Dutch.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.