Thanks Charlie. Glad to hear that Wowza could stream at a faster rate than the encoded rate so that it can fill player buffer without impacting on time to start the stream.
I will try this with jw player.
jw player has buffer change after starting with small buffer. This is done to avoid long start delays. I am not sure whether jw uses NetStream.bufferTime value.
I have noticed that they are changing the small start-up buffer to a larger one after the stream start in RTMPModel.as. And then, when user interacts, it reduces to the original start-up-delay buffer (model.config[‘bufferlength’]). They are using stream.bufferTime to adjust the buffer after the start-up. I am wondering whether this should be changed to NetStream.bufferTime.
What would occur when this buffer is full. Would JW maintains a FIFO buffer on a sliding basis so that Wowza can keep it full until it is used to fill the write buffer in case of bandwidth fluctuations?
I could observe that it is almost not using an extra buffer to insulate the stream from bandwidth fluctuations. It appears that youtube is better insulated from bandwidth fluctuations in comparison to a Jw/Wowza rtmp stream.