On 27/02/2019 10:22, Gyan wrote: > Looks like, at present, the only way to effect ROI is via side data, and > no filter or other in-tree mechanism at present can convey or generate it.
Life exists outside of ffmpeg.c, and it's an extremely useful API to have. > Are there any near-term plans to add some? If not, may I suggest that > you add a private option for supporting encoders, for users to input ROIs? Please don't suggest removing an API that was *just added*, after many months of bikeshedding. Please. - Derek _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
