MPC / Media Player Classics - not shown any more
-
@Anselm Is the issue solved?
-
@OLLI_S yes, see my comment before your comment
-
@Tom The version number is not correct:
Version shown by vulndetect: 1.8.3
Version in the GUI: 1.8.3.8 (fc4fb469a)File name and path: C:\Program Files\K-Lite Codec Pack\MPC-HC\mpc-hc.exe Product Name: MPC-HC Internal Name: mpc-hc Original Filename: mpc-hc.exe File Description: MPC-HC Company: MPC-HC Team Legal Copyright: Copyright 2002-2018 all contributors, see Authors.txt Legal Trademarks: Comments: Based on the original Media Player Classic v6.4.9.0 © Gabest File Version String: 1.8.3.8 (fc4fb469a) File Version: 1.8.3.8 Product Version String: 1.8.3.8 (fc4fb469a) Product Version: 1.8.3.8
-
If the version number is not correct, I keep this topic opened.
-
@Anselm According to GitHub there is only one release tagged with 1.8.3:
https://github.com/clsid2/mpc-hc/tree/1.8.3I reckon that the issue here is that the author doesn't provide the binary builds, thus someone else has compiled the project and they may have arbitrary build information that we have to ignore and correlate it back to the original code / release at GitHub.
The discrepancies between announcements on websites and what is displayed in the UI is quite common, even Mozilla sometimes refer to e.g. 64.0 as 64. Mostly we have to rely on what is published on websites.
-
@Tom Seems to be diffucult, i think they also generate a hash code / checksum (the one in brackets). So e.g. changing compiler options will change this. Even if a date is included, it may change. Or configuration options?
I found different information:
https://codecguide.com/media_player_classic.htm (Version 1.8.3 (latest version) (October 5th 2018))
https://codecguide.com/features_standard.htm (Media Player Classic Homecinema [version 1.8.3.8])
https://codecguide.com/features_full.htm ((Media Player Classic Homecinema [version 1.8.3.8]))
https://codecguide.com/features_mega.htm ((Media Player Classic Homecinema [version 1.8.3.8]))https://codecguide.com/changelogs_standard.htm
Changelog 14.5.5 to 14.6.0 ~ 2018-12-14Updated MPC-HC to version 1.8.3.8 MPC-HC is now able to download online streams using: Menu > File > Save a Copy
Changelog 14.5.2 to 14.5.5 ~ 2018-11-06
Updated MPC-HC to version 1.8.3.1
Swapped two keyboard shortcuts in MPC-HC. Framestep is now Ctrl+RightArrow, and MediumJump is RightArrow.
OK, i think i have it now, there is a developer branch:
https://github.com/clsid2/mpc-hc/commits/develop -
@Anselm Yes, the hash refers to a commit (the latest they included?):
https://github.com/clsid2/mpc-hc/commit/fc4fb469a3c8fb96384270839e4221021c14cb8bSo you do indeed run something newer than 1.8.3. But since that isn't official, then we won't track it officially.
I will evaluate as we see more different versions, but I reckon that we will move all those bleeding edge builds into a separate channel with the flags "Untracked" and "Pre-release" and then we will keep proper track of the two main projects i.e. the original and the main releases from clsid2.
-
@Tom I am running the official k-lite codec pack. So you should be aware you will get those versions also from other installations.
-
@Anselm Yes, and they seem to build their own binaries.
Perhaps we should detection for K-Lite?
I can see that I can pull the version info from the Registry. Would "CodecTweakTool.exe" be a candidate for detection?
-
@Tom If you can pull the version information of k-lite from the repository, this is the best solution. (actual version 14.6.0)
I checked the CodecTweakTool.exe in the past, but it is not always updated:
CodecTweakTool.exe (last change 2018/11/06)
mpc-hc.exe (last change 2018/11/29)File name and path: C:\Program Files\K-Lite Codec Pack\Tools\CodecTweakTool.exe Product Name: Internal Name: Original Filename: File Description: Setup/Uninstall Company: Legal Copyright: Legal Trademarks: Comments: File Version String: 51.1052.0.0 File Version: 51.1052.0.0 Product Version String: Product Version: 0.0.0.0
-
@Anselm Yes, that is why I think this is an interesting case. We have some apps that we need to handle in other ways than pulling info from the files. So this is a bit of an experiment.
I will discuss this with my colleague tomorrow.