From: Zhao Zhili <quinkblack-at-foxmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 1/6] tests: Add enhanced-flv-hevc-hdr10 for demux and mux HDR color info
Date: Thu, 20 Mar 2025 00:36:00 +0800
Message-ID: <tencent_BF396A6A7E46AD3E3899C2A5B410686E020A@qq.com> (raw)
In-Reply-To: <CAPBf_O=DtFf2tKuYz5gnk-YoyP+bbZsyT5XV4j-Zs8mc-1F37g@mail.gmail.com>
> On Mar 19, 2025, at 23:38, Sean McGovern <gseanmcg@gmail.com> wrote:
>
> Hi Zhao,
>
> On Mon, Mar 10, 2025 at 10:35 PM Zhao Zhili
> <quinkblack-at-foxmail.com@ffmpeg.org> wrote:
>>
>> From: Zhao Zhili <zhilizhao@tencent.com>
>>
>> ---
>> tests/fate/flvenc.mak | 4 +
>> tests/ref/fate/enhanced-flv-hevc-hdr10 | 100 +++++++++++++++++++++++++
>> 2 files changed, 104 insertions(+)
>> create mode 100644 tests/ref/fate/enhanced-flv-hevc-hdr10
>
> Sorry for not addressing this earlier -- this fails on big-endian
> PowerPC (both 32- and 64-bit). Please have a look at FATE.
> The test should probably explicitly request that the sample is little-endian.
OK. It’s due to ffprobe shows the native endian yuv420p10 as yuv420p10le on little endian
arch.
I can filter out the pix_fmt entry, but it’s a general problem in test: there is no way to separate
native endian from explicit big/little endian in pixel format.
>
> Thanks,
> Sean McGovern
> _______________________________________________
> 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:[~2025-03-19 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 2:34 Zhao Zhili
2025-03-12 4:20 ` Steven Liu
2025-03-19 15:38 ` Sean McGovern
2025-03-19 16:36 ` Zhao Zhili [this message]
2025-03-20 3:09 ` James Almer
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_BF396A6A7E46AD3E3899C2A5B410686E020A@qq.com \
--to=quinkblack-at-foxmail.com@ffmpeg.org \
--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