From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] fate/cbs: Add tests for h264_redundant_pps BSF
Date: Tue, 20 Sep 2022 18:48:05 +0200
Message-ID: <GV1P250MB0737733CD80AE991FEBD5FD78F4C9@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <GV1P250MB073745D88F9E6ECAB8431F8C8F4C9@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
Andreas Rheinhardt:
> This also tests writing slice data in the unaligned mode
> (some of these files use CAVLC) as well as updating
> side data as well as parsing ISOBMFF avcc extradata.
>
> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
> ---
> tests/fate/cbs.mak | 43 ++-
> tests/ref/fate/h264_redundant_pps-annexb | 307 +++++++++++++++++++
> tests/ref/fate/h264_redundant_pps-mov | 115 +++++++
> tests/ref/fate/h264_redundant_pps-side_data | 21 ++
> tests/ref/fate/h264_redundant_pps-side_data2 | 11 +
> 5 files changed, 494 insertions(+), 3 deletions(-)
> create mode 100644 tests/ref/fate/h264_redundant_pps-annexb
> create mode 100644 tests/ref/fate/h264_redundant_pps-mov
> create mode 100644 tests/ref/fate/h264_redundant_pps-side_data
> create mode 100644 tests/ref/fate/h264_redundant_pps-side_data2
>
Forget about this patch, I forgot to send commits that this is based
upon. The real patchset is here:
https://ffmpeg.org/pipermail/ffmpeg-devel/2022-September/301762.html
- Andreas
_______________________________________________
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-09-20 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 16:30 Andreas Rheinhardt
2022-09-20 16:48 ` Andreas Rheinhardt [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=GV1P250MB0737733CD80AE991FEBD5FD78F4C9@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM \
--to=andreas.rheinhardt@outlook.com \
--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