From: Christophe Gisquet via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: mypopy@gmail.com, Christophe Gisquet <christophe.gisquet@gmail.com>
Subject: [FFmpeg-devel] Re: [PATCH] av1_in_ts_v2 (PR #21307)
Date: Thu, 8 Jan 2026 08:32:17 +0100
Message-ID: <CAPYFPM2_L7cbCNJ4rxb1nRoZoC8gVwy9ztcE5NC=1jP=3Ar6ZA@mail.gmail.com> (raw)
In-Reply-To: <CACYjbn21h1EeAAx7bWRPAOiTGjGCvY3E4V5GMXL+dhkHsARi1g@mail.gmail.com>
Hi,
Le jeu. 8 janv. 2026, 02:24, mypopy--- via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> a écrit :
> On Wed, Jan 7, 2026 at 9:26 PM
> > Mostly my 2 cents,
> > Regards,
> > Christophe
>
> My perspective is as follows:
>
> 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.
>
Ok. Sorry, I'm looking through a phone and just took the first hit for this
topic.
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.
My comment was not a NACK, but a call to caution and informed decision. If
several people are taking that decision and judging the consequences can be
handled, good.
Regards
>
_______________________________________________
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-08 7:33 UTC|newest]
Thread overview: 6+ 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 [this message]
2026-01-08 8:25 ` 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='CAPYFPM2_L7cbCNJ4rxb1nRoZoC8gVwy9ztcE5NC=1jP=3Ar6ZA@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=christophe.gisquet@gmail.com \
--cc=mypopy@gmail.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