Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mxfdec: support MCA audio information
Date: Sun, 2 Jan 2022 02:35:25 +0100
Message-ID: <AM7PR03MB6660B2126455ECA06119438D8F489@AM7PR03MB6660.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <CAF_7JxCk5Zw2rJvStcXq+LjLQJ+XJ89JnFQVSWSCE3+2aSWyOg@mail.gmail.com>

Pierre-Anthony Lemieux:
> Minor suggestion below.
> 
> In addition, will sample file(s) be added to FATE? Below are two examples:
> 
> http://ffmpeg-imf-samples-public.s3.us-west-1.amazonaws.com/callout_51_l_r_c_lfe_ls_rs.mxf
> http://ffmpeg-imf-samples-public.s3.us-west-1.amazonaws.com/callout_51_l_c_r_ls_rs_lfe.mxf
> 

These files are 1.62MiB each, having 49 packets of lossless audio. Would
it decrease coverage if this were reduced? After all, the amount of
audio should not matter for channel reorderings.

- 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".

  parent reply	other threads:[~2022-01-02  1:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01 19:26 Marton Balint
2022-01-01 23:13 ` Pierre-Anthony Lemieux
2022-01-02  1:11   ` Marton Balint
2022-01-02  2:16     ` Pierre-Anthony Lemieux
2022-01-02 10:26       ` Marton Balint
2022-01-08 18:48         ` Marton Balint
2022-01-02 17:35     ` Michael Niedermayer
2022-01-02  1:35   ` Andreas Rheinhardt [this message]
2022-01-02  1:54     ` Pierre-Anthony Lemieux
2022-01-02 10:33       ` Marton Balint
2022-01-03  7:12       ` Andreas Rheinhardt
2022-01-04  4:38         ` Pierre-Anthony Lemieux

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=AM7PR03MB6660B2126455ECA06119438D8F489@AM7PR03MB6660.eurprd03.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