From: Vignesh Venkatasubramanian <vigneshv-at-google.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avformat/mov: Only read the primary item for AVIF Date: Tue, 28 Jun 2022 11:58:00 -0700 Message-ID: <CAOJaEPJc40G7r_Pr2qns901+Vwqa4g9aiUsGu75-BEQvD9jGGQ@mail.gmail.com> (raw) In-Reply-To: <CABWgkXKnNKSx8upKofwkGu9ugfLt+ym0qM_uHXUB_9aM05yguQ@mail.gmail.com> On Tue, Jun 28, 2022 at 11:21 AM James Zern <jzern-at-google.com@ffmpeg.org> wrote: > > On Mon, Jun 13, 2022 at 9:32 AM Vignesh Venkatasubramanian > <vigneshv-at-google.com@ffmpeg.org> wrote: > > > > On Fri, Jun 10, 2022 at 10:34 AM Vignesh Venkatasubramanian > > <vigneshv@google.com> wrote: > > > > > > On Thu, Jun 9, 2022 at 12:50 AM Gyan Doshi <ffmpeg@gyani.pro> wrote: > > > > > > > > > > > > > > > > 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 > > > > > > > > > > Thank you i have added a couple of fate tests. > > > > > > I am not sure how to add the AVIF files to the fate test server. I > > > have them on Google Drive here: > > > > > > https://drive.google.com/file/d/1diZoM0Ew7Co3Yh5w5y1J-3IiBYVmUv9J/view?usp=sharing > > > https://drive.google.com/file/d/1DdrD1mW36evt40a4RkeLYpx-oojmbc3z/view?usp=sharing > > > > > > These links should be publicly available without any sign in required. > > > Please let me know if there is another preferred way of sharing test > > > files and i can share it that way. > > > > > > > Also, i forgot to mention that these files have to be uploaded under a > > new directory called "avif" in the fate server. > > > > Can you send a separate patch with the tests disabled and marked by a > TODO to enable them after the files are uploaded? > https://ffmpeg.org/developer.html#Adding-files-to-the-fate_002dsuite-dataset I have updated this patch to comment out the actual tests (with a FIXME note). I can send separate patch once the files are added to the server to uncomment the tests and remove the FIXME. > _______________________________________________ > 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".
prev parent reply other threads:[~2022-06-28 18:58 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 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 [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=CAOJaEPJc40G7r_Pr2qns901+Vwqa4g9aiUsGu75-BEQvD9jGGQ@mail.gmail.com \ --to=vigneshv-at-google.com@ffmpeg.org \ --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