[FFmpeg-trac] #2503(FFmpeg:new): ffmpeg seek function seems to have lost frame accuracy on latest git
FFmpeg
trac at avcodec.org
Thu Apr 25 17:59:56 CEST 2013
#2503: ffmpeg seek function seems to have lost frame accuracy on latest git
-------------------------------------+-------------------------------------
Reporter: derick | Type: defect
Status: new | Priority: important
Component: FFmpeg | Version: 0.11.3
Keywords: seeking | Blocked By:
frame by frame accuracy | Reproduced by developer: 0
Blocking: |
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Summary of the bug:
{{{
How to reproduce: I utilize ffmpeg combined Fast+accurate frame seek (as
seen on ffmpeg Seeking tutorial to grab a frame of film.
http://ffmpeg.org/trac/ffmpeg/wiki/Seeking%20with%20FFmpeg
Up to last git update I had performed (April 4th)
ffmpeg output showed 00:00:00:01 at end of log, now it shows 00:00:00.04:
"frame= 1 fps=0.0 q=0.0 Lsize=N/A time=00:00:00.04 bitrate=N/A"
I don't seem to be skipping frame by frame like I was able to do in the
past.
This is the command I use:
ffmpeg -y -ss 036.311 -i /media/film.MP4 -vframes 1 -ss 01.0 out.jpg
built on April 25th,2013
}}}
Patches should be submitted to the ffmpeg-devel mailing list and not this
bug tracker.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2503>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list