Wowza Community

Wowza cuts the stream when using ABR / Stream sync with timeline.

Hello. In my company we are developing an online solution based in real time video. Our applications in Wowza have ABR configured, and sometimes we use streams seted with a fixed quality (url…_720p) and other times we just use the standard url without any quality to get the original source.

Our applications have a backend server that manages a wide spectrum of functionalities; we are experiencing difficulties when synchronizing the state of the stream with the signals that we share with the server, specifically in the pause/stop modes.

  • When the transmitter application (the one that generates the stream) wishes to pause or stop, it stops the stream and at the same time sends a pause/stop signal to the server.

  • The receiver application (the many that receives the stream) uses both the state of the stream and the signas from the server to deduct if the stream is effectively paused or stopped.

Now the behaviour of the Wowza streams differ upon if using ABR or not.

  • If the receiver application consumes the original source of the stream without any quality adaptation, the stream will stop when all the video/audio has been delivered; so she can use this alongside with the server state to know that the stream is stopped and act in consequence.

  • If the receiver application consumes a stream using ABR, the stream will NOT contain all video/audio, it will contain video and audio until the emitter has stopped it, the remaining seconds are lost.

In conclusion, my question is if there is any mechanism to know some kind of ‘timeline’ in which to know when the stream started…or when it was stopped; or at least tell Wowza to not cut the remaining stream despite if the emitter has stopped the stream.

Thanks.

Hi,

When there is an unpublish event from your source encoder, the livestream packetizers for the transcoded renditions are subsequently destroyed. Any incoming packets that were queued up for packetization would also be destroyed as well. You can try using a low-latency type of stream in order to minimize this buffer.

Michelle