On Fri, May 11, 2018 at 2:54 PM, Moritz Barsnick <barsn...@gmx.net> wrote: > On Thu, May 10, 2018 at 17:41:26 +0200, Stephan Holljes wrote: >> +In its current for this is a HTTP live-streaming server. A media file can be > ^ form ^ an > >> +streamed to a number of clients with the correct media file being muxed on- >> +the-fly for each client starting at the current position in the stream. > > I don't understand: What's "correct"? And what is the "current > position"? From ffserver's point of view: The position if progressed to > between launch and connection of client?
"correct" was probably the wrong word here. I have replaced it locally by "a proper" instead of "the correct", although it feels unnecessary in general. I might reword this. The "current position" is, as you described, the position ffserver has progressed to with reading the input since starting the program + configurable buffering (so client's don't "stutter" during playback). I will try to make that a bit clearer. > >> +The stream received by the clients is simply a HTTP response to an HTTP > ^ an ^ here, > it's correct ;-) > >> +is answered with a HTTP 400 error. > ^ an I noticed these right before going to bed last night as well, fixed. > > Moritz > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel Thanks again! _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
