Results 1 to 3 of 3

Thread: Timecode of order

  1. #1
    Join Date
    Aug 2011
    Posts
    100

    Default Timecode of order

    Hi! I have WowzaMS3 mountly license
    120 live streams, customers looking cupertino streams, average connections is 800, and sometime in errorlog i got that message:

    WARN server comment 2011-12-18 21:50:10 - - - - - 41898.892 - - - - - - - -CupertinoPacketHandler.handlePacket[live/_definst_/live1.stream]: Timecode out of order [audio]: 15:16777210
    WARN server comment 2011-12-18 21:50:10 - - - - - 41898.892 - - - - - - - -SanJosePacketHandler.handlePacket[live/_definst_/live1.stream]: Timecode out of order [audio]: 15:16777210
    WARN server comment 2011-12-18 21:50:10 - - - - - 41898.99 - - - - - - - -CupertinoPacketHandler.handlePacket[live/_definst_/live1.stream]: Timecode out of order [video]: 26:16777202
    WARN server comment 2011-12-18 21:50:10 - - - - - 41898.99 - - - - - - - -SanJosePacketHandler.handlePacket[live/_definst_/live1.stream]: Timecode out of order [video]: 26:16777202
    WARN server comment 2011-12-18 21:50:10 - - - - - 41899.105 - - - - - - - -CupertinoPacketHandler.resetStream[live/_definst_/live1.stream][11:5]: Timecodes jumped back in time.
    WARN server comment 2011-12-18 21:50:10 - - - - - 41899.105 - - - - - - - -SanJosePacketHandler.resetStream[live/_definst_/live1.stream][11:5]: Timecodes jumped back in time.


    What it can be?

  2. #2
    Join Date
    Sep 2011
    Posts
    1,933

    Default

    Hi
    There could are generally two reasons for this and they are
    1) your network is too busy and you are suffering from packed loss
    2) your sever is overworked and can't process the packets in time.

    An unlikely but still possible reason could be that your source stream is broken but I don't think that it is in this case.

    Jason

  3. #3

    Default

    Quote Originally Posted by JasonH View Post
    Hi
    There could are generally two reasons for this and they are
    1) your network is too busy and you are suffering from packed loss
    2) your sever is overworked and can't process the packets in time.

    An unlikely but still possible reason could be that your source stream is broken but I don't think that it is in this case.

    Jason
    How can I be sure what is the real problem?

Similar Threads

  1. Timecode out of order [video]
    By jefe78 in forum Live Streaming and Encoder Discussion
    Replies: 3
    Last Post: 01-11-2014, 07:07 AM
  2. Wowza transcoder problem (Timecode out of order)
    By rubenlg in forum AddOn: Transcoder
    Replies: 3
    Last Post: 07-17-2013, 11:53 AM
  3. Live Stream - Timecode out of order [audio]
    By dirtystar in forum General Forum
    Replies: 1
    Last Post: 10-12-2012, 03:30 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •