Jerome Martinez

But, this does not explain why MediaInfo displays a name for value then uses a different name to extract that value! It does. Again, if you want to have the "right" names, use " --Language=raw" on the command line instead of the translation to English for humans. You are not the center of the world with English, and it is not because that we default to English for humans that the interface for computer is in English for humans. If I want a displayed parameter named 'something' and the extraction...

I don't know why MediaInfo would display a parameter and use different spelling For your information, in some configurations of MediaInfo, the program is absolutely not aware about "Color primaries", as it does not have the Machine to plain English dictionary. In the case we implement the template system with accepting one of the languages on Earth, this template may not work everywhere, only when the program has the Machine to the used language dictionary.

I don't know why MediaInfo would display a parameter and use different spelling We already explained it in the first comment. It is not about spelling. You imagine that everyone uses MediaInfo in English, this is not the case. What is displayed if for humans, translated in their language. The template does not support human language, and especially not any language on Earth, we could implement that if there is a sponsor for that, in the meantime we use letters accepted everywhere by machines (in...

but it doesn't explain why the Medainfo parameter which others state has to be the same including capitalisation and spelling turn out to be different! It does, please read again the other comment. It is not unreasonable to expect the listed parameter to be the one to use, not some unknown alternative spelling. We don't support template field in e.g. French or Chinese, English is no exception, that's all. None of which return the parameter value. So what should the parameter actually be? Read again...

Let's assume "Video;%Color primaries%". You use the "translated" (here, in plain English, but it could be another language) words, used for display to users, not computers. You can see the field names to use in the templates with e.g. the XML or JSON output in the GUI, or with --Language=rawoption with the CLI. Also available at https://mediaarea.net/en/MediaInfo/Support/Fields In your case, "Video;%colour_primaries%".

this is a 0 filled file, what do you expect from it? If there is something to recover: - need the whole file for checking if there is ore than 0 filled bytes. - recovering is not the purpose of MediaInfo, it will be custom (not free) dev.

Wrong architecture (i386) of MediaInfo installed via winget upgrade

Running the command with explicit architecture works: The issue is in WinGet and forcing the architecture (once) it the fix.