On Sun, 24 May 2020 at 05:44, Soft Works <softwo...@hotmail.com> wrote:
> Hello, > > I've seen the commit about the option for dumping the filtergraph and that > reminded me about something that I'd be willing to contribute in case > anybody likes it. > > A while ago I was looking for a way to get information about the > filtergraphs that ffmpeg builds at runtime, the individual formats that > have been negotiated between input and output pins and which filters have a > hardware context. > > I had expected that this is what the graph2dot is intended to do, but that > wasn't the case. Turning a filter string into a graph is not what I was > looking for. > > Eventually I have implemented a feature that iterates all filters, their > connections and the negotiated media formats during runtime and writes them > out as json or xml (using the same methods that ffprobe uses). > > I have attached an example output and an image as an example for what > could be done with the output. > > Let me know whether there's some interest in this. > > Regards > Softworkz > > Direct links to the attachments: > https://gist.github.com/softworkz/4f4bf2c1365d2ce3f6ac70b1b434aa40 > https://github.com/softworkz/ffmpegfiltergraphs/issues/1 > > > This is very fascinating, thanks for working on this. Such output would allow for troubleshooting filter performance, especially in complex filter setups where hardware contexts are in use. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
