From: Nicolas Gaullier via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Nicolas Gaullier <nicolas.gaullier@cji.paris>
Subject: [FFmpeg-devel] Re: [PATCH] av1_in_ts_v2 (PR #21307)
Date: Fri, 9 Jan 2026 11:32:02 +0100
Message-ID: <b90f219b-3072-4a85-a413-153adbf6379e@cji.paris> (raw)
In-Reply-To: <CAPYFPM2_L7cbCNJ4rxb1nRoZoC8gVwy9ztcE5NC=1jP=3Ar6ZA@mail.gmail.com>
On 1/8/26 08:32, Christophe Gisquet via ffmpeg-devel wrote:
> Le jeu. 8 janv. 2026, 02:24, mypopy--- via ffmpeg-devel <
> ffmpeg-devel@ffmpeg.org> a écrit :
>> As James Almer pointed out in his response, the current merge request
>> has already removed the muxer component, so there won't be any
>> compatibility issues, even if the specification is still in draft
>> status.
>>
>> AV1 in TS is already being utilized in certain scenarios, and we also
>> need an implementation to validate this specification concurrently
> Well, I don't particularly like that argument (flv extension again by some
> operator?), but this is beside the point.
I also don't particularly like that argument, but what I do not
understand is why we cannot get a public sample for sharing ?
It seems to me this demuxer-case should require FF_COMPLIANCE_EXPERIMENTAL.
Nicolas
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2026-01-09 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-28 18:45 [FFmpeg-devel] " Jun Zhao via ffmpeg-devel
2026-01-07 13:25 ` [FFmpeg-devel] " Christophe Gisquet via ffmpeg-devel
2026-01-07 23:30 ` James Almer via ffmpeg-devel
2026-01-08 1:23 ` mypopy--- via ffmpeg-devel
2026-01-08 7:32 ` Christophe Gisquet via ffmpeg-devel
2026-01-08 8:25 ` mypopy--- via ffmpeg-devel
2026-01-09 10:32 ` Nicolas Gaullier via ffmpeg-devel [this message]
2026-01-09 10:41 ` mypopy--- via ffmpeg-devel
2026-01-09 15:42 ` James Almer via ffmpeg-devel
2026-01-09 17:19 ` Nicolas Gaullier via ffmpeg-devel
2026-01-10 2:28 ` mypopy--- via ffmpeg-devel
2026-01-10 9:45 ` mypopy--- 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=b90f219b-3072-4a85-a413-153adbf6379e@cji.paris \
--to=ffmpeg-devel@ffmpeg.org \
--cc=nicolas.gaullier@cji.paris \
/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