Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Vignesh Venkat via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Vignesh Venkat <vigneshv@google.com>
Subject: Re: [FFmpeg-devel] [PATCH v3] avformat/mov: Add support for demuxing still HEIC images
Date: Wed, 10 Jan 2024 13:05:33 -0800
Message-ID: <CAOJaEPKirT89JdbfTAjOhwxZ5JqOCwsjXBdeJUELMx9MLEmUnw@mail.gmail.com> (raw)
In-Reply-To: <ad3842fc-cb81-4db4-be46-2ee5b9b82114@gmail.com>

On Tue, Jan 9, 2024 at 4:39 AM James Almer <jamrial@gmail.com> wrote:
>
> On 10/4/2023 1:40 PM, Vignesh Venkatasubramanian via ffmpeg-devel wrote:
> > They are similar to AVIF images (both use the HEIF container).
> > The only additional work needed is to parse the hvcC box and put
> > it in the extradata.
> >
> > With this patch applied, ffmpeg (when built with an HEVC decoder)
> > is able to decode the files in
> > https://github.com/nokiatech/heif/tree/gh-pages/content/images
> >
> > Also add a couple of fate tests with samples from
> > https://github.com/nokiatech/heif_conformance/tree/master/conformance_files
> >
> > Partially fixes trac ticket #6521.
> >
> > Signed-off-by: Vignesh Venkatasubramanian <vigneshv@google.com>
> > ---
> >   libavformat/isom.h                            |  2 +
> >   libavformat/mov.c                             | 41 ++++++++++++++++++-
> >   tests/fate/mov.mak                            |  6 +++
> >   .../fate/mov-heic-demux-still-image-1-item    | 11 +++++
> >   .../mov-heic-demux-still-image-multiple-items | 11 +++++
> >   5 files changed, 70 insertions(+), 1 deletion(-)
> >   create mode 100644 tests/ref/fate/mov-heic-demux-still-image-1-item
> >   create mode 100644 tests/ref/fate/mov-heic-demux-still-image-multiple-items
>
> This seems to have been forgotten, so I'll apply it soon.

Sorry that was my bad. Thanks for applying.

> _______________________________________________
> 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".



-- 
Vignesh
_______________________________________________
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".

  reply	other threads:[~2024-01-10 21:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 17:37 [FFmpeg-devel] [PATCH] " Vignesh Venkatasubramanian via ffmpeg-devel
2023-10-03 22:56 ` Vignesh Venkat via ffmpeg-devel
2023-10-04  0:29   ` Steven Liu
2023-10-04  1:31     ` Vittorio Giovara
2023-10-04  4:01       ` Vignesh Venkat via ffmpeg-devel
2023-10-04  4:40         ` Vittorio Giovara
2023-10-04 16:36           ` Vignesh Venkat via ffmpeg-devel
2023-10-04 16:40             ` [FFmpeg-devel] [PATCH v3] " Vignesh Venkatasubramanian via ffmpeg-devel
2023-10-05 17:36               ` Vittorio Giovara
2023-10-05 22:40                 ` Vignesh Venkat via ffmpeg-devel
2023-10-09 18:52                   ` Vignesh Venkat via ffmpeg-devel
2023-10-27 16:52                     ` Thilo Borgmann via ffmpeg-devel
2024-01-09 12:39               ` James Almer
2024-01-10 21:05                 ` Vignesh Venkat via ffmpeg-devel [this message]
2023-10-05 17:59             ` [FFmpeg-devel] [PATCH] " Andreas Rheinhardt
2023-10-05 22:32               ` Vignesh Venkat via ffmpeg-devel
2023-10-04  4:28     ` Vignesh Venkat via ffmpeg-devel
2023-10-04  2:35 ` Leo Izen
2023-10-04  4:19   ` Vignesh Venkat via ffmpeg-devel
2023-10-04  4:20     ` [FFmpeg-devel] [PATCH v2] " Vignesh Venkatasubramanian via ffmpeg-devel

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=CAOJaEPKirT89JdbfTAjOhwxZ5JqOCwsjXBdeJUELMx9MLEmUnw@mail.gmail.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=vigneshv@google.com \
    /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