Skip to main content
V
vayvanne
Inspiring
June 30, 2017
Question

default live app disconnects every 7:50h

  • June 30, 2017
  • 2 replies
  • 4632 views

Hello,

I have pretty regular setup with fmle encoder and AMS 5.0.14 on the same windows PC.

For testing purposes I run ffmpeg like this:

ffmpeg -rtmp_live live -i rtmp://localhost/live/stream -f null -

Stream disconnects every 7h 50 s.

I do not see disconnects on fmle side and do not see anything helpful in logs.

Should not default live app support 24/7 streaming?

Tips and debug suggestions are appreciated.

This topic has been closed for replies.

2 replies

V
vayvanneAuthor
Inspiring
August 9, 2018

Still no solution. Stream reading ffmpeg instances disconnects reaching to 4GB traffic limit. Publishing to the same server one - survives for about 4 weeks to reach rtmp timestamp overflow. How could I debug this disconnection issue on server side?

Graeme Bull
Community Expert
Graeme BullCommunity Expert
Community Expert
August 13, 2018

I don't know of any cases where this doesn't happen at some point. 4 weeks is a long time actually, you've done well. You'll likely have to plan for disconnections instead of trying to solve this at the media server level.

V
vayvanneAuthor
Inspiring
August 13, 2018

Thanks for reply. 4 weeks is when publishing to the server (pushing). When reading from the server 4GB does mean only 7-8 hours of uptime with my stream. This is substandard in my view.

Graeme Bull
Community Expert
Graeme BullCommunity Expert
Community Expert
July 31, 2017

This generally happens when a core gets rolled over. Which sounds weird.. but it's the thread running for the AMS service itself, it rolls over a particular amount of minutes in, everybody that is connected, gets disconnected and the app goes on as normal.. Not sure of a better way of explaining it

    V
    vayvanneAuthor
    Inspiring
    January 29, 2018

    Hi Graeme Bull, thanks for reply. 7h 50m is since ffmpeg starts, not FMLE or server. I suspect it is something with ffmpeg (zeranoe windows build btw), not server or live app. It also has something to do with stream itself, because another audio only stream survives a week. It can be compatibility issue with FMLE linked to timestamps as I see the following:

    Fri Jan 26 2018 17:03:46 : Error: Device Timecode not supported : The selected video device or the timecode dll provided for the device doesn't support timecode generation. Disabling Device timecode generation option.

    ... with the FMLE option "Embed system time as Timecode" enabled.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices