From: James Almer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: James Almer <jamrial@gmail.com>
Subject: [FFmpeg-devel] Re: [PATCH] av1_in_ts_v2 (PR #21307)
Date: Mon, 12 Jan 2026 18:05:13 -0300
Message-ID: <65245d69-f709-4ef7-a233-4a634e0cbf07@gmail.com> (raw)
In-Reply-To: <4eb79192-fd47-42a3-85fd-2995c4904d62@cji.paris>
[-- Attachment #1.1.1: Type: text/plain, Size: 2280 bytes --]
On 1/12/2026 1:31 PM, Nicolas Gaullier via ffmpeg-devel wrote:
> On 12/28/25 19:45, Jun Zhao via ffmpeg-devel wrote:
>> PR #21307 opened by Jun Zhao (mypopydev)
>> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21307
>> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21307.patch
>>
>> Add functions to parse AV1 OBUs in MPEG-TS start code format
>> (0x000001 prefix). This is needed for AV1 streams from MPEG-TS
>> containers per AOM AV1 in MPEG-2 TS specification.
>
> I have some questions around aligned PES and start codes; please correct
> me if I am wrong.
>
> Start codes: it seems to me current PR autodetects start codes, which
> means if a stream miss them, it would still be successfully decoded.
> This is possible because, additionally, AV1 requires aligned PES (which
Where does the spec say that?
> is unusual for h2645 typically). Being able to handle non-conformant
> files is nice until there are no downsides. The situation is maybe a
> little bit tricky here since this format is not widespread, you may want
> to be more carefull, check interoperability etc., and maybe you want to
> be warned that "this file may not be supported outside of ffmpeg" ? It
Why would we warn that? Demuxing has no need for any kind of warning
like that. We're reading a file and trying to make sense of its
contents. What other readers can or can't do is irrelevant.
> seems there is no "issue" in the other way (a stream which is not pes-
> aligned would not be decodable since there is no "find_frame_end" in the
> parser to split the packets), but anyway maybe it could be
I already wrote an implementation for Temporal Unit assembly in
av1_parser, but I'm waiting until all is said and done, and probably an
actual sample is provided.
> an interesting opportunity to introduce pes alignment support in
> mpegts ? If I understand correctly, it would allow disabling packet
> repacking in some use cases (j2k for example: I just had a quick look
> today since mpegts mandates pes alignment for it too).
>
> Nicolas
>
> _______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
[-- Attachment #2: 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
prev parent reply other threads:[~2026-01-12 21:06 UTC|newest]
Thread overview: 14+ 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
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
2026-01-12 16:31 ` [FFmpeg-devel] " Nicolas Gaullier via ffmpeg-devel
2026-01-12 21:05 ` James Almer via ffmpeg-devel [this message]
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=65245d69-f709-4ef7-a233-4a634e0cbf07@gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=jamrial@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