Opened 11 years ago
Closed 11 years ago
#2503 closed defect (needs_more_info)
ffmpeg seek function seems to have lost frame accuracy on latest git
Reported by: | derick | Owned by: | |
---|---|---|---|
Priority: | important | Component: | undetermined |
Version: | unspecified | Keywords: | seek regression |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
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.
Change History (2)
comment:1 by , 11 years ago
Component: | FFmpeg → undetermined |
---|---|
Keywords: | seek added; seeking frame by frame accuracy removed |
Version: | 0.11.3 → unspecified |
comment:2 by , 11 years ago
Keywords: | regression added |
---|---|
Resolution: | → needs_more_info |
Status: | new → closed |
Please reopen this ticket if you can add the missing information.
Note:
See TracTickets
for help on using tickets.
As-is, this does not look like a useful bug report.
Did the output file change between an older and newer version of FFmpeg? Or are you just unhappy about the console output (one frame lasts for 0.04 seconds assuming a default "frame rate" of 25)?
In any case, please provide your command line together with the complete, uncut console output to make this a valid ticket.