[PATCH 1/4] Remove all uses of AVFrame QP tables and related fields [PATCH 2/4] avutil/frame: Rename QP related fields so unintentional
These 2 are common in both options, they break API but not ABI so should not be applied before the next release [PATCH 3/4] avutil: frame Update the existing QP API This is a rough sketch of how the existing API can cope with a much wider range of codecs. I did not check if this is enough to handle every codec that has QP values but a variant if this should be able to work with all. [PATCH 4/4] libavutil: AVEncodeInfo data structures This is the alternative to 3/4, which is Juan De Leóns patch which was previously posted and discussed. IIUC there where no objections to this previously but it was not applied by anyone. So Maybe we can just use this. The disadvantage here that i can see is primarely that every codec has to convert its internal format to the one specified in the API. In effect this would need a switch to only export such data when needed. Because otherwise it would waste time. _______________________________________________ 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".
