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
{{ message }}
This repository has been archived by the owner on Jul 17, 2024. It is now read-only.
Hi,Roverr,
Thanks for your last help,and it's effective.
I changed the setting of RTSP_CLEANUP_ENABLED:false , but start api responsebody returns 'running:false' in the course of time. So i want to know what's the meaning of 'running' , and final purpose is knowing the RTSP stream trans state.
Thanks again!
The text was updated successfully, but these errors were encountered:
Actually running should indicate if your transcoding process for the stream is started running or not. It states that the underlying ffmpeg process is still working or not. However, it does not do it perfectly as it is building on the underlying rate limiter's activity status. Which is in your case matters in absolutely no way, because your streams are always "active".
That's actually a good catch, I will take look on the weekend how it could be made more consistent to reflect the transcoding process better
Hi,Roverr,
Thanks for your last help,and it's effective.
I changed the setting of RTSP_CLEANUP_ENABLED:false , but start api responsebody returns 'running:false' in the course of time. So i want to know what's the meaning of 'running' , and final purpose is knowing the RTSP stream trans state.
Thanks again!
The text was updated successfully, but these errors were encountered: