[FFmpeg-devel] [PATCH] ogg: Fix seek to zero and packet pts after read through.
Dale Curtis
dalecurtis at chromium.org
Wed Apr 25 04:42:31 CEST 2012
On Tue, Apr 24, 2012 at 6:57 PM, Michael Niedermayer <michaelni at gmx.at>wrote:
>
> i dont seem to have equally as much luck with that stream
>
> with the patch:
> ret: 0 st: 0 flags:0 dts: 0.000000 pts: 0.000000 pos: 6183 size:
> 4133
> ret: 0 st: 1 flags:1 dts: 5833.897506 pts: 5833.897506 pos: 10360
> size: 91
> ret: 0 st: 1 flags:1 dts: 5833.920726 pts: 5833.920726 pos: 10479
> size: 91
> ret: 0 st: 0 flags:1 dts: 5833.920000 pts: 5833.920000 pos: 10598
> size: 11769
> ret: 0 st: 1 flags:1 dts: 5833.943946 pts: 5833.943946 pos: 22441
> size: 94
> ret: 0 st:-1 flags:0 ts:-1.000000
> ret: 0 st: 0 flags:0 dts: 0.000000 pts: 0.000000 pos: 6183 size:
> 4133
> ret: 0 st: 1 flags:1 dts: 5833.897506 pts: 5833.897506 pos: 10360
> size: 91
> ret: 0 st: 1 flags:1 dts: 5833.920726 pts: 5833.920726 pos: 10479
> size: 91
> ret: 0 st: 0 flags:1 dts: 5833.920000 pts: 5833.920000 pos: 10598
> size: 11769
> ret: 0 st: 1 flags:1 dts: 5833.943946 pts: 5833.943946 pos: 22441
> size: 94
>
> that looks consistent, giving the same both times but still its
> wrong both times, the first packet ends up with 0 time stamps
>
>
Strange, what are the numbers w/o the patch? The first read_frame shouldn't
be affected by the patch since neither ogg_read_seek nor ogg_read_timestamp
have been called by that point, right? I can't find any calls to them in
any case.
- dale
More information about the ffmpeg-devel
mailing list