On Wed, Dec 05, 2018 at 09:31:48AM +0100, Steinar H. Gunderson wrote: >> We don't have a solution for that, and its really something the user >> application currently has to solve. > The user application doesn't feel like the right place for this. How would it > be in a better position than FFmpeg to know? And if it really is in the > position to set a policy here, it can read out the information of the codec > parameter struct and override it, no matter what libavcodec decided to do.
What's the status of this patch? Is it rejected on the basis of “this is the wrong thing to do” and nedes a larger rework of the rest of FFmpeg, or could it be merged with some changes? /* Steinar */ -- Homepage: https://www.sesse.net/ _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
