I 10035 Provider | stream.cpp:36 | RtspcProvider Application has started to play stream I 10035 Monitor | application_metrics.cpp:56 | Create StreamMetrics(ZxTsjrvA_lyn3) for monitoring I 10035 MediaRouter.Stream | mediarouter_stream.cpp:41 | Trying to create media route stream: name(ZxTsjrvA_lyn3) id(105)
I 10035 MediaRouter.App | mediarouter_application.cpp:181 | I 10035 MediaRouter.App | mediarouter_application.cpp:180 | Trying to create a stream: I 10035 Provider | application.cpp:116 | #default#rtsp application has created 5 stream motor I 10035 Provider | stream.cpp:49 | #default#rtsp/ZxTsjrvA_lyn3(105) has been started stream I 10035 Orchestrator | orchestrator.cpp:1280 | Trying to pull stream from provider using origin map: PullProvider I 10035 Signalling | rtc_signalling_server.cpp:99 | New client is connected: I know that RTSP is not fully implemented yet. So I can't see anything on the logs.Īt least to handle the logs in order stop receiving the error without control. Im having about 500MB of log file by day. It is very annoying because the audio gets stuck until I stop streaming, and the logs start growing without control. If you like we can make a test with my stream in order to check this on your servers. It seems that it only happens with RTSP streams. It happens for example with an AES67 source that comes from a PC through a Virtual Sound Card on my environment. These audios trigger FFMPEG exhausted buffer errors, and then the audio of this stream becomes unavailable until OME deletes it. What I found now is that it is related to some specific audio sources. I wrote something about this issue on #168 but at that moment I thought that a format change on the encoder's input was necessary to trigger this error.
0 kommentar(er)
