# Timecodes out of order **URL:** \ **Category:** Wowza Streaming Engine\ **Created:** [August 29, 2012, 4:10pm UTC](https://community.wowza.com/t/timecodes-out-of-order/36140 "2012-08-29T16:10:51Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![David\_Peterson](https://avatars.discourse-cdn.com/v4/letter/d/9de0a6/32.png) [@David\_Peterson](https://community.wowza.com/u/David_Peterson)\ **Post date:** [August 29, 2012, 4:10pm UTC](https://community.wowza.com/t/timecodes-out-of-order/36140/1 "2012-08-29T16:10:51Z")
How do I interpret these messages? What is the [audio}: xxxxx:yyyyy. Is the xxxxx the expected and the yyyyy the actual timestamps? Or is it something else? They always seem to be around 21 to 22 apart. Is that a clue of anything? Second question. What is Wowza doing when it gets this warning? Is it tossing the audio packets out? I see the video lagging the audio so it seems like the audio may be running faster because wowza is tossing packets, but that’s just a theory. What actually happens? WARN server comment 2012-08-29 21:03:18 - - - - - 40.917 - - - SanJosePacketHandler.handlePacket[live/_definst_/udp://239.0.4.4:2025]: Timecode out of order [audio]: 54720:54741 WARN server comment 2012-08-29 21:04:43 - - - - - 125.687 - - - CupertinoPacketHandler.handlePacket[live/_definst_/udp://239.0.4.3:2027]: Timecode out of order [audio]: 136342:136363 WARN server comment 2012-08-29 21:04:43 - - - - - 125.687 - - - SanJosePacketHandler.handlePacket[live/_definst_/udp://239.0.4.3:2027]: Timecode out of order [audio]: 136342:136363 WARN server comment 2012-08-29 21:04:43 - - - - - 125.687 - - - LiveStreamPacketizerSmoothStreaming.handlePacket[live/_definst_/udp://239.0.4.3:2027]: Timecode out of order [audio]: 1363420000:1363630000 WARN server comment 2012-08-29 21:04:43 - - - - - 125.699 - - - SanJosePacketHandler.handlePacket[live/_definst_/udp://239.0.4.2:2027]: Timecode out of order [audio]: 136427:136448 WARN server comment 2012-08-29 21:04:43 - - - - - 125.699 - - - CupertinoPacketHandler.handlePacket[live/_definst_/udp://239.0.4.2:2027]: Timecode out of order [audio]: 136427:136448 WARN server comment 2012-08-29 21:04:43 - - - - - 125.699 - - - LiveStreamPacketizerSmoothStreaming.handlePacket[live/_definst_/udp://239.0.4.2:2027]: Timecode out of order [audio]: 1364270000:1364480000 WARN server comment 2012-08-29 21:04:43 - - - - - 125.888 - - - SanJosePacketHandler.handlePacket[live/_definst_/udp://239.0.4.4:2027]: Timecode out of order [audio]: 136512:136533 WARN server comment 2012-08-29 21:04:43 - - - - - 125.888 - - - CupertinoPacketHandler.handlePacket[live/_definst_/udp://239.0.4.4:2027]: Timecode out of order [audio]: 136512:136533 WARN server comment 2012-08-29 21:04:43 - - - - - 125.889 - - - LiveStreamPacketizerSmoothStreaming.handlePacket[live/_definst_/udp://239.0.4.4:2027]: Timecode out of order [audio]: 1365120000:1365330000 ---
**Author:** ![Jason\_Hilton](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_hilton/32/437_2.png) [@Jason\_Hilton](https://community.wowza.com/u/Jason_Hilton)\ **Post date:** [August 30, 2012, 11:27am UTC](https://community.wowza.com/t/timecodes-out-of-order/36140/2 "2012-08-30T11:27:33Z")
Hi Generally this indicates an encoder issue. It also could be an issue when the machine CPU utilization, or GPU utilization, is maxed out. To debug, see [How to debug AAC or MP3 timecode issues with cupertino packetization](https://www.wowza.com/docs/how-to-debug-aac-or-mp3-timecode-issues-with-apple-hls-packetization). Try using [Advanced Stream Monitor](https://www.wowza.com/docs/how-to-enable-advanced-monitoring-and-resetting-of-mediacaster-streams%28MediaStreamNameGroups-and-ModuleMediaCasterStreamMonitorAdvanced). If you see this message immediately after the stream is published before packetization starts, it can be ignored. You can find answers and suggestions to questions you may have in regard to log messages you encounter here, [https://www.wowza.com/docs/how-to-troubleshoot-error-messages](https://www.wowza.com/docs/how-to-troubleshoot-error-messages) Jason