Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Dai, Jianhui J" <jianhui.j.dai-at-intel.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v6] avcodec/cbs_vp8: Add support for VP8 codec bitstream
Date: Mon, 20 Nov 2023 04:36:55 +0000
Message-ID: <DM6PR11MB26818E50DADE8FBA1AB3EECEB1B4A@DM6PR11MB2681.namprd11.prod.outlook.com> (raw)
In-Reply-To: <49c154cd-4fee-4ce7-86eb-cea7db959b02@gmail.com>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> James Almer
> Sent: Thursday, November 16, 2023 9:30 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v6] avcodec/cbs_vp8: Add support for
> VP8 codec bitstream
> 
> On 11/15/2023 3:47 PM, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Sun, Nov 12, 2023 at 8:53 PM Dai, Jianhui J <
> > jianhui.j.dai-at-intel.com@ffmpeg.org> wrote:
> >
> >> TESTS: ffmpeg -i fate-suite/vp8/frame_size_change.webm -vcodec copy
> >> -bsf:v trace_headers -f null -
> >>
> >
> > (I've merged this already.)
> >
> > I don't think a fate test was added to prevent regressions. Would that
> > be useful? (I didn't see one for the other trace_headers like vp9 or
> > av1, so it's possible the answer is "no".)
> >
> > Ronald
> 
> trace_headers bsf doesn't have tests. What's used to test CBS
> implementations in general is a *_metadata bsf.

Thanks.
I will add the WRITE methods into cbs_vp8, and implement the vp8_metadata_bsf for FATE as the next step.

> _______________________________________________
> 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".
_______________________________________________
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:[~2023-11-20  4:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13  1:53 Dai, Jianhui J
2023-11-15 18:47 ` Ronald S. Bultje
2023-11-16 13:24   ` Dai, Jianhui J
2023-11-16 13:29   ` James Almer
2023-11-20  4:36     ` Dai, Jianhui J [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=DM6PR11MB26818E50DADE8FBA1AB3EECEB1B4A@DM6PR11MB2681.namprd11.prod.outlook.com \
    --to=jianhui.j.dai-at-intel.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