MPEGTS live stream & audio delay

[HectorH]

We are using Elecard's G4 SDK to encode live audio and video and then send it to WMS for redistribution. Audio is AAC LC 48kbps, Video is h.264 Baseline 3.0 600kbps. Video resolution is 640x360 @ 30fps

When we use JWPlayer (RTMP) we notice the audio lags behind the video by 4-6 seconds. It's not consistent.

When we use iOS (HLS) we notice the audio lags behind the video 6 to 10 seconds.

I saw the article about troubleshooting live streaming and I have applied all the recommendations indicated, however the audio delay persists.

What is the meaning of the value of sortBufferSize? is it milliseconds? is it packets? is it MB? obviously, with my large delay of 6 seconds, a 750 ms buffer will not help.

I tried looking for a document that explains this values but can't find one. Can you provide a document that explains all the options for the Application.xml file?

Do you have any ideas or suggestions to try and determine where the audio delay is coming from?

The stream is currently live:

'rtmp://70.33.217.246/live', 'mpegts.stream'
or
'http://70.33.217.246/live/mpegts.stream/playlist.m3u8'

Thank you,

Hector

[HectorH]

I'm using Wowza Media Server 2 Subscription 2.2.3.04 build26774

It may be unrelated but the error log shows the following:

CupertinoPacketHandler.handlePacket[live/_definst_/mpegts.stream]: Timecode out of order [video]: 2474340:2474347
CupertinoPacketHandler.handlePacket[live/_definst_/mpegts.stream]: Timecode out of order [video]: 107:113
CupertinoPacketHandler.handlePacket[live/_definst_/mpegts.stream]: Timecode out of order [video]: 17457:17464

[HectorH]

Is the fix in this article relevant to my situation?

12210-A-V-Synchronization-with-RTP-Source

[rrlanham]

It may be an encoding problem with AAC. The sample frequency is slightly off. There is a way to turn on debugging in Wowza to see if this is the case:

http://www.wowzamedia.com/forums/sho...-packetization

Richard

[HectorH]

After activating the AAC timecode debugging, Wowza support was able to spot the timeclock errors, as such, this points to an error on the encoder side. I will now contact Elecard for support.

Thank you Wowza!