From: Nicolas Gaullier <nicolas.gaullier@cji.paris>
To: ffmpeg-devel@ffmpeg.org
Cc: Nicolas Gaullier <nicolas.gaullier@cji.paris>
Subject: [FFmpeg-devel] [PATCH 0/1] avformat/demux: Fix accurate probing of durations in mpegts/ps
Date: Thu, 14 Mar 2024 18:57:38 +0100
Message-ID: <20240314175739.1499196-1-nicolas.gaullier@cji.paris> (raw)
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"
Nicolas Gaullier (1):
avformat/demux: Fix accurate probing of durations in mpegts/ps
libavformat/demux.c | 30 +---
tests/ref/fate/concat-demuxer-simple2-lavf-ts | 170 +++++++++---------
tests/ref/fate/ts-opus-demux | 4 +-
3 files changed, 93 insertions(+), 111 deletions(-)
--
2.30.2
_______________________________________________
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 reply other threads:[~2024-03-14 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 17:57 Nicolas Gaullier [this message]
2024-03-14 17:57 ` [FFmpeg-devel] [PATCH 1/1] " Nicolas Gaullier
2024-03-14 22:41 ` Michael Niedermayer
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=20240314175739.1499196-1-nicolas.gaullier@cji.paris \
--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