Skip to content
This repository has been archived by the owner on Jul 12, 2023. It is now read-only.

RTSP Player Endpoint Issue #144

Closed
tjmcclure0501 opened this issue Nov 6, 2016 · 4 comments
Closed

RTSP Player Endpoint Issue #144

tjmcclure0501 opened this issue Nov 6, 2016 · 4 comments

Comments

@tjmcclure0501
Copy link 

me (Tim McClure change)

Oct 11

I am using a player endpoint to consume a live RTSP endpoint. The player endpoint is being created server-side and then distributed to through Kurento to clients as they connect to save on the transcoding from RTSP to OP8. It is working well except for one scenario as described below:

  1. If the RTSP is streaming before the player endpoint is created everything works well.
  2. If the player is created before the RTSP stream is streaming and the RTSP source starts streaming before any client webRTCEndpoints connect everything works fine.
  3. If the player is created and a client webRTCEndpoint connects before the RTSP source starts streaming no video is ever rendered. It appears the RTSP source needs to be streaming before any client webRTCEndpoints can connect.

KMS Version:

Version 6.6

Using NodeJS server side - Chrome Browser Javascript
@sampleref
Copy link

Yes I too observed same problem. Basically our use case issues comes up where steps are like:

  1. RTSP Stream available
  2. PlayerEndpoint created and play is invoked on it
  3. RecorderEndpoint and WebrtcEndpoint connected to above player, everything works fine
  4. RTSP Stream disconnected, PlayerEndpoint throws error event
  5. PlayerEndpoint I keep into pause() state and wait for 3-4 secs
  6. Check if RTSP stream is alive again, once available
  7. Trigger play() on PlayerEndpoint above
  8. It just hangs, nothing further in logs too

@zhangalex
Copy link

@sampleref Could you please tell me how to check if rtsp stream is disconnected? And I tried to play() it again, it failed! I'm using kurento-utils-js.

@sampleref
Copy link

I am using https://github.com/bramp/ffmpeg-cli-wrapper to check RTSP is alive or not after I get Error/EndOfStream Event

j1elo added a commit to Kurento/kms-core that referenced this issue Jun 22, 2018
@j1elo
KmsAgnosticBin: FIXME Reconfigure pipeline (Kurento/bugtracker#144)
35c4865 
Work on Kurento/bugtracker#144

When an RTSP stream is dosconnected and re-connected again, and the
PlayerEndpoint is stopped and later restarted, there is an internal
error in the pad chain function, somewhere between the Agnosticbin's
input fakesing and the parsetreebin.

This fix will replace the fakesink with a new one whenever a flow error
happens, and will also force reconfiguring the treebin.

It's been tested that these two operation must be done together. It's
not enough to either just replace the fakesink, or just reconfigure the
input bin.
@j1elo
Copy link
Member

j1elo commented Nov 14, 2018

Please check if KMS version 6.8.1 fixes this issue

@j1elo j1elo closed this as completed Jun 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@zhangalex @j1elo @sampleref @tjmcclure0501