[FFmpeg-trac] #17(FFmpeg:new): FFPlay set different pts from ffmpeg for AVFilterBufferRef
FFmpeg
trac at avcodec.org
Fri Mar 25 00:30:48 CET 2011
#17: FFPlay set different pts from ffmpeg for AVFilterBufferRef
---------------------+----------------------
Reporter: chinshou | Owner: michael
Type: defect | Status: new
Priority: normal | Component: FFmpeg
Version: | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced: 0
Analyzed: 0 |
---------------------+----------------------
Comment (by saste):
Replying to [ticket:17 chinshou]:
> Sorry I did not used the latest FFmpeg.
>
> I found this problem with version 26383 get from ffmpeg on windows
autobuild site.
>
> ffplay set the pts for AVFilterBufferRef struct with output from
guess_correct_pts function which is very small for example 67, 133 ,etc
for the first several frames.
>
> But ffmpeg will set the pts for AVFilterBufferRef with very large
rescaled value which is calculated by output_packet function's function
following process.
[...]
> and used the command
>
> ffmpeg -i 1.avi -vf "rotate" 2.avi
> ffplay -vf "rotate" 1.avi
>
> confirmed the problem
Sorry but I can understand which is the problem. Can you show me a failing
command?
Timebases may be re-scaled within filters, but that shouldn't be an issue
as they are scaled
back at the end of the filterchain.
Also don't forget that timestamp values need to be rescaled accordingly to
their timebases:
picref_time = picref->pts * av_q2d(inlink->time_base);
--
Ticket URL: <http://avcodec.org/trac/ffmpeg/ticket/17#comment:1>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list