Skip to main content
M
Mr_Dave
Known Participant
December 29, 2011
Question

Server detected a backward timestamp from 1973406 to 0 in file

  • December 29, 2011
  • 1 reply
  • 2852 views

In my core.log file I'm receiving these error messages;

Server detected a backward timestamp from 1973406 to 0 in file:C:\FMSHOME\applications\livepkgr\streams\_definst_\bbc1

Server detected a backward timestamp from 1973406 to 0 in file:C:\FMSHOME\applications\livepkgr\streams\_definst_\bbc2

Is this an issue caused by the encoder? I'm using a Viewcast Niagara to encode and not the FMLE. These are the only settings I have available.

I'm using all default settings on the FMS 4.5 server. 

.

Thanks,

Dave

    This topic has been closed for replies.

    1 reply

    A
    Anonymous
    January 3, 2012

    Are you appending to some already existing streams on your server or is it a new recording ? There is a concept of Absolute Time Code which enables the encoders to publish the livestream based on absolute system time rather than starting the messages from timestamp 0 everytime you append to a recording.

    I suspect you encoder is starting everytime from 0 timestamp but since the server already has recording till some time - say x, for the server these are backward timestamps and hence the continous warnings.

    Try to check your encoder configurations for something like ATC or stream synchronization settings and set them to true(if any). 

    M
    Mr_DaveAuthor
    Known Participant
    January 5, 2012

    After speaking with support staff at ViewCast concerning the Niagara 4100 streaming appliance about this error, they replied with this response.

    "This is really a server side problem since the encoder can't determine how long it takes the server to tear down the stream. "

    Is there anything else I can do?

    Thanks,

    Dave


    Nikhil_Kalyan
    Nikhil_Kalyan
    Participating Frequently
    January 10, 2012

    But did you check whether ATC is enabled on the encoder?  Can you please confirm that /

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