Skip to main content
Participant
July 3, 2013
Question

Backward Timestamp - FMS 4.5

  • July 3, 2013
  • 1 reply
  • 1159 views

Hello All,

I'm working with Edgecast on an issue with the FMS logs stating the following:

2013-07-02 16:05:05 24854 (w)2611179 Warning from libf4f.so: [Utils] [07022013-10060-PS410122] [07022013-10060-PS410122] FMS F4F recording received timestamps with absolute time flowing backward lastTime held was 1928742 and the most recent arrived was 1928736. This message is being ignored - recording will continue.

Edgecast thinks this is causing Server Size Archive file corruption and iOS playout issues.

I was hoping someone could tell me what timestamp or timecode it is reffering to.  Is it the elementry h.264 video timecodes (PCR or PTS or STC) , ip packet timecodes, or other information.

Thank you

Austin

This topic has been closed for replies.

1 reply

Participating Frequently
July 5, 2013

Hi

That would be the audio/video timecodes (DTS)

-Karishma

Participant
July 6, 2013

Thank you Karishma. 


Would only video DTS in the PES cause this or would audio also cause this?  Just to be clear only the DTS issues would cause this to happen, correct?


I'm assuming the unit of time is milliseconds, correct?


When <streamsynchronization> is enable on FMLE, does that change the DTS and other PES timecode/timestamps to be absolute time (referenced to UTC) rather than a counter? 


Thank again

Austin


Participating Frequently
July 8, 2013

Hi

Timestamp of all messages being sent to AMS (irrespective if audio, video or data) should be in increasing order. The timestamp is in milliseconds. For video messages that time would be DTS and for audio/data it would be the message time.

Also, your understanding of streamsynchronization is right and you should set that to true if you want to retstart/append to an existing stream anytime.

-Karishma