We're using our own scheduler and encoder to stream videos to Wowza.
We have a software switch that enables the streamer to stream a playlist of files back to back, so that they don't stop the player, like Flash or VLC between clips.
This works fine with RSTP and RTMP protocols.
But with HTTP streaming (to Apple devices), the first 2 clips in a playlist stream back to back, but the third clip always shuts down the Apple video player in the iPhone. If we have Is there something we can do to make sure the stream keeps playing like it does when we stream from Wowza using RSTP and RTMP protocols?
Look for encoding differences between the clips where the transition fails. Try to eliminate as much difference as possible, ideally they should be exact same video and audio encoding parameters, so the client doesn't know the difference.
Can you run a test on development server that shows this failure: First delete the contents of the current access log, then restart Wowza, then start the stream, then playback on a iOS device until it fails.