From: Lynne via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: Paul B Mahol <onemda@gmail.com>,
FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>
Cc: Lynne <dev@lynne.ee>
Subject: Re: [FFmpeg-devel] [PATCH] fate: add tests for xHE-AAC
Date: Tue, 21 May 2024 10:18:21 +0200
Message-ID: <01534eb3-70c9-4576-93cd-4623925b3799@lynne.ee> (raw)
In-Reply-To: <CAPYw7P4aiUs4On4B_pc0+GwawQbejJWx_oA=4G0_H=QV6iYnaA@mail.gmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 2424 bytes --]
On 21/05/2024 09:18, Paul B Mahol wrote:
>
>
> On Tue, May 21, 2024 at 4:05 AM Lynne via ffmpeg-devel
> <ffmpeg-devel@ffmpeg.org <mailto:ffmpeg-devel@ffmpeg.org>> wrote:
>
> Starting off small with a few features.
> Samples and reference decoded files copied from the official ISO
> reference suite.
>
>
> Sorry for my ignorance, but is such copy allowed from them?
>
> ---
> Samples and references: https://files.lynne.ee/xhe_refs/
> <https://files.lynne.ee/xhe_refs/>
>
> tests/fate/aac.mak | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/tests/fate/aac.mak b/tests/fate/aac.mak
> index 817944773d..ff58392ad9 100644
> --- a/tests/fate/aac.mak
> +++ b/tests/fate/aac.mak
> @@ -62,6 +62,14 @@ FATE_AAC += fate-aac-ap05_48
> fate-aac-ap05_48: CMD = pcm -i $(TARGET_SAMPLES)/aac/ap05_48.mp4
> fate-aac-ap05_48: REF = $(SAMPLES)/aac/ap05_48.s16
>
> +FATE_AAC += fate-aac-fd_2_c1_ms_0x01
> +fate-aac-fd_2_c1_ms_0x01: CMD = pcm -i
> $(TARGET_SAMPLES)/aac/Fd_2_c1_Ms_0x01.mp4
> +fate-aac-fd_2_c1_ms_0x01: REF = $(SAMPLES)/aac/Fd_2_c1_Ms_0x01.s16
> +
> +FATE_AAC += fate-aac-fd_2_c1_ms_0x04
> +fate-aac-fd_2_c1_ms_0x04: CMD = pcm -i
> $(TARGET_SAMPLES)/aac/Fd_2_c1_Ms_0x04.mp4
> +fate-aac-fd_2_c1_ms_0x04: REF = $(SAMPLES)/aac/Fd_2_c1_Ms_0x04.s16
> +
> FATE_AAC += fate-aac-er_ad6000np_44_ep0
> fate-aac-er_ad6000np_44_ep0: CMD = pcm -i
> $(TARGET_SAMPLES)/aac/er_ad6000np_44_ep0.mp4
> fate-aac-er_ad6000np_44_ep0: REF = $(SAMPLES)/aac/er_ad6000np_44.s16
> --
> 2.43.0.381.gb435a96ce8
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org <mailto:ffmpeg-devel@ffmpeg.org>
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org
> <mailto:ffmpeg-devel-request@ffmpeg.org> with subject "unsubscribe".
>
We have code from very big movie productions that people still buy BDs
of and go to the cinema, and you're worried about the ISO noticing that
we're hosting a small set of samples (which anyone can download) to test
machines?
https://standards.iso.org/iso-iec/23003/-3/ed-2/en/
[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 637 bytes --]
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2024-05-21 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 2:05 Lynne via ffmpeg-devel
2024-05-21 7:18 ` Paul B Mahol
2024-05-21 8:18 ` Lynne via ffmpeg-devel [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=01534eb3-70c9-4576-93cd-4623925b3799@lynne.ee \
--to=ffmpeg-devel@ffmpeg.org \
--cc=dev@lynne.ee \
--cc=onemda@gmail.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