Add options to display only certain tracks/labels

[Baerbeisser]

While this tool supports many formats for output, it would be more convenient for use in shell scripts/quick usage, if it had options to

• display only certain video/audio tracks
• display only certain labels (like Width, Length, Format, ...)

I always have to use it with grep, and i think that's a ugly/unreliable workaround due to localization of labels. Sure, i could use it with --Output=JSON and then parse that with jq. But from a efficiency and usability standpoint, that's a bit stupid, if you need merely two labels.

lsblk does it right IMO, with -o PATH,VENDOR,... and -H to display all labels.

Or alternatively, options for direct access to often used labels, like --width, --height.

As it is, the tool is more suitable as some sort of library in a heavy duty scripts, where you read lots of documentation for.

[JeromeMartinez]

display only certain video/audio tracks

Currently no possible, we need to implement that.

display only certain tags (like Width,Length,Format,...)

mediainfo --Output=file://template.csv with template.csv like in https://github.com/MediaArea/MediaInfo/tree/master/Source/Resource/Plugin/Custom
(when only one part of the output is needed, can be also directly on command line mediainfo "--Output=General;%Duration%")

But from a efficiency and usability standpoint, that's a bit stupid, if you need merely two labels.

The stable interface is XML or JSON, and it is not stupid, efficiency is good (parsing such output is fast), anyway there is the template system, just that we don't have the filter per track yet.

[Baerbeisser]

My focus here is more on usability, not many people use cli structured data parsers that often to know their usage by heart.

And the other proposal width quick access options (--width, --height)?

[JeromeMartinez]

And the other proposal width quick access options (--width, --height)?

mediainfo "--Output=Video;%Width%x%Height%"
field names are the ones in XML/JSON or --Language=raw --full
Generally speaking, you have examples in https://github.com/MediaArea/MediaInfo/tree/master/Source/Resource/Plugin/Custom

[Baerbeisser]

So you have to read documentation/output data yet again, only to get some quick info?

[JeromeMartinez]

So you have to read documentation/output data yet again, only to get some quick info?

You asked for something like outputting width only, I provided something for outputting width only, what is missing here?

[Baerbeisser]

What i'm trying to say is, mediainfo as it currently is, is fine if you use it in some big multiple hundreds-lines script, because there you read documentation for.

But for common use in a one- or two-liner, you type -h/--help, see that the only way to parse it is via some complicated structured data parser (and common cli user doesn't have vast knowledge about those tools), then proceeds to parse via grep or googles, if there is another tool with simpler output.

Current example: i want to compare width/length of multiple video-splits. A quick find -exec would have been fine, if mediainfo had a way to filter labels. But as it is, i would have to create something more elaborate for it, spend a hour or so to figure out mediainfo and parser tool syntax. Or parse via grep, that is.

[JeromeMartinez]

is fine if you use it in some big multiple hundreds-lines script,

Plenty of people handle MediaInfo report without hundreds-lines script. Mainly with a JSON or XML parsing, like with tons of other tools, or the template system we provide.

but as it is, i would have to create something more elaborate for it, spend a hour or so to figure out mediainfo and parser tool syntax.

We are open to patches about the help or the documentation or a better (but also easy to maintain at long term because we don't want to have a burden there) interface from you, someone else motivated for doing that (sponsored by you or not), or your sponsorship for prioritizing this issue.

This is not a constructive discussion, I stop there.

[Baerbeisser]

I mean, why do you provide output to cli at all, but to filter it, you have to use another output format and parse it? That's a usability issue.