Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] fate: use an even more exotic channel layout mov-mp4-pcm-float test
Date: Sun, 18 Feb 2024 15:41:18 -0300
Message-ID: <f07aec37-bc1c-49a1-8fed-e799d9feafd0@gmail.com> (raw)
In-Reply-To: <be5ff745-a396-edc3-c7e9-f151ac213cea@passwd.hu>

On 2/18/2024 3:38 PM, Marton Balint wrote:
> 
> 
> On Sun, 18 Feb 2024, James Almer wrote:
> 
>> On 2/18/2024 7:45 AM, Marton Balint wrote:
>>>  The old layout happened to be a native layout and therefore missed some
>>>  recently fixed layout parsing bugs.
>>>
>>>  Signed-off-by: Marton Balint <cus@passwd.hu>
>>>  ---
>>>    tests/fate/mov.mak               | 2 +-
>>>    tests/ref/fate/mov-mp4-pcm-float | 4 ++--
>>>    2 files changed, 3 insertions(+), 3 deletions(-)
>>>
>>>  diff --git a/tests/fate/mov.mak b/tests/fate/mov.mak
>>>  index 4850c8aa94..8d154c8b5b 100644
>>>  --- a/tests/fate/mov.mak
>>>  +++ b/tests/fate/mov.mak
>>>  @@ -187,7 +187,7 @@ fate-mov-mp4-pcm: CMD = transcode wav
>>>  $(TARGET_PATH)/tests/data/asynth-44100-1.w
>>>    FATE_MOV_FFMPEG-$(call TRANSCODE, PCM_S16LE, MOV, WAV_DEMUXER
>>>    PAN_FILTER) \
>>>                              += fate-mov-mp4-pcm-float
>>>    fate-mov-mp4-pcm-float: tests/data/asynth-44100-1.wav
>>>  -fate-mov-mp4-pcm-float: CMD = transcode wav
>>>  $(TARGET_PATH)/tests/data/asynth-44100-1.wav mp4 "-af
>>>  aresample,pan=FL+LFE+BR|c0=c0|c1=c0|c2=c0 -c:a pcm_f32le" "-map 0 -c 
>>> copy
>>>  -frames:a 0"
>>>  +fate-mov-mp4-pcm-float: CMD = transcode wav
>>>  $(TARGET_PATH)/tests/data/asynth-44100-1.wav mp4 "-af
>>>  aresample,pan=FR+FL+FR|c0=c0|c1=c0|c2=c0 -c:a pcm_f32le" "-map 0 -c 
>>> copy
>>>  -frames:a 0"
>>
>> Wouldn't FR+FL+LFE be enough to test this? While also generating a 
>> file that's realistic.
> 
> It depends on what you want to test. With the old code, for FR+FL+LFE,
> only the channel order would have been wrong, with FR+FL+FR also the 
> channel count.
> 
> Having the same channel position in the same track is not that 
> theoretical, at least for MOV I have samples where an additional FR/FL 
> track is used for Music/Effects. I admit, for MP4 that might be less 
> common though, and I also admit that using a separate track for it would 
> be better. But as we know, nothing is ideal in practice...
> 
> Nevertheless, I can change the test to FR+FL+LFE if that is preferred.

No, it's ok as is if it tests more things that can potentially regress.

> 
> Regards,
> Marton
> _______________________________________________
> 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:[~2024-02-18 18:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18 10:45 Marton Balint
2024-02-18 11:09 ` Zhao Zhili
2024-02-18 12:49 ` James Almer
2024-02-18 18:38   ` Marton Balint
2024-02-18 18:41     ` James Almer [this message]
2024-02-19 20:53       ` Marton Balint

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=f07aec37-bc1c-49a1-8fed-e799d9feafd0@gmail.com \
    --to=jamrial@gmail.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