From: Benjamin Cheng via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org> Cc: Benjamin Cheng <ben@bcheng.me>, xyz1001 <zgzf1001@gmail.com> Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/dxva2.c: fix dxva2 does not support H264 baseline profile Date: Sat, 14 Oct 2023 12:36:42 -0400 Message-ID: <CW8B4RUTL6XQ.2GZYWSUGQ64EI@bcheng.me> (raw) In-Reply-To: <20231014035957.66508-1-zgzf1001@gmail.com> On Fri Oct 13, 2023 at 11:59 PM EDT, xyz1001 wrote: > dxva2 fail to init when decode h264 with baseline profile becase `prof_h264_high` does not contains `AV_PROFILE_H264_BASELINE` and `dxva_check_codec_compatibility` will return error prof_h264_high uses either DXVA2_ModeH264_E or DXVA2_ModeH264_F, which only supports up to H.264 High, and H.264 Baseline has features that are not in High. You have to use a different DXVA profile for Baseline. > --- > libavcodec/dxva2.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/libavcodec/dxva2.c b/libavcodec/dxva2.c > index d7bc587562..e6b83f89cc 100644 > --- a/libavcodec/dxva2.c > +++ b/libavcodec/dxva2.c > @@ -61,7 +61,8 @@ typedef struct dxva_mode { > static const int prof_mpeg2_main[] = {AV_PROFILE_MPEG2_SIMPLE, > AV_PROFILE_MPEG2_MAIN, > AV_PROFILE_UNKNOWN}; > -static const int prof_h264_high[] = {AV_PROFILE_H264_CONSTRAINED_BASELINE, > +static const int prof_h264_high[] = {AV_PROFILE_H264_BASELINE, > + AV_PROFILE_H264_CONSTRAINED_BASELINE, > AV_PROFILE_H264_MAIN, > AV_PROFILE_H264_HIGH, > AV_PROFILE_UNKNOWN}; _______________________________________________ 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-10-14 16:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-14 3:59 xyz1001 2023-10-14 16:36 ` Benjamin Cheng via ffmpeg-devel [this message] 2023-10-14 17:10 ` Hendrik Leppkes
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=CW8B4RUTL6XQ.2GZYWSUGQ64EI@bcheng.me \ --to=ffmpeg-devel@ffmpeg.org \ --cc=ben@bcheng.me \ --cc=zgzf1001@gmail.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