Quoting Michael Niedermayer (2020-02-17 23:38:31) > On Mon, Feb 17, 2020 at 06:28:23PM +0000, Fu, Linjie wrote: > > > > > > https://patchwork.ffmpeg.org/patch/14122/ > > iam hesitating because it feeds encoders with changing resolution resulting > in potentially undefined behavior ... > > > > > > > https://patchwork.ffmpeg.org/patch/14139/ > > long discussion here its not immedeatly clear if anyone was against it > > Also there is the question about the API, is there anything in the API > documentation that restricts the user app from changing the encoder > input frame dimensions? > This should be documented somewhere if its not ... > > If a flag is added that affects this, it would have to > be documented so someone writing a user app using the encoders > would know if they are allowed to change the resolution. > With just the flag and its documentation a developer could miss > the flag entirely
Is there even a sufficiently strong use case for this? Why not just create a new encoder instance? -- Anton Khirnov _______________________________________________ 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".