I am creating my own CLI wrapper for ffmpeg. I am designing it so that you can
build a command line by selecting various options from dropdown lists. In order
to do this, you need some kind of document that can be parsed, but I am finding
that there is very little structure in the output generated by -h all as well
as other outputs for anything command-line-related.
For example, here are the specs for the channel_coupling switch:
-channel_coupling boolean
Enables/Disables use of channel coupling
-1
auto
Selected by Encoder (default)
0
off
Disable Channel Coupling
1
on
Enable Channel Coupling
I would like to that in a deserializable format like JSON here:
[
{
"ArgName": "channel_coupling",
"Description": "Enables/Disables use of channel coupling [etc etc]",
"DataType": "boolean",
"Values": [
"-1",
"1",
"0"
]
}
]
Otherwise, the only way to get this structured is to parse the document which
is virtually impossible given how there is no structural uniformity. Any way to
get all output text in JSON like you can with ffmpegprobe?
Sent with [ProtonMail](https://protonmail.com) Secure Email.
_______________________________________________
ffmpeg-user mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
