OK, I went through the thread from January about http seeking. As far as I understand, it is so ffmpeg can directly get a URL like http://pornonet.com/dirty-movie.xxx, and seek it, presumably for the sake of skipping inane dialog, and getting directly to the naughty bits. All well, of course, but as far as I can tell in the ffmpeg/ffserver combo, the first step is to get the stream parameters, (in the conf file), from ffserver via GET, then send the stream back via POST. When I connected vial telnet, or wget the response I got back was very short. (A few dozen bytes, or so). The data are not plain text, and not any type of movie format, as far as I know. (Begins with FFM, then binary). The response is short, and complete. Nothing really to seek. Is the problem that ffmpeg is trying to seek, when there is really nothing to seek? P. --------------------------------- Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4