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 12:15:40 +0000
Message-ID: <CAK+ULv7FsXcb1N-7+NfMfQVrRRZZ4DDkPfPohs7Ji3RHc+_Bzw@mail.gmail.com> (raw)
In-Reply-To: <MR1P264MB24830807E7E47790AF9053B09B462@MR1P264MB2483.FRAP264.PROD.OUTLOOK.COM>
On Tue, 6 Feb 2024 at 11:39, Nicolas Gaullier <nicolas.gaullier@cji.paris>
wrote:
> >> 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
>
> Yes, of course! I am really really sorry.
> Personally, I have not found a better solution as an mpegts fix, but if
> anyone has a better code, of course my version can be dropped.
> (I have not looked for a possible fix in the upper ffmpeg demux/parser
> layers, but it would be certainly even more ugly, if possible at all).
>
> Again, sorry. There are some implementers who take the standards very
> crude to "optimize" for every little byte unreasonably.
> Fact is, here, the standard should not have allowed this!
> Nicolas
>
Yes, I know exactly who is creating these files.
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 12:16 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
2024-02-06 11:38 ` Nicolas Gaullier
2024-02-06 12:15 ` Kieran Kunhya [this message]
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+ULv7FsXcb1N-7+NfMfQVrRRZZ4DDkPfPohs7Ji3RHc+_Bzw@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