You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first frames transmitted during an RTSP transmission have wrong timestamp and this causes some players (such as VLC) to stop playing.
This occurs because the queue between an Encoder and a SinkManager (Transmitter) is filled up without being consumed. When it is full, for each new frame pushed into the queue, the last frame pushed is flushed. This means that there is a timestamp gap between all the frames of the queue (the first ones which where pushed into the queue) and the last one.
So, when someone requests the RTSP session (or we create an RTP Connection) the timestamp gap "is transmitted" to the player.
The text was updated successfully, but these errors were encountered:
The first frames transmitted during an RTSP transmission have wrong timestamp and this causes some players (such as VLC) to stop playing.
This occurs because the queue between an Encoder and a SinkManager (Transmitter) is filled up without being consumed. When it is full, for each new frame pushed into the queue, the last frame pushed is flushed. This means that there is a timestamp gap between all the frames of the queue (the first ones which where pushed into the queue) and the last one.
So, when someone requests the RTSP session (or we create an RTP Connection) the timestamp gap "is transmitted" to the player.
The text was updated successfully, but these errors were encountered: