Jerome Martinez

MediaInfo is maybe open, or locked by a process, a reboot (yeah, classic answer) should resolve the issue.

C'est en effet l'inconvénient.

Si vous ne pouvez pas utiliser l'ancienne version en attendant, oui.

Dans notre (longue) liste des choses à faire en support gratuit.

Il a raison. Mais il faut qu'on gère mieux ça.

No fichiers fonctionnent bien. Il faut plus de détail sur le fichier et la commande utilisée.

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.