Skip to main content
T
Tom_Darby_at_CA
Participant
August 24, 2010
Question

Desperately need solution to Backwards Timestamp FMS Server error

  • August 24, 2010
  • 1 reply
  • 1834 views

We have a very simple webcam recording/playback application we're using in a mission-critical user assessment application.  Users are given the ability to record themselves using their webcam and microphone, then review their recording and submit it for graded review.  The recording application appears multiple times per HTML page, and while we can record and play back video, we have large numbers of instances in our core.log of the following error

Server detected a backward timestamp from [####]to [####] in file: [filePath]

While these videos will play back with varying degrees of reliability, they will often "hang" for several seconds at the end of playback before sending the appropriate NetStream.Play.Stop and NetStream.Buffer.Empty events, and will sometimes hang indefinitely.  Further, they report inaccurate runtime metadata, causing our playback indicator and progress/scrub bar to function erratically.  In any case, the functionality and user experience of the recording tool is substantially degraded and must be fixed in order to successfully deploy this tool.

Disabling NTP services is not an option, and further does not appear to be the culprit, as these errors occur on a large number of recordings.  As recordings need to be immediately available for self-review before submission, running flvcheck on each recording is also not an option.  We have tried a variety of fixes, including waiting to unpublish until the buffer is empty, reconnecting after every recording, forcing FMS not to reuse connections, and using separate NetStream objects for recording and playback.  Nothing has eliminated these errors.  Adobe support referred us to Tier 2 support, and I am in the process of contacting them, but I'm looking to exhaust all my options before continuing.

Is there any reliable solution to the backwards timestamp recording issue, or do we need to find a different media server application for our needs?

Tom Darby

Manager of Multimedia Design

Connections Academy

http://www.connectionsacademy.com/

    This topic has been closed for replies.

    1 reply

    N
    Adobe Employee
    NpComplete
    Adobe Employee
    August 25, 2010

    Are you using the flash player for publishing the stream?? If yes, can you please try using the latest Flash Player build. Which FMS version are you using?? You can use the flvcheck tool to verify you flv.

    T
    Tom_Darby_at_CAAuthor
    Participant
    September 10, 2010

    Yes, we are using Flash Player to record this stream.

    We are experiencing this issue on the latest version of the Flash Player (Win FF and Win IE), as well as older versions of Flash Player 10.

    This error manifests on FMS 3.5.3, 3.5.4, and 4.0.

    As noted in the original post, using flvcheck to verify and fix timestamps is not a suitable solution given the volume of recordings and the need for the video to be immediately available to the user for playback.

    We're still looking for a fix.  Has anybody else who has encountered this issue successfully resolved it?

    N
    Adobe Employee
    NpComplete
    Adobe Employee
    September 14, 2010

    You can use this http://kb2.adobe.com/cps/495/cpsid_49588.html to log the live stream. Logs may help to know whether the

    backward timestamps are being sent by the player/cam or FMS is goofing up with the timestamp.

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