From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>, "softworkz@hotmail.com" <softworkz@hotmail.com> Subject: Re: [FFmpeg-devel] [PATCH] qsv: add requirement for the mininal version of libmfx Date: Tue, 24 May 2022 08:46:53 +0000 Message-ID: <aa25261c8ea5902c331d9737b1b7ccecec2534cf.camel@intel.com> (raw) In-Reply-To: <DM8P223MB03656706BDBD7BAD3E57B6FEBAD59@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Haihao > > Xiang > > Sent: Sunday, May 22, 2022 2:19 PM > > To: ffmpeg-devel@ffmpeg.org > > Cc: Haihao Xiang <haihao.xiang@intel.com> > > Subject: [FFmpeg-devel] [PATCH] qsv: add requirement for the mininal > > version of libmfx > > > > libmfx 1.28 was released 3 years ago, it is easy to get a greater > > version than 1.28. We may remove lots of compile-time checks if adding > > the requirement for the minimal version in the configure script. > > --- [...] > > LookAheadDepth: %"PRIu16"\n", > > - info->ICQQuality, co2->LookAheadDepth); > > - } > > -#endif > > -#if QSV_HAVE_QVBR > > - else if (info->RateControlMethod == MFX_RATECONTROL_QVBR) { > > - av_log(avctx, AV_LOG_VERBOSE, "QVBRQuality: %"PRIu16"\n", > > - co3->QVBRQuality); > > + av_log(avctx, AV_LOG_VERBOSE, "ICQQuality: %"PRIu16"\n", info- > > > ICQQuality); > > This branch is now identical with the previous one. But I wouldn't > mind leaving it like this as it's better readable. > > Probably somebody will mind the curly brace formatting around else if, > though. > Thanks for pointing it out. I'll change it when merging the patch. [...] > > LGTM. This patch is a great improvement to the qsv code as it is dropping > a lot of old and unnecessary clutter. > Thanks for reviewing this patch. I'll applying it if no more comment. BRs Haihao _______________________________________________ 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".
next prev parent reply other threads:[~2022-05-24 8:47 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-22 12:19 Haihao Xiang 2022-05-22 14:04 ` Jean-Baptiste Kempf 2022-05-22 18:09 ` Soft Works 2022-05-24 8:46 ` Xiang, Haihao [this message] 2022-05-25 16:05 ` Timo Rothenpieler 2022-05-25 16:22 ` Leo Izen 2022-05-26 0:42 ` Xiang, Haihao 2022-05-26 0:39 ` Xiang, Haihao
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=aa25261c8ea5902c331d9737b1b7ccecec2534cf.camel@intel.com \ --to=haihao.xiang-at-intel.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=softworkz@hotmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git