On Thu, Feb 27, 2020, at 12:30, Anton Khirnov wrote: > > Today, for example, when we want to visualize QP, we use libavcodec to > > decode the frame, use another piece of code to extract the QP and overlay > > both of them. This is almost (and i say ALMOST) decoding the frame twice. > > (BTW, we can do that already with libavcodec for MV, so why not for QP) > > Thank you, finally there is a clear use case.
Thanks Thierry! > > I agree that the current QP code (not feature) should be deprecated as it > > does not work with newer codec. > > But before removing the deprecated code, it will be nice to have the same > > feature available with a newer API, so the features of > > extracting/analyzing/overlaying QP still work. > > Yes, it does indeed sound reasonable to push this new API and convert > the old code to it. The question remains if any of the people arguing > for keeping those filters are also willing to do the conversion. Lynne? Juan? Can it be done with the new API patches? -- Jean-Baptiste Kempf - President +33 672 704 734 _______________________________________________ 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".
