MPC-HC (users discussions/info) (to support go to github)

[Klaus1189]

Yeah, I can see the commits, but what is exactly different? You said I should see the changelog. Where is it?
As I already said, it was good before for me, so what is exactly better now? I don't get your hype. I want be be hyped, too.

[Sunspark]

Does it make a difference when you use different renderers? mpcvr+lav configured for d3d11, madvr+lav configured for d3d9, etc?

[clsid]

He is "testing" an old obsolete and unmaintained renderer that hasn't been modified in YEARS...

What you can be hyped about is that MPC-HC has been rock solid and stable for YEARS...

Anyone that doesn't get good sync has a broken Windows install.

[Klaus1189]

Thanks for confirming.

[CruNcher]

Originally Posted by clsid

He is "testing" an old obsolete and unmaintained renderer that hasn't been modified in YEARS...

What you can be hyped about is that MPC-HC has been rock solid and stable for YEARS...

Anyone that doesn't get good sync has a broken Windows install.

obsolete maybe stable surely

solid for years you would attest that for every system configuration im not sure if i would do that

what about the crashing when the energy saving comes into play and the device doesn't respond fast enough and the respond timer neither while a change on the playlist happens and MPC-HC goes by by completely

calling something rock solid on Windows alone i think many did that also before the chinese took their systems apart.

Who not has a broken Windows Install ?

I was just trying MPC-BE and MPC Video Renderer together and i was like ehhhhh what all the judder test fail at some cyclepoint maybe the longest stability was 4 cycles before it broke ?

i hope MPC-HC and MPCVR will do better

I think Elon also said that before he put the driver into Betatester mode but nicer than the Alphatester mode before.

Anyway MPC-HC does good work in finding something in that "Obsolete configuration"

The Spikes are coming from the Keyframes that's clear now but those are even just the sane ones

ATEME Titan KFE 3.5.1 <- it was going wild pretty fast replaced by
ATEME Titan KFE 3.6.1

i wonder if those transmission was even supposed to be 60 fps int and not 59.940 i mean broadcast in 60 that's weird

First transmission part was ok 2nd got high wire and they really did the broadcast in 60 fps int

There was this Broadcast in 60 FPS int and LG made several demo versions out of it in 59.940 for different Device Demos

_________________________________________________________________________________________________________

Process with highest pagefault count: firefox.exe

Total number of hard pagefaults 204
Hard pagefault count of hardest hit process: 102
Number of processes hit: 12

[CruNcher]

I think the problems in MPCVR are a overall performance issues you can get 23.976 stable but higher framerates it becomes more and more problematic

but your options are mostly judder/skips or broken sync

at 30 and 60 fps and the difference it becomes very obvious

Disable the statistics and it already improves a lot also a clear sign and we now improve the stability

Hispasat test 23.976

Potplayer + Potplayer (Framework) + MPC Video Decoder = 1 Frames skipped (No Statistics active)
MPC-BE + MPC (Framework) + MPC Video Decoder = 17 Frames skipped (No Statistics active)
MPC-HC + LAV (Framework) + MPC Video Decoder = 120 Frames skipped (No Statistics active)
MPC-HC + LAV (Framework) + EVR FullSync = 111 Frames skipped (OSD Level 2 Statistics (minimal counter) with Realtime Graph was active all the time)


Framework Components (Parser/Audio + Video Decoder) Calculate different impacts differently mostly scene changes not really impacting the viewing result lot of the differences in the Framework go back to IDR handling.

[CruNcher]

Yeah especially that the old parts in MPC-BE outside of MPC Video Decoder fail completely by now in terms of stability, you could as well remove the old bloat completely