Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Andriy Gelman <andriy.gelman@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH v2 1/5] avcodec/parser: merge packets from the same frame
Date: Tue, 5 Mar 2024 21:51:56 +0100
Message-ID: <20240305205156.GB6420@pb2> (raw)
In-Reply-To: <MR1P264MB248371344369AD1227A37CB99B232@MR1P264MB2483.FRAP264.PROD.OUTLOOK.COM>


[-- Attachment #1.1: Type: text/plain, Size: 1741 bytes --]

Hi

On Mon, Mar 04, 2024 at 05:38:48PM +0000, Nicolas Gaullier wrote:
> >De : ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> De la part de Michael Niedermayer
> >Envoyé : dimanche 3 mars 2024 23:07
> >À : FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> >Objet : Re: [FFmpeg-devel] [PATCH v2 1/5] avcodec/parser: merge packets from the same frame
> >
> >On Fri, Mar 01, 2024 at 02:39:19PM +0100, Nicolas Gaullier wrote:
> >> The mpegts demuxer splits packets according to its max_packet_size.
> >> This currently fills the AVCodecParserContext s->cur_frame_* arrays 
> >> with kind of 'empty' entries: no pts/dts.
> >> This patch merges these entries, so the parser behaviour is 
> >> independent from the demuxer settings.
> >> This patch is required for the following patch which will fetch 'past'
> >> timestamps from past cur_frames.
> >> 
> >> Signed-off-by: Nicolas Gaullier <nicolas.gaullier@cji.paris>
> >> ---
> >>  libavcodec/parser.c | 4 ++++
> >>  1 file changed, 4 insertions(+)
> >
> >Breaks fate-seek-lavf-as
> 
> Really sorry about that, I was not aware that assert-level=2 had to be enabled to get full fate tests.
> Maybe this should be documented in the fate.texi.

patch welcome


> I also checked the green light on patchwork... It seems at least assert-level=1 is not supposed to consume too much cpu, so maybe it could be enabled for patchwork?

CCing Andriy


thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

If you fake or manipulate statistics in a paper in physics you will never
get a job again.
If you fake or manipulate statistics in a paper in medicin you will get
a job for life at the pharma industry.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  reply	other threads:[~2024-03-05 20:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 13:39 [FFmpeg-devel] [PATCH v2 0/5] avcodec/parser: fix fetch_timestamp in a scenario with unaligned packets Nicolas Gaullier
2024-03-01 13:39 ` [FFmpeg-devel] [PATCH v2 1/5] avcodec/parser: merge packets from the same frame Nicolas Gaullier
2024-03-03 22:06   ` Michael Niedermayer
2024-03-04 17:38     ` Nicolas Gaullier
2024-03-05 20:51       ` Michael Niedermayer [this message]
2024-03-01 13:39 ` [FFmpeg-devel] [PATCH v2 2/5] avcodec/parser: reindent after previous commit Nicolas Gaullier
2024-03-01 13:39 ` [FFmpeg-devel] [PATCH v2 3/5] avcodec/parser: fix fetch_timestamp in a scenario with unaligned packets Nicolas Gaullier
2024-03-01 13:39 ` [FFmpeg-devel] [PATCH v2 4/5] avcodec/h264_parser: fix start of packet for some broken streams Nicolas Gaullier
2024-03-01 13:39 ` [FFmpeg-devel] [PATCH v2 5/5] lavf/demux: duplicate side_data in parse_packet() Nicolas Gaullier
2024-03-01 13:49   ` James Almer
2024-03-01 13:54     ` James Almer

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=20240305205156.GB6420@pb2 \
    --to=michael@niedermayer.cc \
    --cc=andriy.gelman@gmail.com \
    --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