Hi, extending AVVideoEncParams was the first hypothesis I made but it didn't seem it was the proper place to add the mb_info flags. I may be wrong but my impression is that AVVideoEncParams is used to carry encoding parameters read from the bitstream at the decoder side while here were going the other direction, i.e., were passing information from the application to the encoder. Secondly, mb_info can't be strictly considered encoding parameters and it's not present in the bitstream at all. It's just a way to give hints to the libx264 encoder on which macroblock we know have not changed since the previous frame and could be coded as P_SKIPs. Libx264 however, may or may not oblige according to its logic, and this specific information is not transmitted in the bitstream nor can be recovered at the decoder. Elias ________________________________________ From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> on behalf of Anton Khirnov <anton@khirnov.net> Sent: Saturday, June 18, 2022 5:06 PM To: ffmpeg-devel@ffmpeg.org Subject: RE: [EXTERNAL][FFmpeg-devel] [PATCH] Added support for MB_INFO CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Quoting Carotti, Elias (2022-06-17 10:41:30)
Hi all, any chance someone could possibly have a look at this patch, please? Thanks in advance
This looks like it belongs in AVVideoEncParams. -- 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-request@ffmpeg.org with subject "unsubscribe". NICE SRL, viale Monte Grappa 3/5, 20124 Milano, Italia, Registro delle Imprese di Milano Monza Brianza Lodi REA n. 2096882, Capitale Sociale: 10.329,14 EUR i.v., Cod. Fisc. e P.IVA 01133050052, Societa con Socio Unico