aboutsummaryrefslogtreecommitdiffstats
path: root/libavcodec/cinepak.c
diff options
context:
space:
mode:
authorPanagiotis H.M. Issaris <takis.issaris@uhasselt.be>2011-11-15 18:35:03 +0100
committerMartin Storsjö <martin@martin.st>2011-11-18 11:33:44 +0200
commit795d9594cfaf9b6c9ce0c60f86c6e51636096a5a (patch)
tree02593ab93fb7b4ddb36092e5ae8ba6ba18979c8e /libavcodec/cinepak.c
parentdbc2424baa5aa4c72026d167f0678f2374620f44 (diff)
downloadandroid_external_ffmpeg-795d9594cfaf9b6c9ce0c60f86c6e51636096a5a.tar.gz
android_external_ffmpeg-795d9594cfaf9b6c9ce0c60f86c6e51636096a5a.tar.bz2
android_external_ffmpeg-795d9594cfaf9b6c9ce0c60f86c6e51636096a5a.zip
applehttp: Fix seeking in streams not starting at DTS=0
The Apple HTTP Live Streaming demuxer's implementation of seeking searches for the MPEG TS segment which contains the requested timestamp. In its current implementation it assumes that the first segment will start from 0. But, MPEG TS streams do not necessarily start with timestamp (near) 0, causing seeking to fail for those streams. This also occurs when using live streaming of HTTP Live Streams. In this case sliding playlists may be used, which means that in that case only the last x encoded segments are stored, the earlier segments get deleted from disk and removed from the playlist. Because of this, when starting playback of a stream in the middle of such a broadcast, the initial segment fetched after parsing the m3u8 playlist will not start from timestamp (near) 0, causing (the admittedly limited live) seeking to fail. This patch changes this demuxers seeking implementation to use the initial DTS as an offset for searching the segments containing the requested timestamp. Signed-off-by: Martin Storsjö <martin@martin.st>
Diffstat (limited to 'libavcodec/cinepak.c')
0 files changed, 0 insertions, 0 deletions