From: Zhao Zhili <quinkblack@foxmail.com>
To: ffmpeg-devel@ffmpeg.org
Cc: Zhao Zhili <zhilizhao@tencent.com>
Subject: [FFmpeg-devel] [PATCH] avcodec/evc: Remove redefine of HEVC_MAX_ENTRY_POINT_OFFSETS
Date: Thu, 22 Feb 2024 14:41:50 +0800
Message-ID: <tencent_CA400B832623D08226E1E7D0AAB6D3125C06@qq.com> (raw)
From: Zhao Zhili <zhilizhao@tencent.com>
---
libavcodec/evc.h | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/libavcodec/evc.h b/libavcodec/evc.h
index 9711c760fe..e493455a42 100644
--- a/libavcodec/evc.h
+++ b/libavcodec/evc.h
@@ -141,15 +141,6 @@ enum {
// A.4.1: table A.1 allows at most 600 slice segments for any level.
EVC_MAX_SLICE_SEGMENTS = 600,
-
- // 7.4.7.1: in the worst case (tiles_enabled_flag and
- // entropy_coding_sync_enabled_flag are both set), entry points can be
- // placed at the beginning of every Ctb row in every tile, giving an
- // upper bound of (num_tile_columns_minus1 + 1) * PicHeightInCtbsY - 1.
- // Only a stream with very high resolution and perverse parameters could
- // get near that, though, so set a lower limit here with the maximum
- // possible value for 4K video (at most 135 16x16 Ctb rows).
- HEVC_MAX_ENTRY_POINT_OFFSETS = EVC_MAX_TILE_COLUMNS * 135,
};
#endif // AVCODEC_EVC_H
--
2.42.0
_______________________________________________
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 reply other threads:[~2024-02-22 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240222064217eucas1p28c0b4c2f5c918fe99acdda64d5793642@eucas1p2.samsung.com>
2024-02-22 6:41 ` Zhao Zhili [this message]
2024-02-22 6:55 ` mypopy
2024-02-23 7:50 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
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_CA400B832623D08226E1E7D0AAB6D3125C06@qq.com \
--to=quinkblack@foxmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=zhilizhao@tencent.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