Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mov: Only read the primary item for AVIF
Date: Thu, 9 Jun 2022 13:20:25 +0530
Message-ID: <085f0277-e678-4d20-f2bf-fbf55ed959d8@gyani.pro> (raw)
In-Reply-To: <CAOJaEPJwWmEzzOETDL-jWHD+XzdSmwAprviVeY6L6sNtpQA22A@mail.gmail.com>



On 2022-06-08 10:51 pm, Vignesh Venkatasubramanian wrote:
> On Thu, Jun 2, 2022 at 1:35 PM James Zern <jzern@google.com> wrote:
>> On Wed, Jun 1, 2022 at 1:38 PM Vignesh Venkatasubramanian
>> <vigneshv@google.com> wrote:
>>> On Wed, Jun 1, 2022 at 10:30 AM James Zern <jzern@google.com> wrote:
>>>> On Sun, Apr 24, 2022 at 11:35 AM Vignesh Venkatasubramanian
>>>> <vigneshv-at-google.com@ffmpeg.org> wrote:
>>>>> Update the still AVIF parser to only read the primary item. With this
>>>>> patch, AVIF still images with exif/icc/alpha channel will no longer
>>>>> fail to parse.
>>>>>
>>>>> For example, this patch enables parsing of files in:
>>>>> https://github.com/AOMediaCodec/av1-avif/tree/master/testFiles/Microsoft
>>>>>
>>>> Can some of the failing files or similar ones be added to fate?
>>> There are no fate tests for AVIF parsing as of now. I was thinking
>>> about adding some for the muxing. But i am not sure what can be done
>>> here for the parsing.
>>>
>> Thanks. Are there any for general mov/mp4 parsing that could be
>> extended? This looks good otherwise.
>  From what i see, most of the mov tests only seem to be for muxing. I'm
> not entirely certain about how to add a test for AVIF parsing. If
> anybody has an idea, i'd be open to adding it.

Basic test would use the framemd5 muxer to compare demuxed packets with 
a reference.
See fate-ffmpeg-streamloop

Regards,
Gyan
_______________________________________________
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:[~2022-06-09  7:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-24 18:35 Vignesh Venkatasubramanian
2022-05-02 21:39 ` Vignesh Venkatasubramanian
2022-05-09 16:32   ` Vignesh Venkatasubramanian
2022-05-16 16:59     ` Vignesh Venkatasubramanian
2022-05-19 16:13       ` Vignesh Venkatasubramanian
2022-05-31 19:11         ` Vignesh Venkatasubramanian
2022-06-01 17:30 ` James Zern
2022-06-01 20:38   ` Vignesh Venkatasubramanian
2022-06-02 20:34     ` James Zern
2022-06-08 17:21       ` Vignesh Venkatasubramanian
2022-06-09  7:50         ` Gyan Doshi [this message]
2022-06-10 17:30           ` Vignesh Venkatasubramanian
2022-06-10 17:33             ` Andreas Rheinhardt
2022-06-10 17:37               ` Vignesh Venkatasubramanian
2022-06-10 17:34           ` Vignesh Venkatasubramanian
2022-06-13 16:32             ` Vignesh Venkatasubramanian
2022-06-21 17:12               ` Vignesh Venkatasubramanian
2022-06-27 16:44                 ` Vignesh Venkatasubramanian
2022-06-28 18:21               ` James Zern
2022-06-28 18:56                 ` Vignesh Venkatasubramanian
2022-06-28 19:02                   ` James Zern
2022-06-29 19:20                     ` James Zern
2022-06-28 18:58                 ` Vignesh Venkatasubramanian

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=085f0277-e678-4d20-f2bf-fbf55ed959d8@gyani.pro \
    --to=ffmpeg@gyani.pro \
    --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