Thanks Carl, What would make it more efficient (if possible) is for requests to contain end offset. As it stands, the server downloads the file to the end for every request. Is there another approach (not necessarily http) that would allow me to only transfer the blocks that ffmpeg actually needs ?
Yuri > On Jan 17, 2016, at 9:43 AM, Carl Eugen Hoyos <[email protected]> wrote: > > Yuri Zats <yuri <at> zatsweb.com> writes: > >> For example, http requests for a short 10MB file look like this: >> bytes=0- >> bytes=10947419- >> bytes=36- >> bytes=3153008- >> bytes=5876422- >> >> Is what I’m seeing matching what people thing should be happening ? > > The issue - iirc - is that mov files have different sizes. > Your file would fit in memory / buffer, but this is > impossible for mov files in general. The number of accesses > do not seem completely unreasonable to me but I may miss > something. > mov is simply not made for streaming. > > Carl Eugen > _______________________________________________ > ffmpeg-user mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/ffmpeg-user _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user
