On 2/26/20, Jean-Baptiste Kempf <j...@videolan.org> wrote: > Yo, > > On Wed, Feb 26, 2020, at 14:27, Thilo Borgmann wrote: >> > The patch in your link is not using this API. Precisely because this API >> > is inadequate for anything newer than MPEG4 ASP. If anything, it's an >> > additional argument in favor of my patches. >> >> My actual point about that patch was that there is a use case to >> extract QP tables for more current codecs. Suggests this use case is >> also there for less current ones which says we should not just remove >> this possibility. > > I think this is the right question: > "Are there actual valid use cases to do it?" > > I remember that last year, there was an extractqp for h264 patches from > Google, for example. > > Any other question is basically less important. > > If that is useful, then, we should update the API and remove the old API. > If it is not, then, let's remove everything. >
It is useful as already proved. Please refrain from ignoring obvious facts. > Best, > > -- > 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". _______________________________________________ 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".
