From: Discord Account via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: samples-request@ffmpeg.org
Cc: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>,
Discord Account <cordacct2001@gmail.com>
Subject: [FFmpeg-devel] New Media File for FATE Suite
Date: Mon, 2 Feb 2026 17:35:42 +0530
Message-ID: <CAB7CwxtUYMmzcaDXPnS5b_ZLms3fi+ShQO-J6_Ez=rsW82O+8g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Hi,
I would like to submit a new sample media file for inclusion in the FATE
suite.
*File:*
-
dummy_multistream.mkv (105 KB)
*Proposed path:*
-
fate-suite/mkv/dummy_multistream.mkv
*Description:*
Dummy video file containing a test pattern, sine audio, and two French
subtitle streams. The sample is intended for regression testing subtitle
stream selection in FFmpeg.
This file is needed to test code addressing the following issue:
https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/20149
The code is ready, and the tests are implemented, but they currently fail
on CI because the existing FATE suite does not include a sample with
multiple subtitle streams.
Please let me know if any additional information is required.
The file is new and does not replace any existing samples.
Regards,
Practice2001
[-- Attachment #2: dummy_multistream.mkv --]
[-- Type: video/x-matroska, Size: 107294 bytes --]
[-- Attachment #3: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next reply other threads:[~2026-02-02 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 12:05 Discord Account via ffmpeg-devel [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-02 11:57 Makarand More via ffmpeg-devel
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='CAB7CwxtUYMmzcaDXPnS5b_ZLms3fi+ShQO-J6_Ez=rsW82O+8g@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=cordacct2001@gmail.com \
--cc=samples-request@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