> And 'moov' contains the info needed to make sense of the rest of the file.
> Now that it has that, it goes back and downloads from where it
> short-circuited before. At <10MBs, as you say, it might make more sense to
> download the whole file and then work with it on disk. But for larger
>
Hi,
> There is no attempt to seek the video on the command line. The server returns
> HTTP/1.1 206 Partial Content initially and ffmpeg then tries to get data at
> different offsets before it prints "All info found" and proceeds with the
> conversion. Multiple connections cause an additional
Am Fr., 17. Juli 2020 um 08:21 Uhr schrieb Vladimir Grishchenko
:
>
> A bit more details.
But still not enough.
When asking for support here, please always provide the command line
you tested together
with the complete, uncut console output.
Carl Eugen
on behalf of Vladimir
Grishchenko
Sent: Thursday, July 16, 2020 5:04 PM
To: ffmpeg-user@ffmpeg.org
Subject: [FFmpeg-user] Ffmpeg issues multiple HTTP requests when starting a
video from a URL
I'm using ffmpeg to read an mp4 video from a HTTP URL and in some cases it
issues up to 3 HTTP calls before
I'm using ffmpeg to read an mp4 video from a HTTP URL and in some cases it
issues up to 3 HTTP calls before it actually starts the conversion. There is no
attempt to seek the video on the command line. The server returns HTTP/1.1 206
Partial Content initially and ffmpeg then tries to get data
