New submission from Jack Jansen <[email protected]>: Playback of (some?) H264 files over HTTP fails. This happens both with the current trunk and with the 0.5 release. Things worked correctly with ffmpeg of approximately mid-2008.
A sample file displaying the problem is <http://old- www.cwi.nl/projects/Ambulant/Demos/VideoTests/Content/turn-on-off.mp4>. ffplay gives lots of errors, and shows maybe one frame, maybe nothing. Debugging revealed that within the (binary) data passed from the reader to the decoder there is suddenly a couple of HTTP header lines. The problem appears to be somewhere in the http seek code: if I disable this by putting a "return -1;" near the top of http_seek(), simulating the the server does not implement seeking, the file plays back correctly. The same file also plays back correctly locally. MPEG-1 files play back correctly, also over http. I have not tried other formats. This behaviour has been seen with a number of distinct webservers (but all are probably apache-based) with clients on MacOSX 10.5 and 10.6 as well as Windows. ---------- messages: 8431 priority: normal status: new substatus: new title: MP4/H264 playback over HTTP fails type: bug _____________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/roundup/ffmpeg/issue1631> _____________________________________________________
