From: Eric Joyner <erj@erj.cc> To: ffmpeg-devel@ffmpeg.org Cc: Eric Joyner <erj@erj.cc> Subject: [FFmpeg-devel] [PATCH 2/2] libavformat: Enable jpeg streams in HEIF MOVContext Date: Wed, 16 Jul 2025 19:30:02 -0700 Message-ID: <20250717023057.678-3-erj@erj.cc> (raw) In-Reply-To: <20250717023057.678-1-erj@erj.cc> Nikon HEIFs from a camera or NX studio include a small jpeg thumbnail in addition to the expected HEVC thumbnails; allowing jpegs allows all thumbnails to have an associated stream for Nikon HEIF files. With this, Nikon HEIFs can finally be decoded without failing and the thumbnails can be extracted into their own files. Signed-off-by: Eric Joyner <erj@erj.cc> --- libavformat/mov.c | 1 + 1 file changed, 1 insertion(+) diff --git a/libavformat/mov.c b/libavformat/mov.c index 7010e13b50..19b31b032d 100644 --- a/libavformat/mov.c +++ b/libavformat/mov.c @@ -8840,6 +8840,7 @@ static int mov_read_infe(MOVContext *c, AVIOContext *pb, MOVAtom atom, int idx) switch (item_type) { case MKTAG('a','v','0','1'): + case MKTAG('j','p','e','g'): case MKTAG('h','v','c','1'): ret = heif_add_stream(c, c->heif_item[idx]); if (ret < 0) -- 2.49.0.windows.1 _______________________________________________ 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-07-17 2:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-17 2:30 [FFmpeg-devel] [PATCH 0/2] Fix Nikon HEIF decoding error Eric Joyner 2025-07-17 2:30 ` [FFmpeg-devel] [PATCH 1/2] libavformat: Support multiple thumbnails in HEIF Eric Joyner 2025-07-17 2:30 ` Eric Joyner [this message] 2025-07-17 11:54 ` [FFmpeg-devel] [PATCH 2/2] libavformat: Enable jpeg streams in HEIF MOVContext Lynne 2025-07-17 15:54 ` [FFmpeg-devel] [PATCH 0/2] Fix Nikon HEIF decoding error compn
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=20250717023057.678-3-erj@erj.cc \ --to=erj@erj.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