From: asivery via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: asivery <asivery@protonmail.com>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avformat/aeadec, avcodec/atrac1: Fix 8 and 4-channel ATRAC1 support
Date: Wed, 03 Jul 2024 14:56:11 +0000
Message-ID: <5_LKileGYOO5ExfAWyW_9_90ZQ5CxiRWRPn3q3wo6tUkUVzN0cyxQCJ5Zy7j35PwZaxnbAZXeVrZ4bqvYj_TPMCeRiHPCXsd5n_p56bD1Po=@protonmail.com> (raw)
In-Reply-To: <GV1P250MB07379D5942424C4CEC87F4978FDD2@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
On Sat, 15 Jun 2024 I was asked for samples by Anton Khirnov - this is why I wrote the test.
If the test is not necessary after all, that patch doesn't need to be applied. I can also shorten the test file, if it's required.
On Wednesday, July 3rd, 2024 at 4:49 PM, Andreas Rheinhardt <andreas.rheinhardt@outlook.com> wrote:
> asivery via ffmpeg-devel:
>
> > I'm sending the patch again, so that it is correctly rebased on the current master.
> > Here are the two sample files required by the FATE test:
> > https://0x0.st/Xaw2.aea/boxboy333_house_music_multitrack.aea
> > https://0x0.st/Xaw_.pcm/boxboy333_house_music_multitrack.pcm
> > Please let me know if I need to provide anything else.
>
>
> Why such a gigantic file? And why actually a multi-channel file given
> that there are no special coding modes for multi-channel files?
>
> - 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".
_______________________________________________
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".
next prev parent reply other threads:[~2024-07-03 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 14:34 asivery via ffmpeg-devel
2024-07-03 14:49 ` Andreas Rheinhardt
2024-07-03 14:56 ` asivery via ffmpeg-devel [this message]
2024-07-05 11:08 ` Anton Khirnov
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='5_LKileGYOO5ExfAWyW_9_90ZQ5CxiRWRPn3q3wo6tUkUVzN0cyxQCJ5Zy7j35PwZaxnbAZXeVrZ4bqvYj_TPMCeRiHPCXsd5n_p56bD1Po=@protonmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=asivery@protonmail.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