From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mov: Fix endian-dependent parsing
Date: Fri, 21 Jan 2022 12:52:33 +0200 (EET)
Message-ID: <6ace45d6-1796-79e-bfe6-a8be9567d82@martin.st> (raw)
In-Reply-To: <AM7PR03MB6660D256CE0D1451F3801FDC8F5B9@AM7PR03MB6660.eurprd03.prod.outlook.com>
On Fri, 21 Jan 2022, Andreas Rheinhardt wrote:
> MOVAtom.type is always read as a little-endian number
> (despite MOV/ISOBMFF being big-endian).
> Fixes the matroska-dovi-write-config8 FATE-test on big-endian
> arches (which runs into the "index out of range" warning message).
>
> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
> ---
> A few days ago I sent a patch using the dv84.mov sample
> that also failed on the PPC BE endian FATE box, yet this test
> reencoded the audio and so I blamed this (despite encoder and
> decoder being fixed-point); see [1]. Seems like I was wrong
> and the fixed-point codecs are indeed bitexact.
>
> [1]: https://ffmpeg.org/pipermail/ffmpeg-devel/2022-January/291792.html
>
> libavformat/mov.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/mov.c b/libavformat/mov.c
> index e401cd39b5..1437d160f8 100644
> --- a/libavformat/mov.c
> +++ b/libavformat/mov.c
> @@ -407,7 +407,7 @@ retry:
> atom.size -= 16;
>
> if (!key && c->found_hdlr_mdta && c->meta_keys) {
> - uint32_t index = AV_RB32(&atom.type);
> + uint32_t index = av_bswap32(atom.type); // BE number has been read as LE
LGTM.
// Martin
_______________________________________________
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:[~2022-01-21 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 10:08 Andreas Rheinhardt
2022-01-21 10:52 ` Martin Storsjö [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=6ace45d6-1796-79e-bfe6-a8be9567d82@martin.st \
--to=martin@martin.st \
--cc=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