From: Kieran Kunhya <kierank@obe.tv>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 0/1] avformat/mpegts: fix first NAL start code splited in two different packets
Date: Tue, 6 Feb 2024 11:28:38 +0000
Message-ID: <CAK+ULv6EmqDPsCNpopUaEgXWz1mS1MKu7mW2J4BbFwxnPvUvOg@mail.gmail.com> (raw)
In-Reply-To: <MR1P264MB2483C01B792974CB01CEAB9A9B462@MR1P264MB2483.FRAP264.PROD.OUTLOOK.COM>
On Tue, 6 Feb 2024 at 10:58, Nicolas Gaullier <nicolas.gaullier@cji.paris>
wrote:
> >Envoyé : vendredi 2 février 2024 16:24
> >À : ffmpeg-devel@ffmpeg.org
> >Objet : [PATCH 0/1] avformat/mpegts: fix first NAL start code splited in
> two different packets
> >
> >This issue happens in the following case:
> >- unaligned PES and NAL encoding
> >- the first NAL of the access unit begins at the very end of a ts packet,
> sometimes only the 0x00 of the trailing byte (unfortunately, this is still
> conformant to the standards!)
> >- the video frame is so small (ex: typically still picture) it fits in a
> ts packet and a new PES is immediately started
> >
> >Two sample files can be found here:
> >a) https://0x0.st/HDwD.ts
> >b) https://0x0.st/HDwd.ts
> >
> >For sample a, the first NAL (AUD) is splited this way:
> >0x00 / 0x00 0x00 0x01 0x09
> >And for sample b:
> >0x00 0x00 0x00 / 0x01 0x09
> >
> >ffmpeg -i input.ts -f null /dev/null
> >=> Application provided invalid, non monotonically increasing dts...
> >
> >
> >Nicolas Gaullier (1):
> > avformat/mpegts: fix first NAL start code splited in two different
> > packets
> >
> > libavformat/mpegts.c | 41 +++++++++++++++++++++++++++++++++++++++--
> > 1 file changed, 39 insertions(+), 2 deletions(-)
>
> Ping ?
> If you think it would be better to have a related trac ticket, just tell
> me, I can do this of course.
> Nicolas
>
I think it's ok. I wish it were less ugly but I guess it can't be.
Kieran
_______________________________________________
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-02-06 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 15:23 Nicolas Gaullier
2024-02-02 15:23 ` [FFmpeg-devel] [PATCH] " Nicolas Gaullier
2024-02-06 10:58 ` [FFmpeg-devel] [PATCH 0/1] " Nicolas Gaullier
2024-02-06 11:28 ` Kieran Kunhya [this message]
2024-02-06 11:38 ` Nicolas Gaullier
2024-02-06 12:15 ` Kieran Kunhya
2024-02-06 21:36 ` Marton Balint
2024-02-20 16:58 ` Nicolas Gaullier
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=CAK+ULv6EmqDPsCNpopUaEgXWz1mS1MKu7mW2J4BbFwxnPvUvOg@mail.gmail.com \
--to=kierank@obe.tv \
--cc=ffmpeg-devel@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