ErrorDetectionType on Sheet View

Joe Bijoba — Mon, 02 Mar 2026 21:32:31 -0000

Hello
Is it possible to add a "ErrorDetectionType" colum. I don't find this data in the list of colums

CLI template help please.

James301 — Sun, 08 Feb 2026 02:44:25 -0000

Hello, I have created a PS1 file that will compare audio/video files using the CLI version of Media Info. It will also compare directory trees which contain Audio/video files providing metadata about the files in the tree listings. The tree listings use a configurable templet.txt file. I would like to add Images as an option to the program. When I set the ps1 file to output full metadata and select image files it produces the full data about the image. But I need to create a template file to use the directory tree portion of the ps1. I have tried to add image to the template but it locks up and will not process.
This is what I am using as a template can someone tell me what I am doing wrong? Again I’m using the CLI version and it’s a text file template not a CVS file.

General;Format:%Format%$if(%OverallBitRate%, at (%OverallBitRate/String%)) Length: %FileSize/String% [ (%Duration/String1%)] \r\n
Video;Video#%StreamKindID%:%Format%$if(%BitRate%, at %BitRate/String%) Aspect: %Width%x%Height% (%AspectRatio%)$if(%FrameRate%, at %FrameRate% fps) \r\n
Audio;Audio#%StreamKindID%:%Format%$if(%BitRate%, at %BitRate/String%),$if(%SamplingRate%, %SamplingRate/String%),$if(%BitDepth%, %BitDepth/String%), %Channel(s)/String% %ChannelPositions/String2% \r\n
Text;
Chapters;
Image; Type: %Type% Format: %Format% Dimensions: %Width/String%x%Height

Thanks for any help.

Why not showing Video-/Audio-Stream-Sizes info ?

EkriirkE — Sat, 31 Jan 2026 17:25:14 -0000

I am going to bump this since it was the first google result and remains unanswered. I found it elsewhere. Add --ParseSpeed=1 to the command, it is much slower but will give you the sizes every time.

mediainfo --ParseSpeed=1 filename

Names of output parameters for color spaces

Jerome Martinez — Sun, 18 Jan 2026 16:57:51 -0000

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 name is 'nothis' how am I supposed to know what parameter to use for extracting the data I want?

Use the output for machine, i.e. " --Language=raw" option.

Stating that using --raw parameters gives you the solution when it clearly does not, as there is nothing to directly link it to the viewed parameter.

???
It does, you have the exact field names to use in the template with this output, + https://mediaarea.net/en/MediaInfo/Support/Fields .

Currently I am relying on guesswork and trial.

Well, you have several solutions, you don't want to use them, your choice.

Names of output parameters for color spaces

Annie Body — Sun, 18 Jan 2026 16:48:12 -0000

But, this does not explain why MediaInfo displays a name for value then uses a different name to extract that value!
There is no apparent reference I could find that lists the Mediainfo names displayed and the corresponding one to use when extracting that information!
If I want a displayed parameter named 'something' and the extraction name is 'nothis' how am I supposed to know what parameter to use for extracting the data I want?
Stating that using --raw parameters gives you the solution when it clearly does not, as there is nothing to directly link it to the viewed parameter. Currently I am relying on guesswork and trial.

Names of output parameters for color spaces

Jerome Martinez — Thu, 15 Jan 2026 10:01:30 -0000

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.

Names of output parameters for color spaces

Jerome Martinez — Thu, 15 Jan 2026 09:53:52 -0000

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 practice, space is rarely accepted by machines).

Names of output parameters for color spaces

Annie Body — Thu, 15 Jan 2026 09:45:20 -0000

I listed all the parameters from MediaInfo 'Known Parameters' and the CLI output in cmd.
They are both the same as are the CLI --Language Raw parameters. I have attached a spreadsheet listing them all, should this be of any help to others that come across the same problem.

It appears that the list of parameters to use are spelled differently to those displayed in the MediaInfo views which confused me. I don't know why MediaInfo would display a parameter and use different spelling when using that same parameter to provide results, but that is the crux of it.
Many thanks to Jerome for his assistance and patience and helping me get a solution.

Names of output parameters for color spaces

Jerome Martinez — Wed, 14 Jan 2026 19:23:23 -0000

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 the first comment.

Where is the one definitive and correct list to be found?

Read again the first comment.

TL;DR: --Language=rawoption with the CLI and https://mediaarea.net/en/MediaInfo/Support/Fields

Names of output parameters for color spaces

Annie Body — Wed, 14 Jan 2026 17:29:33 -0000

OK , thanks that works for the above, 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! How are we expected to know which option to use and which one is right?
It is not unreasonable to expect the listed parameter to be the one to use, not some unknown alternative spelling.
Now for the next similar issue "Video;%bit_depth%" reports nothing. I have tried:
"Video;%Bit_depth%"
as shown in MediaInfo (with the added underscore)
"Video;%bit_depth%" as a suggested alternative
or
"Video;%bitdepth%" as shown on the link.
None of which return the parameter value. So what should the parameter actually be?
Again which one should we trust? The one within MediaInfo or that displayed elsewhere?
How are users supposed to know what to use when there is contradictory information available?
Where is the one definitive and correct list to be found?

Recent posts to Help

ErrorDetectionType on Sheet View

CLI template help please.

Why not showing Video-/Audio-Stream-Sizes info ?

Names of output parameters for color spaces

Names of output parameters for color spaces

Names of output parameters for color spaces

Names of output parameters for color spaces

Names of output parameters for color spaces

Names of output parameters for color spaces

Names of output parameters for color spaces