We have a service doing some custom encoding and outputting a h.264/AAC transport stream.
I’m serving this stream up to the Wowza server over UDP.
Once in a while we see some complaints in the log about the timecodes jumping back in time. In searching on this, people often attribute this to a loaded network or system. In this case neither is loaded.
Could this error be caused simply by the UDP packets arriving ‘out of order’, or does this indicate some error in the PT of the encoder?
If the former, can the Wowza server accept the TS over TCP?
Thanks,
Chris