I'm not sure how much information could be extracted from the binary, will need to do some more research. Maybe we could read the strings in the static part of the binary and extract some information.
`ffmpeg -i` prints out the configuration FFmpeg was built with, this mostly will let us know which encoder/decoders/container formats you can use. Will add a feature to parse and interpret that output.
I added an ffmpeg command string parser that converts the command stirng into graph nodes, but I temporarily disabled it to fix an infinite loop bug in my parsing code.
As someone with a project at work that involves setting up an ffmpeg project in the future, I'm now expecting to talk to my boss about expensing this and I think it's at the perfect price point where it won't take too much effort to get them to budge.
Question:
Why are you offering lifetime access for $39? Makes no sense. Anyone company that needs this can afford $100/month. Any individual who needs it can afford $30 for 3 months access.
Ideas:
It would be good if I could upload my ffmpeg binary and the IDE queries it to work out what libraries and options are compiled in.
Or maybe you could provide a command that I could enter that dumps this information, which I then put into your IDE.
It would be great if I could put my existing ffmpeg command lines into this and have them represented as a graph.