Mona server reliability

[Jason Dupree]

Hey guys,

I successfully used Mona Server this weekend on an 11 hour live stream. I had 3 Mevo start cameras on the network and 2 phone  cameras off the network sending their feed using Larix Broadcast to Mona Server. It seemed like the first half of the day was great. We had some very short glitchy moments every so often, but then towards the second half of the day and by the end it was every 5-20 seconds before the feed would stop and take a moment to catch up. 

I also had the issue where the videos were not in sync. Is it possible these issues could be solved with some kind of hardware controller, or is the laptop I used just not up to snuff? And any thoughts as to why the feed was so good earlier in the day?

[MonaServer]

Hi Jason!

Did you get warning or error logs on the server side?

There is the bufferSize configuration parameter that can avoid pauses without data like black screen but it only allow to bufferize more.

Now there are a lot of points that can explain sync issues :

- the main one is the network, when you use wifi you can't ensure that there will be no congestion or latency since it's not a reliable connection,

- the protocol used, RTMP is TCP so if a congestion occurs it will just bufferize, some UDP protocols like RTMFP and SRT can ignore some packets when congestion happens, this can be useful to always stay "live",

- the CPU of the server and the clients, this one can be controlled though, take a look at the task manager for example, if CPU is never at 100% it should be ok.

Regards

Thomas

[Jason Dupree]

Thanks for the reply and all of the info! Here's a snippet of the kind of stuff I saw throughout the day. First thing that threw me off was the connection to wpad, as I didn't have that in my folder. I've attached my input folder.

Secondly, I don't have anything in my ini file. So thanks for the ini file you linked to. I'll get that a try.

Thirdly, I didn't realize Mona Server can handle SRT as well. I'll probably give that a try. But for RTMFP, I didn't know about this protocol. Is the process for using this the same as rtmp? just use rtmfp in the url?

And Lastly, I know one mistake I made is I forget to set Vmix's stream output to Youtube to use hardware encoder. So my CPU probably had more strain than it would normally.

01/08 17:09:52.3  INFO   3492 MonaTiny.cpp[176]             HTTP 127.0.0.1:62099 subscribe to wpad

01/08 17:09:52.7  INFO   3492 Server.cpp[119]               3 clients

01/08 17:10:04.7  INFO   3492 MonaTiny.cpp[189]             HTTP 127.0.0.1:62099 unsubscribe to wpad

01/08 17:10:04.7  INFO   3492 Server.cpp[119]               2 clients

01/08 17:10:34.9  WARN   3492 TCPSession.cpp[32]            RTMP 2-174.248.139.10:4975, Connection aborted

01/08 17:10:34.9  NOTE   3492 MonaTiny.cpp[166]             Client unpublish miles

01/08 17:10:34.9  INFO   3492 Publication.cpp[205]          Publication miles stopped

01/08 17:10:36.7  INFO   3492 Server.cpp[119]               1 clients

01/08 17:10:57.0  WARN   3492 TCPSession.cpp[32]            RTMP 1-192.168.0.130:62235, Connection reseted (from=0.0.0.0:0, size=2048, flags=0)

01/08 17:10:57.0  WARN   3492 TCPSession.cpp[32]            RTMP 1-192.168.0.130:62235, Connection aborted

01/08 17:10:57.0  INFO   3492 MonaTiny.cpp[189]             RTMP 192.168.0.130:62235 unsubscribe to miles

01/08 17:10:58.7  INFO   3492 Server.cpp[119]               0 clients

01/08 17:11:13.5  ERROR  3492 FlashMainStream.cpp[150]      Method client getStreamLength not found in application ocrr/

01/08 17:11:13.5  INFO   3492 MonaTiny.cpp[176]             RTMP 192.168.0.130:62267 subscribe to miles

01/08 17:11:13.5  INFO   3492 FlashStream.cpp[126]          setBufferTime 3000ms on stream miles

01/08 17:11:14.7  INFO   3492 Server.cpp[119]               1 clients

01/08 17:14:16.9  INFO   3492 MonaTiny.cpp[176]             HTTP 127.0.0.1:51455 subscribe to wpad

01/08 17:14:18.8  INFO   3492 Server.cpp[119]               2 clients

01/08 17:14:24.9  WARN   3492 TCPSession.cpp[32]            HTTP 4-127.0.0.1:51455, Connection aborted

01/08 17:14:24.9  INFO   3492 MonaTiny.cpp[189]             HTTP 127.0.0.1:51455 unsubscribe to wpad

01/08 17:14:26.8  INFO   3492 Server.cpp[119]               1 clients

01/08 17:17:59.4  NOTE   3492 MonaTiny.cpp[155]             Client publish anna

01/08 17:17:59.4  INFO   3492 Publication.cpp[128]          Publication anna {} started

01/08 17:18:00.8  INFO   3492 Server.cpp[119]               2 clients

01/08 17:18:24.9  WARN   3492 TCPSession.cpp[32]            RTMP 2-71.221.134.246:50350, Connection aborted

01/08 17:18:24.9  NOTE   3492 MonaTiny.cpp[166]             Client unpublish anna

01/08 17:18:24.9  INFO   3492 Publication.cpp[205]          Publication anna stopped

01/08 17:18:26.9  INFO   3492 Server.cpp[119]               1 clients

01/08 17:18:28.0  NOTE   3492 MonaTiny.cpp[155]             Client publish anna

01/08 17:18:28.0  INFO   3492 Publication.cpp[128]          Publication anna {} started

01/08 17:18:28.9  INFO   3492 Server.cpp[119]               2 clients

01/08 17:20:04.7  INFO   3492 MonaTiny.cpp[176]             HTTP 127.0.0.1:50233 subscribe to wpad

01/08 17:20:04.9  INFO   3492 Server.cpp[119]               3 clients

01/08 17:20:17.2  INFO   3492 MonaTiny.cpp[189]             HTTP 127.0.0.1:50233 unsubscribe to wpad

01/08 17:20:17.2  INFO   3492 Server.cpp[119]               2 clients

01/08 17:20:55.6  WARN   3492 TCPSession.cpp[32]            RTMP 1-71.221.134.246:50352, Connection aborted

01/08 17:20:55.6  NOTE   3492 MonaTiny.cpp[166]             Client unpublish anna

01/08 17:20:55.6  INFO   3492 Publication.cpp[205]          Publication anna stopped

[MonaServer]

Hi Jason,

Sorry for the late answer, we are in vacation.

Hardware encoding is a good point, this could resolve any CPU overload.

About RTMFP you can forget it for now, it is a Flash protocol which is a bit similar to rtmp but not supported by common streaming services.

Regards

Thomas