From: "\"zhilizhao(赵志立)\"" <quinkblack@foxmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/2] avcodec/mediacodecdec: check ff_Build_SDK_INT return value Date: Mon, 9 Jan 2023 21:14:21 +0800 Message-ID: <tencent_FC349580C8341F3E7B564D9DB0E0D85A2A09@qq.com> (raw) In-Reply-To: <1665d077c1fb2ef40525643369a66abdda7f0f04.camel@haerdin.se> > On Jan 9, 2023, at 20:34, Tomas Härdin <git@haerdin.se> wrote: > > tis 2023-01-10 klockan 00:36 +0800 skrev Zhao Zhili: >> From: Zhao Zhili <zhilizhao@tencent.com> >> >> Signed-off-by: Zhao Zhili <zhilizhao@tencent.com> >> --- >> libavcodec/mediacodecdec.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/libavcodec/mediacodecdec.c b/libavcodec/mediacodecdec.c >> index 11f655a9aa..6ef23d7369 100644 >> --- a/libavcodec/mediacodecdec.c >> +++ b/libavcodec/mediacodecdec.c >> @@ -415,7 +415,7 @@ static av_cold int >> mediacodec_decode_init(AVCodecContext *avctx) >> s->ctx->codec_name, ret); >> >> sdk_int = ff_Build_SDK_INT(avctx); >> - if (sdk_int <= 23 && >> + if (sdk_int > 0 && sdk_int <= 23 && >> strcmp(s->ctx->codec_name, >> "OMX.amlogic.mpeg2.decoder.awesome") == 0) { >> av_log(avctx, AV_LOG_INFO, "Enabling workaround for %s on >> API=%d\n", >> s->ctx->codec_name, sdk_int); > > Maybe it should bail out if it can't figure out the SDK level? ff_Build_SDK_INT always fail when JVM isn’t available and target api level < 24. If there are more usecases of ff_Build_SDK_INT(), we might make it more robust. For current use case: 1. If JVM is available, ff_Build_SDK_INT() should success, nothing changed. 2. If JVM is unavailable, sdk_int > 0 && sdk_int <= 23 should always be false, since android_get_device_api_level() only available after API >= 24. Then amlogic_mpeg2_api23_workaround doesn’t work. Even if we can make ff_Build_SDK_INT() works when API < 24, get codec name doesn’t work, then amlogic_mpeg2_api23_workaround doesn’t work neither. I don’t think it’s a serious issue. Old usecase with JNI works, and this special workaround might not necessary now. The patch fixed a hypothetical case when the codec is OMX.amlogic.mpeg2.decoder.awesome and the device api level >= 28 (get codec name works after API >= 28), amlogic_mpeg2_api23_workaround is enabled (which shouldn’t). > > /Tomas > > _______________________________________________ > 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". _______________________________________________ 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:[~2023-01-09 13:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20230109163640.343220-1-quinkblack@foxmail.com> 2023-01-09 16:36 ` Zhao Zhili 2023-01-09 12:34 ` Tomas Härdin 2023-01-09 13:14 ` "zhilizhao(赵志立)" [this message] 2023-01-09 16:43 ` Tomas Härdin
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=tencent_FC349580C8341F3E7B564D9DB0E0D85A2A09@qq.com \ --to=quinkblack@foxmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /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