From: lance.lmwang@gmail.com To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v3 2/3] avcodec/libopenh264enc: make the profile configuablable correctly Date: Fri, 14 Jan 2022 21:49:38 +0800 Message-ID: <20220114134938.GA26619@gmail.com> (raw) In-Reply-To: <24646e6-2361-8b18-83b7-c764f422ec3@martin.st> On Fri, Jan 14, 2022 at 02:07:26PM +0200, Martin Storsjö wrote: > On Fri, 14 Jan 2022, lance.lmwang@gmail.com wrote: > > > From: Limin Wang <lance.lmwang@gmail.com> > > > > due to the limitations set in d3a7bdd4ac54349aea9150a234478635d50ebd87, > > you weren't able to use main profile with OpenH264 1.8, or high profile > > with older versions > > > > Reviewed-by: Martin Storsjö <martin@martin.st> > > Signed-off-by: Limin Wang <lance.lmwang@gmail.com> > > --- > > libavcodec/libopenh264enc.c | 8 ++++---- > > 1 file changed, 4 insertions(+), 4 deletions(-) > > > > diff --git a/libavcodec/libopenh264enc.c b/libavcodec/libopenh264enc.c > > index 5b5914c..1bad233 100644 > > --- a/libavcodec/libopenh264enc.c > > +++ b/libavcodec/libopenh264enc.c > > @@ -220,26 +220,25 @@ static av_cold int svc_encode_init(AVCodecContext *avctx) > > #endif > > > > switch (s->profile) { > > -#if OPENH264_VER_AT_LEAST(1, 8) > > case FF_PROFILE_H264_HIGH: > > param.iEntropyCodingModeFlag = 1; > > av_log(avctx, AV_LOG_VERBOSE, "Using CABAC, " > > "select EProfileIdc PRO_HIGH in libopenh264.\n"); > > break; > > -#else > > case FF_PROFILE_H264_MAIN: > > param.iEntropyCodingModeFlag = 1; > > av_log(avctx, AV_LOG_VERBOSE, "Using CABAC, " > > "select EProfileIdc PRO_MAIN in libopenh264.\n"); > > break; > > -#endif > > - case FF_PROFILE_H264_CONSTRAINED_BASELINE: > > case FF_PROFILE_UNKNOWN: > > + s->profile = FF_PROFILE_H264_CONSTRAINED_BASELINE; > > + case FF_PROFILE_H264_CONSTRAINED_BASELINE: > > I don't think it's specifically necessary to move the case labels around > like this; you could just leave both case labels above it, and the > assignment would be a no-op for one case. (No need to resend the patch for > that, do whichever form you prefer.) OK, will not move the case lables as suggestion. > > > param.iEntropyCodingModeFlag = 0; > > av_log(avctx, AV_LOG_VERBOSE, "Using CAVLC, " > > "select EProfileIdc PRO_BASELINE in libopenh264.\n"); > > break; > > default: > > + s->profile = FF_PROFILE_H264_CONSTRAINED_BASELINE; > > param.iEntropyCodingModeFlag = 0; > > av_log(avctx, AV_LOG_WARNING, "Unsupported profile, " > > "select EProfileIdc PRO_BASELINE in libopenh264.\n"); > > @@ -251,6 +250,7 @@ static av_cold int svc_encode_init(AVCodecContext *avctx) > > param.sSpatialLayers[0].fFrameRate = param.fMaxFrameRate; > > param.sSpatialLayers[0].iSpatialBitrate = param.iTargetBitrate; > > param.sSpatialLayers[0].iMaxSpatialBitrate = param.iMaxBitrate; > > + param.sSpatialLayers[0].uiProfileIdc = s->profile; > > Thanks, this seems sensible to me. This is ok if you've tested that setting > profile to FF_PROFILE_H264_CONSTRAINED_BASELINE (as opposed to PRO_BASELINE) > does work with both some old and some recent version of OpenH264. Yes, have tested with v1.4.0, v1.7.0 and master. > > // Martin -- Thanks, Limin Wang _______________________________________________ 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-01-14 13:49 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-13 10:45 [FFmpeg-devel] [PATCH 1/3] avcodec/libopenh264enc: support for colorspace and range information lance.lmwang 2022-01-13 10:45 ` [FFmpeg-devel] [PATCH 2/3] avcodec/libopenh264enc: make the profile configuablable correctly lance.lmwang 2022-01-13 21:57 ` Martin Storsjö 2022-01-14 3:17 ` lance.lmwang 2022-01-13 10:45 ` [FFmpeg-devel] [PATCH 3/3] avcodec/libopenh264enc: set iEntropyCodingModeFlag by coder option lance.lmwang 2022-01-13 22:01 ` Martin Storsjö 2022-01-14 3:20 ` lance.lmwang 2022-01-13 21:35 ` [FFmpeg-devel] [PATCH 1/3] avcodec/libopenh264enc: support for colorspace and range information Martin Storsjö 2022-01-14 2:59 ` lance.lmwang 2022-01-14 9:00 ` [FFmpeg-devel] [PATCH v2 " lance.lmwang 2022-01-14 9:00 ` [FFmpeg-devel] [PATCH v2 2/3] avcodec/libopenh264enc: make the profile configuablable correctly lance.lmwang 2022-01-14 9:28 ` Martin Storsjö 2022-01-14 9:43 ` lance.lmwang 2022-01-14 9:00 ` [FFmpeg-devel] [PATCH v2 3/3] avcodec/libopenh264enc: set iEntropyCodingModeFlag by coder option lance.lmwang 2022-01-14 9:30 ` Martin Storsjö 2022-01-14 9:23 ` [FFmpeg-devel] [PATCH v2 1/3] avcodec/libopenh264enc: support for colorspace and range information Martin Storsjö 2022-01-14 9:55 ` [FFmpeg-devel] [PATCH v3 " lance.lmwang 2022-01-14 9:55 ` [FFmpeg-devel] [PATCH v3 2/3] avcodec/libopenh264enc: make the profile configuablable correctly lance.lmwang 2022-01-14 12:07 ` Martin Storsjö 2022-01-14 13:49 ` lance.lmwang [this message] 2022-01-14 9:55 ` [FFmpeg-devel] [PATCH v3 3/3] avcodec/libopenh264enc: set iEntropyCodingModeFlag by coder option lance.lmwang
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=20220114134938.GA26619@gmail.com \ --to=lance.lmwang@gmail.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