MPC-HC v1.7.13 is released and farewell(mpc-hc.org) |
MPC-HC v1.7.13 is released and farewell(mpc-hc.org) |
Even on the Linux side I have seen a drop in the number of full blown media players being developed, they are mostly front ends to things like mpv and mplayer.
I agree with you that there isn't much (if any) advantage to doing it all again with a new media player core. I would rather all the expertise is put into mpv to be honest and then let others build front ends that do all the extra bits.
I haven't tried the Roku/Fire etc though, so they may be good too.
It uses libmpv though.
mpv supports display calibration and HDR conversion as well. You can load a 3DLUT for display calibration if you want, but for mpv, you would more likely load an ICC profile and have it generate the correct LUT automatically. You can even just let it pick up the ICC profile configured in the operating system. As for HDR, there are a number of built-in tone mapping algorithms: https://mpv.io/manual/master/#options-hdr-tone-mapping
The default keybinds are absolutely nonsensical, though.
Now, the general consensus is that they should be changed gradually, rather than all at once. Some obviously bad keybindings have been removed this way (eg. Esc->quit.) If you create an issue for your most hated keybind, it can probably be changed.
Fortunately there's a file included that will restore the original behaviors.
Here's a rough version of my script: https://github.com/smnx/mpv-autosub (forked from https://gist.github.com/selsta/ce3fb37e775dbd15c698).
I suppose I'll try out MPV.
Fortunately, I believe MPC-HC will still likely be updated if necessary, or forked and updated if need be. I know I haven't updated mine in years and haven't had any problems.
I wonder if this is still a problem (I haven't used VLC in a while.) That message box is shown when fontconfig rebuilds its font cache, but libass has been able to run without fontconfig since 0.13.0 (October 2015.) I guess it depends on whether the current release version of VLC still needs it.
I haven't used MPV enough to see if this case is still true.
On Linux/macOS I use mpv - I recommend it!
Edit: Turns out this isn't unique to MPC-HC: https://www.svp-team.com/
It reimplements mpc-hc UX using qt for the UI and libmpv for the heavy lifting. The issue with this one is that it doesn't have public builds yet, but it has been in active development for years.
Maybe you want someone to update the ffmpeg it links to. Occasionally. But that's already well into "super power user" territory.
MPC-HC is just a DirectShow frontend, or at least, that's how I used it. Filters do most of the work. And no one seems to care about DirectShow anymore but that's mostly because everything works fine.
It will die eventually, because Microsoft is trying hard to kill DirectShow (to replace it with something inferior...) and the opensource guys mostly go to mplayer, but for now, updates are not really necessary.
Media Foundation ain’t that bad. I coded some moderately advanced stuff with it, custom stream sources, custom transforms — it was fun, and it run well.
I can see how it was inferior back in 2007. The first version of MF was shipped with Vista, and Vista… Let’s just say many people were disappointed with it. Nowadays however, when you only need to support Windows 7+, MF is fine.
I even use mpv on windows...
$ brew install mpv
$ mpv ~/Media/my-movie.mp4
MPV is indeed a good alternative, though.
I am currently on Windows and use MPV, I don't see why it should be exclusive in any way.
The dotfiles are compatible, and same goes for lua scripts. So there's no trade off at all that I've found. And it's nice to be able to just clone my dotfiles and have it work in OS X, and same for Windows.
It's super feature rich, with (in my opinion) a much nice interface than e.g. VLC.
Article 5 (Collection and Use of Data and Other Information)
(1) Daum may collect and use data from the computer of Users as a part of its product support services that are provided to Users in connection with the Software. Data that may be collected solely include the type of computer and type of operating system used on the computer, memory capacity, type of graphic card, Directx version, media player version, type of webcam and TV reception card.
(2) Daum will use the above collected data only for the purpose of improving the Software or providing service or technology that is suitable to the user environment of the User and will not use such data for any other purposes.
EDIT: Yeah, I was just pointing out the fact that, if you're using MPC-HC, then you're probably using Windows. In which case, whilst MPV is a good alternative, you wouldn't be installing it with (Home)brew, which is a package manager for macOS.
Also, enable "Run mpv in its own window" under Preferences -> Advanced. This removes all the issues caused by the default mode of embedding the mpv window (such as subtitles being on the video and not in the black bars).
Thank you for your work on mpv!
Any gradual changes just mean gradual changes to a keybind file. Anyone who doesn't like them can simply use their own keybind file from previous versions, or from their own modification.
Though rather than being baked in, these bindings have to be manually copied over the user's input.conf. mpv's config profiles don't extend to input.conf at the moment.
I disagree on a couple of points though. Jinc may in fact produce noticeable ringing (while NGU doesn't), and neither produce aliasing so asserting the opposite seems strange. The difference in sharpness is also quite obvious. On top of that mpv's anti-ringing filter is very basic in comparison.
HDR processing also seems quite limited and requires a lot of hand-tuning compared to madVR.
If it works for you, great, but it would be disingenuous to say that both programs are at a feature parity.
Context for others: NGU is a proprietary algorithm created by the author of madVR.
I'll admit I haven't watched any HDR content in mpv yet, but it supports all the standard tone-mapping algorithms (hable, reinhard, etc.) and apparently the default algorithm (mobius) was chosen for its colour accuracy.
I'm not saying madVR doesn't have its strengths. Error-diffusion dithering is strictly more accurate than what mpv does, and for people who like super-resolution upscalers, madVR tends to have a larger selection and faster implementations. Still, it would be disingenuous to say that madVR has a larger feature-set than mpv. They have different feature-sets. mpv's convolution-based upscalers are much more tunable and its colour management is more advanced, since it can use an ICC profile to auto-generate a LUT for any input gamut, rather than relying on an external CMS for this.
It says right there in the source you provided that MPC-BE "not only looks better than MPC, but also performs faster"
Not only does it look better, it plays files better then HC by default. Not sure HC has improved since then, back in the day BE would handle AVI, rmvb, WMV, much better without the need of fiddling around with settings and filters.
MPC-BE is the only thing I really miss on Mac.
> MPC-BE is the only thing I really miss on Mac.
And HC definitely improved after BE was forked. While BE chose to keep maintaining their own decoding filters the HC team chose to completely switch to an internal build of LAV Filters. MPC-HC also had a lot of performance improvements to the internal subtitle renderer.
MPC-BE regularly backported these improvements though, so the fact that MPC-HC died also affects MPC-BE.