[vlc-devel] VLC reading SDP files does not re-connect with "--loop"

[Sampsa Riikonen]

Dear List (and Remi),

Pretty-please, one final question on this issue..

I have been able to pin-point this bug/error into a few simple steps 
that anyone can easily try @home:
(you might actually need a crappy network to reproduce this)

Launch vlc with:

vlc -vvv filename.sdp

Where filename.sdp points to a multicast stream from an ip camera, then

1) I press "pause"

2) I wait for a few seconds

3) I press play again

=> vlc goes into the state

"more than 5 seconds of late video -> dropping frame (computer too slow ?)"

and never recovers again, unless ..

4) I press "stop" and then "play" again

So, I guess that issuing "stop" clears buffers, closes sockets, etc. and 
that's the difference.

Or else, what is going on?

Regards,

Sampsa


On 30.07.2015 14:11, Sampsa Riikonen wrote:
>
>
> On 30.07.2015 14:01, Rémi Denis-Courmont wrote:
>> Le 2015-07-30 13:22, Sampsa Riikonen a écrit :
>>> On 30.07.2015 11:36, Rémi Denis-Courmont wrote:
>>>> Le 2015-07-30 11:12, Sampsa Riikonen a écrit :
>>>>> 1) For the SDP file case, is there any switch / option to tell vlc
>>>>> that if data has not been received in N seconds (this is automagic in
>>>>> the "rtsp://" case), it should close the sockets and re-connect again
>>>>> (I'm talking about the UDP data sockets for video and audio) ?
>>>>
>>>> The question makes no sense. You cannot connect (to) a multicast 
>>>> stream.
>>>>
>>>
>>> Sorry, I did not make myself clear .. I am talking about socket.bind,
>>> i.e. with "reconnection" I mean ..
>>
>> There is absolutely no point in doing that.
>>
>
> ok, if you say so.
>
> That still leaves us with the original problems A, B and C.
>
> Any consultants out there willing to get paid for implementing:
>
> 1) A vlc event for the unfortunate detection of ..
>
> "more than 5 seconds of late video -> dropping frame (computer too 
> slow ?)"
>
> (that event should be catchable from python .. needs tweaking the 
> python ctypes module as well)
>
> 2) .. or, the reinitialization / restart of mediaplayer when that 
> happens ?
>
>
> Regards,
>
> Sampsa
>
>