I am very new to WOWZA and to streaming. I am using Adobe Flash Encoder on the same box as WOWZA. I am pushing a feed to WOWZA with properties listed below and am sending it to my CDN for delivery of RTMP and HLS. My RTMP is running fine but the HLS users are having an issue where they are watching and at one time they just go back minutes to hours and the feed starts over, even at that time sometimes it does it yet again and this happens over and over. We are a church so we run service 4 times a weekend continuous but the service is new every 80 minutes. We usually dont disconnect and reconnect between times we just open the stream and let it go. Today we had a 3 hour straight event with no breaks and do again tomorrow at 6pm EST Sat. April 20th. Any help would be great.
My CDN team said they see this:
We are investigating the stream and we are seeing a tremendous amount of "NetStream.Buffer.Empty" and “NetStream.Buffer.Full” so they kept invalidating the content for me....Later they said because we stream new events back to back If your encoder will allow you to use unique ts file names, or unique chunks, it would help eliminate this type of issue.
I notice about the same time that people report this issue in the WOWZA window I see cupertino disconnects looks like this:
Also, the cupertino Property settings are in the wrong place. They should be in the /LiveStreamPacketizer Properties container. You have them in a /Streams /LiveStreamPacketizers Properties container, which has no affect.
However, with 2 second key frame frequency the default settings are fine, so that is not your problem.
The connect/disconnect lines are not necessarily a problem.
I don't quite understand the work-flow. Is it the clients streaming from the CDN that are having the problem? Or is it clients streaming from your Wowza server having problems? How are you delivering to the CDN?
The behavior sounds like playback from a vod application. If you push a live stream to a vod application (StreamType "default") you can play it back, but it might jump back as you describe.