It seems to me that the problem with the server. Record through the Wowza, so good. The only problem for online viewing. Have to do a ForceReset every 30 minutes.
It seems to me that the problem with the server. Record through the Wowza, so good. The only problem for online viewing. Have to do a ForceReset every 30 minutes.
Take a look at ModuleMediaCasterStreamMonitorAdvanced which will reset as necessary. That would be better than a set reset interval:
http://www.wowzamedia.com/forums/con...onitorAdvanced)
Richard
We have the exactly same issue with our Q1755. Firmware 5.02 and recent 5.20. No difference. I tried to use the StreamMonitor but I can't figure out how to read the loglines and which settings are needed to reset the stream.
I set
streamMonitorAVSyncToleranceEnable=true
streamMonitorAVSyncTolerance=100
Using the videos from
http://editorsean.com/blog/49-audiovideosynctest
I still see much bigger desync and no reset until I stop and restart the player (JW Player 5)
I opened a case with AXIS, too.
Opening a case with Axis is the right direction. Output of the AAC timecode debug method we pointed to should be helpful.
http://www.wowzamedia.com/forums/sho...-packetization
Richard
Well, AXIS tries to play the "Sorry, but there's nothing we can do about that"-gameDo you have any suggestions how I can proof that their devices do something wrong in a way they can not deny? I think Wowza timecode debugging is not possible for them.
Latest Update. AXIS wanted to know if AXIS Media Control (AMC activex component) shows the same drift. Took me a while to get a Windows Box with IE, but no, it doesn't. It claims to use RTP over RTSP over HTTP. Streaming parameters are the same used for wowza. In sync at start and no drift. Not one frame within 30 minutes.
Another update. AXIS told me to check some things. After doing so I finally had time to check the AAC debug output from wowza, too.
The output shows
tc[0]: ...
for some seconds and then ....
tc[8]: 1012784303:1012784295:16000
reset: 16204548720
tc[8]: 1012784359:1012784367:16000
reset: 16204549872
time between the tc[8] differs, but they always appear twice.
Only to understand the technical aspects... why is it that RTSP clients are able to keep A/V Sync while it fails in some other cases like RTMP to flash?
Some clients are able to adjust a/v sync issues and others can't. I think Flash can sometimes (albeit not in your case) while iOS does not.
Richard
Flash Player 11.2 (maybe 11.1) fixed this issue for us. AV-Sync is stable with AXIS now.