[FFmpeg-user] gracefully restart an ffmpeg stream?

jd1008 jd1008 at gmail.com
Sun Jan 10 21:30:49 CET 2016



On 01/10/2016 01:27 PM, Reindl Harald wrote:
>
> Am 10.01.2016 um 21:24 schrieb jd1008:
>> On 01/10/2016 01:07 PM, Reindl Harald wrote:
>>>
>>>
>>> Am 10.01.2016 um 21:05 schrieb jd1008:
>>>> On 01/10/2016 01:00 PM, Reindl Harald wrote:
>>>>>
>>>>>
>>>>> Am 10.01.2016 um 20:48 schrieb chovy:
>>>>>> What's the least intrusive way to restart an ffmpeg stream?
>>>>>>
>>>>>> I don't mind if the stream flickers or jumps ahead...but right now
>>>>>> when I kill the pid and restart it, the player completely stops
>>>>>> playing it.
>>>>>
>>>>> that's nothing you can solve on the server side
>>>>> the client needs to graceful hand short interruptions
>>>> Seems like if the server kills the video streamer, then the client's
>>>> connection is broken. So when server restarts the streamer, then
>>>> the client should still be able to re-connect to server and start
>>>> playing the stream. No?
>>>
>>> surely, that connection is broken
>>> yes, the *client* should be able to reconnect
>>>
>>> if the client don't re-connect just blame the client
>>> you can't solve that on the server side
>>>
>>> exactly what i said
>> Since the client is not able to reconnect, it seems that it may be 
>> possible
>> that the very server PROCESS which invokes ffmpeg to start the stream
>> needs to be restarted, not just ffmpeg - I am assuming the main server
>> daemon is NOT ffmpeg
>
> jesus christ - it does not matter who is the main server daemon
>
> when the client can't cope with a interrupted connection than you 
> can't fix that anywhere else then on the client side
>
> and for "I am assuming the main server daemon is NOT ffmpeg", well, 
> than it's even more NOT a ffmpeg topic
That's  the point I wanted the OP to know.
Since ffmpeg is a spawned process based on the request of the client,
then the problem would be the server daemon, and not ffmpeg.


More information about the ffmpeg-user mailing list