From: Sean McGovern <gseanmcg@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] tests: Fix enhanced-flv-hevc-hdr10 on big endian systems Date: Sat, 29 Mar 2025 13:20:34 -0400 Message-ID: <CAPBf_Om2eH2wgVOJAYxYFj+H8MNbs0b5pX_kkYOn7dJkkS8Dvg@mail.gmail.com> (raw) In-Reply-To: <DU0P250MB074768470F68F3BE4DB640518FA32@DU0P250MB0747.EURP250.PROD.OUTLOOK.COM> Hi, On Sat, Mar 29, 2025, 13:07 Andreas Rheinhardt < andreas.rheinhardt@outlook.com> wrote: > Zhao Zhili: > > Ping. Fate on powerpc is still broken. > > > > I still think that we should strip le/be in ffprobe. The documentation > of bitexact requires it for the cases where decoders output native > endianness and if we can't distinguish the cases of native endianness vs > explicit source endianness (and we can't really), then we have to strip > it in all cases. > > >> On Mar 21, 2025, at 12:11, Zhao Zhili <quinkblack@foxmail.com> wrote: > >> > >>> > >>> On Mar 21, 2025, at 05:50, James Almer <jamrial@gmail.com> wrote: > >>> > >>> On 3/20/2025 10:17 AM, Zhao Zhili wrote: > >>>> From: Zhao Zhili <zhilizhao@tencent.com> > >>>> hevc decoder output native endian yuv420p10. yuv420p10 is alias of > >>>> yuv420p10le on little endian system, and yuv420p10be on big endian > >>>> system. > >>>> --- > >>>> tests/fate/flvenc.mak | 2 +- > >>>> tests/ref/fate/enhanced-flv-hevc-hdr10 | 19 ------------------- > >>>> 2 files changed, 1 insertion(+), 20 deletions(-) > >>>> diff --git a/tests/fate/flvenc.mak b/tests/fate/flvenc.mak > >>>> index 471bb0fe72..22208aa64b 100644 > >>>> --- a/tests/fate/flvenc.mak > >>>> +++ b/tests/fate/flvenc.mak > >>>> @@ -15,7 +15,7 @@ fate-enhanced-flv-av1: CMD = stream_remux ivf > $(TARGET_SAMPLES)/av1/seq_hdr_op_p > >>>> FATE_ENHANCED_FLVENC_FFMPEG_FFPROBE-$(call REMUX, FLV HEVC, > FLV_DEMUXER HEVC_DECODER HEVC_PARSER) += fate-enhanced-flv-hevc-hdr10 > >>>> fate-enhanced-flv-hevc-hdr10: CMD = stream_remux hevc > $(TARGET_SAMPLES)/hevc/hdr10_plus_h265_sample.hevc "-c:v hevc" \ > >>>> - flv "-c copy" "-c:v hevc" "-c copy" "-show_frames" > >>>> + flv "-c copy" "-c:v hevc" "-c copy" "-show_frames > -show_entries > frame=media_type,stream_index,key_frame,pts,width,height,pict_type,color_range,color_space,color_primaries,color_transfer,chroma_location,side_data" > >>>> FATE_ENHANCED_FLVENC_FFMPEG_FFPROBE-$(call REMUX, FLV, FLV_DEMUXER > AAC_PARSER AC3_PARSER OPUS_PARSER FLAC_PARSER VP9_PARSER AV1_PARSER > HEVC_PARSER H264_PARSER) += fate-enhanced-flv-multitrack > >>>> fate-enhanced-flv-multitrack: CMD = stream_remux flv > $(TARGET_SAMPLES)/flv/multitrack.flv "" flv "-map 0" "" "-c copy -map 0" \ > >>>> diff --git a/tests/ref/fate/enhanced-flv-hevc-hdr10 > b/tests/ref/fate/enhanced-flv-hevc-hdr10 > >>>> index cb7acea328..8495572705 100644 > >>>> --- a/tests/ref/fate/enhanced-flv-hevc-hdr10 > >>>> +++ b/tests/ref/fate/enhanced-flv-hevc-hdr10 > >>>> @@ -10,28 +10,9 @@ media_type=video > >>>> stream_index=0 > >>>> key_frame=1 > >>>> pts=0 > >>>> -pts_time=0.000000 > >>>> -pkt_dts=0 > >>>> -pkt_dts_time=0.000000 > >>>> -best_effort_timestamp=0 > >>>> -best_effort_timestamp_time=0.000000 > >>>> -duration=N/A > >>>> -duration_time=N/A > >>>> -pkt_pos=459 > >>>> -pkt_size=77718 > >>>> width=1280 > >>>> height=720 > >>>> -crop_top=0 > >>>> -crop_bottom=0 > >>>> -crop_left=0 > >>>> -crop_right=0 > >>>> -pix_fmt=yuv420p10le > >>>> -sample_aspect_ratio=N/A > >>>> pict_type=I > >>>> -interlaced_frame=0 > >>>> -top_field_first=0 > >>>> -lossless=0 > >>>> -repeat_pict=0 > >>>> color_range=tv > >>>> color_space=bt2020nc > >>>> color_primaries=bt2020 > >>> > >>> Did you check the test i mentioned that solved this with a sed string > replace? I'd rather do that than print less information. > >> > >> The test first remux hevc to flv, then probe and check frame colorspace > and side data information. How to use sed together with stream_remux? > >> > >>> > >>> _______________________________________________ > >>> ffmpeg-devel mailing list > >>> ffmpeg-devel@ffmpeg.org <mailto:ffmpeg-devel@ffmpeg.org> > >>> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > >>> > >>> To unsubscribe, visit link above, or email > >>> ffmpeg-devel-request@ffmpeg.org <mailto: > 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". > As an aside, my G5 has been unavailable ever since a package was pushed to Debian sid that broke boot. The machine is headless and nothing I have tried so far will resurrect it. -- 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".
prev parent reply other threads:[~2025-03-29 17:20 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-03-20 13:17 Zhao Zhili 2025-03-20 21:31 ` Sean McGovern 2025-03-20 21:50 ` James Almer 2025-03-21 4:11 ` Zhao Zhili 2025-03-29 15:52 ` Zhao Zhili 2025-03-29 17:06 ` Andreas Rheinhardt 2025-03-29 17:20 ` Sean McGovern [this message]
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=CAPBf_Om2eH2wgVOJAYxYFj+H8MNbs0b5pX_kkYOn7dJkkS8Dvg@mail.gmail.com \ --to=gseanmcg@gmail.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