From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] fftools/ffprobe: Remove endianness dependency of pix fmt when, bitexact
Date: Fri, 21 Mar 2025 13:51:54 +0100
Message-ID: <GV1SPRMB00361F3758F01B5291A0B6D08FDB2@GV1SPRMB0036.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <tencent_9B099ACA409E9A209F3BAB8A4EC370312D08@qq.com>
Zhao Zhili:
> On Mar 21, 2025, at 19:23, Andreas Rheinhardt <andreas.rheinhardt@outlook.com> wrote:
>>
>> Patch attached.
>
> Sometimes the bitstream has builtin endian, not native endian, in which case it shouldn’t be ignored.
>
Do you have a list of all decoders for which this is true?
Anyway, the documentation of the bitexact flag says that the output
shall not be dependent on the specific build, which is currently not
guaranteed. If we can't distinguish the cases in which a decoder output
in the codec's "native" endianness from the cases in which it just
outputs in the system's endianness (and I don't see how we would
distinguish these cases), then we need to fix up both to ensure that the
output really does not depend on the specific system.
Should there be a need in the future, we could add an option to be
bitexact, but not normalize the pixel formats.
- Andreas
_______________________________________________
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-21 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 11:23 Andreas Rheinhardt
2025-03-21 11:40 ` Zhao Zhili
2025-03-21 12:51 ` Andreas Rheinhardt [this message]
2025-03-21 13:09 ` Zhao Zhili
2025-03-21 13:14 ` Andreas Rheinhardt
2025-03-24 17:24 ` 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=GV1SPRMB00361F3758F01B5291A0B6D08FDB2@GV1SPRMB0036.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