From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 5/5] avcodec/vvcdec: support mv wraparound
Date: Tue, 4 Jun 2024 02:40:54 +0200
Message-ID: <20240604004054.GG2821752@pb2> (raw)
In-Reply-To: <TYSPR06MB6433A1570473A7C0A9E0B7BFAAFF2@TYSPR06MB6433.apcprd06.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 2291 bytes --]
On Mon, Jun 03, 2024 at 08:51:16PM +0800, Nuo Mi wrote:
> A 360 video specific tool
> see https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=9503377
>
> passed files:
> DMVR_A_Huawei_3.bit
> WRAP_D_InterDigital_4.bit
> WRAP_A_InterDigital_4.bit
> WRAP_B_InterDigital_4.bit
> WRAP_C_InterDigital_4.bit
> ERP_A_MediaTek_3.bit
> ---
> libavcodec/vvc/inter.c | 81 ++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 79 insertions(+), 2 deletions(-)
seems to break fate-vvc-conformance-WRAP_A_4, maybe the fate checksums need to be updated ?
TEST vvc-conformance-WRAP_A_4
--- ./tests/ref/fate/vvc-conformance-WRAP_A_4 2024-06-03 22:55:42.173081332 +0200
+++ tests/data/fate/vvc-conformance-WRAP_A_4 2024-06-04 02:39:44.835650168 +0200
@@ -4,11 +4,11 @@
#dimensions 0: 1680x832
#sar 0: 0/1
0, 0, 0, 1, 4193280, 0xbd70f1b3
-0, 1, 1, 1, 4193280, 0x64e160d5
-0, 2, 2, 1, 4193280, 0xd20722ea
-0, 3, 3, 1, 4193280, 0xa1d00055
-0, 4, 4, 1, 4193280, 0xe3dcb9cd
-0, 5, 5, 1, 4193280, 0xcf97b6cf
-0, 6, 6, 1, 4193280, 0xd87b73d0
-0, 7, 7, 1, 4193280, 0x0f8ee2bc
-0, 8, 8, 1, 4193280, 0x76607ca4
+0, 1, 1, 1, 4193280, 0x491104c9
+0, 2, 2, 1, 4193280, 0xf600c2c1
+0, 3, 3, 1, 4193280, 0x1e3c8e2b
+0, 4, 4, 1, 4193280, 0xad275e45
+0, 5, 5, 1, 4193280, 0xcd6103d7
+0, 6, 6, 1, 4193280, 0x0ec8cfbd
+0, 7, 7, 1, 4193280, 0x2f664486
+0, 8, 8, 1, 4193280, 0x543eb3fc
Test vvc-conformance-WRAP_A_4 failed. Look at tests/data/fate/vvc-conformance-WRAP_A_4.err for details.
make: *** [tests/Makefile:311: fate-vvc-conformance-WRAP_A_4] Error 1
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Some people wanted to paint the bikeshed green, some blue and some pink.
People argued and fought, when they finally agreed, only rust was left.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2024-06-04 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240603125117.10791-1-nuomi2021@gmail.com>
2024-06-03 12:51 ` [FFmpeg-devel] [PATCH 2/5] avcodec/vvcdec: misc, move src offset inside emulated_edge Nuo Mi
2024-06-03 12:51 ` [FFmpeg-devel] [PATCH 3/5] avcodec/vvcdec: refact out emulated_edge_no_wrap Nuo Mi
2024-06-03 12:51 ` [FFmpeg-devel] [PATCH 4/5] avcodec/vvcdec: misc, reindent inter.c Nuo Mi
2024-06-03 12:51 ` [FFmpeg-devel] [PATCH 5/5] avcodec/vvcdec: support mv wraparound Nuo Mi
2024-06-04 0:40 ` Michael Niedermayer [this message]
2024-06-04 12:11 ` Nuo Mi
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=20240604004054.GG2821752@pb2 \
--to=michael@niedermayer.cc \
--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