MPC-HC is dead

"v1.7.13, the latest, and probably the last release of our project…

For quite a few months now, or even years, the number of active developers has been decreasing and has inevitably reached zero. This, unfortunately, means that the project is officially dead and this release would be the last one.

…Unless some people step up that is."...

Source:
https://mpc-hc.org/2017/07/16/1.7.13-released-and-farewell/

K-Lite contains a custom build of MPC-HC that contains additional fixes and improvements compared to the officials builds. This will continue in the future. The internal codecs that MPC-HC uses are also still actively maintained.

K-Lite could use a custom build of MPC-HC but what will you do in future since there will be no new feature added in the app? Do you mean you will take over the project?

It doesn't need any big new features. It already has all important functionality. It hasn't had major changes in the past few years either. The important parts (such as the internal codecs) are external components, which are still actively maintained.

And there will be fixes whenever necessary.

If you look at the changelog of other popular players, like VLC, you will notice that almost all changes are related to its internal codecs. Almost no changes at all to the player itself (GUI, options, etc). That is because VLC is a mature player just like MPC-HC is. Sure, more features can always be added, but most users don't need anything extra, and it only makes it more bloated.

The beauty of MPC-HC that it is very modular. The internal codecs (LAV Filters) are an external project that is still actively maintained. MediaInfo is an external component. MadVR is an external component. All still very much alive and kicking.

So mature players like MPC-HC, VLC, etc. will keep running on majority of PC devices as long as no revolutionary technologies need to be implemented which requires app architecture change.

MPC has been around for 20 years now. That isn't suddenly going to change. It has been 'abandoned' a few times before.

Yes, MPC-HC has been evolved a lot from original MPC. Hope it will survive with those external add-ons as long as it can satisfy users there.

How much different are the custom builds from the official ones?
When can we expect the v1.7.13 build implemented?

I'm really glad we will still get support for MPC-HC. That program alone is the reason I'm still on Windows. Moments like this make's you appreciate projects like MPC-HC and K-Lite Codec Pack.

Cheers!

The differences in the custom build are small, but nonetheless useful.

Latest version of K-Lite contains MPC-HC 1.7.11.41. Literally the only change after that has been the version number bump to 1.7.13. So if you use latest K-Lite you are already fully up-to-date.

And why K-Lite devs dont send the changes to the upstream (to MPC-HC devs)?

They already do.

great. just as i finally managed to play HEVC x265..
i have not yet learned the difference btwn pre and post resized pixels and between sharpen, sharpen complex 1&2 and edge sharpen..etc

IT IS NOT DEAD !!!
https://github.com/mpc-hc/mpc-hc/commits/develop

Pre-resize is applied before the video is resized, post-resize is applied after resizing.

thanks, so do you suggest to check both pre and post resized or merely pre?. is shrp cmplx 1&2 based upon preferences or do you suggest to use one of those particular? is there a difference in the algorithm between edge and sharpen complex?

They are different algorithms. Use the one that looks the best to your eyes. If you want more details about how they works, you can find with Google.

You should choose between either PRE or POST for each shader that you add. In case of sharpening use whatever looks best. It is a subjective choice.

Although the title of the thread, this convo cheered me up a little.