Anton Khirnov (12024-09-23): > I fail to see …
> how that is a problem, since you need an allocated AVFrame > to use the buffersink API anyway. Not at the same point in code. > Not to mention that even if one allocates a dedicated AVFrame for the > parameters, the cost is trivial compared to actual filtering since it's > typically only done once per filtergraph. CPU time is not the only issue. > On the other hand, the cost of a bloated symbol table is paid by > everyone whether they use the functions or not. Benchmark? -- “I dont see why” isn't an argument. Proposing better is. _______________________________________________ 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".
