Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas Gaullier <nicolas.gaullier@cji.paris>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3 0/1] avformat/demux: fix accurate probing of durations in mpegts/ps
Date: Mon, 22 Apr 2024 12:32:13 +0000
Message-ID: <MR1P264MB2483FB88A0FA49A9004F7F179B122@MR1P264MB2483.FRAP264.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20240402212609.572420-1-nicolas.gaullier@cji.paris>

>De : Nicolas Gaullier <nicolas.gaullier@cji.paris> 
>Envoyé : mardi 2 avril 2024 23:26
>Objet : [PATCH v3 0/1] avformat/demux: fix accurate probing of durations in mpegts/ps
>
>v3: rebased after ed9363052f4b8b8 applied tonight (add duration_probesize AVOption)
>
>Note: I have no other plan for demux/probing; with these two patches, I can cover my use cases, especially mpegts-concats.
>
>For remembering, previous cover-letters:
>
>v1--------------------
>ff_read_packet() is more lightweight, but it leads to important issues when looking for accurate durations.
>As a side effect, the code looks also simpler with regular av_read_frame() calls.
>1)Updates in the fate tests do exhibit most of the results.
>
>2)See also more directly the case of an audio PES containing many frames:
>>ffprobe tests/data/lavf/lavf.ts -select_streams a -show_entries 
>>stream=duration -of flat
>Before patch:
>  streams.stream.0.duration="0.757556"
>After patch:
>  streams.stream.0.duration="1.018778"
>
>3)Here is an additional (commonplace) sample to demonstrate the benefit for twofields-encoded video:
>>https://0x0.st/HFbm.ts (say h264-50i_mp2.ts)
>
>>ffprobe h264-50i_mp2.ts -show_entries stream=duration -of flat
>Before patch:
>  streams.stream.0.duration="2.060000"
>  streams.stream.1.duration="1.176000"
>After patch:
>  streams.stream.0.duration="2.080000"
>  streams.stream.1.duration="1.200000"
>
>
>v2--------------------
>v1: There was an issue with teletext where resolution is set just once at decoder init (teletext resolution is fixed/hard coded), so it is somewhat fragile: when a demuxer context update occurs, it is lost/overriden by >avcodec_parameters_to_context(sti->avctx, st->codecpar) in read_frame_internal.
>They could have been other scenario besides teletext, I don't know.
>v2: So now at estimate_timings_from_pts, with one or more seeking involved (seeking is detected by the mpegts demuxer and set last_vn=-1, so pmt is forced/updated and results in demuxer context update), it is required to >preserve the info in codecpar at first.
>Thanks to Michael for reporting the issue.
>
>
>Nicolas Gaullier (1):
>  avformat/demux: Fix accurate probing of durations in mpegts/ps
>
> libavformat/demux.c                           |  36 ++--
> tests/ref/fate/concat-demuxer-simple2-lavf-ts | 170 +++++++++---------
> tests/ref/fate/ts-opus-demux                  |   4 +-
> 3 files changed, 100 insertions(+), 110 deletions(-)

Ping for review ?
The patch (https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=11386) still applies on current master.
Thanks.

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

  parent reply	other threads:[~2024-04-22 12:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 21:26 Nicolas Gaullier
2024-04-02 21:26 ` [FFmpeg-devel] [PATCH v3] " Nicolas Gaullier
2024-04-22 12:32 ` Nicolas Gaullier [this message]
2024-04-29 17:35   ` [FFmpeg-devel] [PATCH v3 0/1] " Nicolas Gaullier
2024-05-24 14:16     ` 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=MR1P264MB2483FB88A0FA49A9004F7F179B122@MR1P264MB2483.FRAP264.PROD.OUTLOOK.COM \
    --to=nicolas.gaullier@cji.paris \
    --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