I am sorry, I am lacking the time and energy to reply to this discussion
constructively.
Therefore I will just write the few general remarks and just let
somebody else take over the specific discussion.
One: features and user interface are two separate things. If you have
added a new feature to the fftools, then we might want it, triggered by
normal options, whether or not we want the JSON-based interface too or
not.
Second: your JSON code only encodes the top-level arguments and options:
codec parameters, filter graphs, but these are still strings and still
require escaping. In fact, you are even making it slightly worse, since
individual arguments do not require escaping (except if using a shell)
whereas your version will always require top-level JSON escaping.
If you want to make your feature really useful, use the structure of
JSON objects. I.e., instead of:
"lavfi" : "drawtext=x=100:y=100:t='Eh: you?',scale=800:600"
make it possible to write something like that:
"lavfi" : [
{
"filter" : "drawtext",
"x" : 100,
"y" : 100,
"t" : "Eh: you?"
},
{
"filter" : "scale",
"w" : 800,
"h" : 600,
}
]
But it is not easy, because a lot of sub-options that need parsing and
escaping are just declared as strings in the code.
Regards,
--
Nicolas George
_______________________________________________
ffmpeg-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
