[FFmpeg-trac] #8657(ffprobe:new): read_intervals parameter in ffprobe skips comma separated intervals
FFmpeg
trac at avcodec.org
Wed May 6 18:32:14 EEST 2020
#8657: read_intervals parameter in ffprobe skips comma separated intervals
----------------------------------------+----------------------------------
Reporter: zeco | Type: defect
Status: new | Priority: normal
Component: ffprobe | Version: 4.2
Keywords: read_intervals | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
----------------------------------------+----------------------------------
Summary of the bug:
As of current versions (tested with ffmpeg 4.2.2), giving ffprobe a comma-
separated list of intervals using the -read_intervals parameter will only
yield results for the first given interval, while the rest of the list is
skipped.
In earlier versions (tested with 3.2.14) ffprobe -read_intervals did
process all the given intervals, conforming with the parameter's current
documentation.
I can try to pinpoint the first affected version between 3.2.14 and 4.2.2
closer if requested.
How to reproduce:
{{{
% ffmpeg-3.2.14/ffprobe -read_intervals 10%+#1,20%+#1,30%+#1 -show_entries
frame=pkt_pts_time -v error test.mp4
[FRAME]
pkt_pts_time=8.000000
[/FRAME]
[FRAME]
pkt_pts_time=20.000000
[/FRAME]
[FRAME]
pkt_pts_time=28.000000
[/FRAME]
% ffmpeg-4.2.2/ffprobe -read_intervals 10%+#1,20%+#1,30%+#1 -show_entries
frame=pkt_pts_time -v error test.mp4
[FRAME]
pkt_pts_time=8.000000
[/FRAME]
}}}
Built on intel + arm.
Specifying time codes as end positions instead of a packet count (+!#1)
has no effect on the issue either.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/8657>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list