From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH v1] avcodec/av1dec: Add tile list OBU to decompose list Date: Thu, 21 Dec 2023 20:14:19 +0100 Message-ID: <AS8P250MB074496124DE11775B62ED2BE8F95A@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw) In-Reply-To: <0ec4a5a324fcb829eea33916dfc4b44e7a91b79b.camel@intel.com> Wang, Fei W: > On Wed, 2023-12-20 at 17:11 +0100, Andreas Rheinhardt wrote: >> fei.w.wang-at-intel.com@ffmpeg.org: >>> From: Fei Wang <fei.w.wang@intel.com> >>> >>> Show the unsupported message and return unsupported for clips >>> contain >>> tile list OBU since it hasn't been implemented. Otherwise, decoding >>> maybe successful but result is incorrect. >>> >>> Signed-off-by: Fei Wang <fei.w.wang@intel.com> >>> --- >>> libavcodec/av1dec.c | 5 +++++ >>> 1 file changed, 5 insertions(+) >>> >>> diff --git a/libavcodec/av1dec.c b/libavcodec/av1dec.c >>> index 4dcde234c6..629e37c3f8 100644 >>> --- a/libavcodec/av1dec.c >>> +++ b/libavcodec/av1dec.c >>> @@ -805,6 +805,7 @@ static const CodedBitstreamUnitType >>> decompose_unit_types[] = { >>> AV1_OBU_SEQUENCE_HEADER, >>> AV1_OBU_TEMPORAL_DELIMITER, >>> AV1_OBU_TILE_GROUP, >>> + AV1_OBU_TILE_LIST, >> >> What do you need this for? Decomposing it would only change whether >> CodedBitstreamUnit.content is available, but you are only reading >> CodedBitstreamUnit.type. > > To show the unsupported error and let user know that there are tile > list OBUs in bitstream that decoder can't handle them. Otherwise, like > my commit mentioned, tile list obu bitsteam may be decoded 'successful' > according to log. > As I said: You do not need CodedBitstreamUnit.content for the error message. >> >>> }; >>> >>> static av_cold int av1_decode_init(AVCodecContext *avctx) >>> @@ -1327,6 +1328,10 @@ static int >>> av1_receive_frame_internal(AVCodecContext *avctx, AVFrame *frame) >>> } >>> break; >>> case AV1_OBU_TILE_LIST: >>> + av_log(avctx, AV_LOG_ERROR, "Large scale tile decoding >>> is unsupported.\n"); >>> + ret = AVERROR_PATCHWELCOME; >>> + goto end; >>> + break; >>> case AV1_OBU_TEMPORAL_DELIMITER: >>> case AV1_OBU_PADDING: >>> break; >> >> _______________________________________________ >> 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". _______________________________________________ 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-12-21 19:12 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-20 8:43 fei.w.wang-at-intel.com 2023-12-20 16:11 ` Andreas Rheinhardt 2023-12-21 0:46 ` Wang, Fei W 2023-12-21 19:14 ` Andreas Rheinhardt [this message] 2023-12-22 1:22 ` Wang, Fei W 2023-12-22 7:41 ` Andreas Rheinhardt 2023-12-26 3:41 ` Wang, Fei W
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=AS8P250MB074496124DE11775B62ED2BE8F95A@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM \ --to=andreas.rheinhardt@outlook.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