Shawn Lewis <[email protected]> added the comment: Very strange. If I download the file (get it from akami at 15mb d/l, so I now bandwidth is good), and then ffmpeg encode it locally, i get some errors, but nothing to worry about.
If put the file locally on a web server, it reverts back to the original issue posted. So my assumption is their is something wrong with the network http-loading of a mp4 or something (in ffmpeg)?? As I need to transcode on the fly, and would be a complete waste (as well as break the application of haveing realtime transcoding) of resources to have to d/l files, wait for the d/l to complete, then transcode. I know with VLC I can treat a file "as a stream", which allows me to point to a file, and have it d/l progressively, and vlc just works as data comes in. Prob just treating the file as an open PIPE. With ffmpeg, other than using a PIPE (which cant be done as PIPE's are not seekable), im not sure if I can treat a file as a stream. In any case, the issue seems to be in the network code of things in ffmpeg as you suggested. ---------- topic: +ffmpeg ________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/issue2282> ________________________________________________
