CLI options clarification
Opened this issue · 1 comments
plondino commented
I am looking to get a bit of clarification on some of the cli options:
- Are
Full
andComplete
essentially the same option? IsComplete
deprecated since it doesn't appear in the help message? ParseSpeed
doesn't appear in the help message - I understand thatParseSpeed=1
does a full parse of the file, is it just 0 (off) and 1 (on) or are there other settings? Interestingly, settingParseSpeed=0
has a slightly different output than leaving it out altogether:
389HR.mediainfo.xml.txt
389HR.mediainfo-parsespeed-0.xml.txt
389HR.mediainfo-parsespeed-1.xml.txt
JeromeMartinez commented
Are Full and Complete essentially the same option?
Yes.
Is Complete deprecated since it doesn't appear in the help message?
I need to clarify that, currently both are synonyms and I should "kill" one at some point. Help message also need a lot of cleanup / expansion :(.
ParseSpeed doesn't appear in the help message
I am so late on the documentation, not a priority for anybody then lot of questions... So need to be done at some point.
I understand that ParseSpeed=1 does a full parse of the file, is it just 0 (off) and 1 (on) or are there other settings?
Part of the doc I need to create, a quick version:
- -1 is "fastest", new (this year), currently only for MXF, super fast parsing, only MXF headers, done for a customer who wanted to quickly scan thousands of files and accepting to rely on only the MXF headers and not the essence contents
- 0 is "faster" parsing, reducing the count of bytes read, but less information (captions detection, GOP size...)
- 0.3 exists also for some edge cases, something in between
- 0.5 is default parsing, balance between bytes read and output completeness
- 0.7 is "slower" parsing sometimes looking for more tips in the file
- 1 is "slowest" parsing, full parsing