Hi,
I tested using the 404 reply for missing segments and what I see is that Safari reacts to it by trying the same segment on other bitrates, going down and down until it has no more (it asks for media playlist before each segment). Then stops.
The problem with this is that if I have for example a 3 second glitch on the encoder ingest network the same segment on all bitrates is affected and will be missing.
So Safari gets 404 for the segment for all bitrates and quits.
What I would like to know is if there is some implementation that could make Safari not quit but pass to the next segment.
Of course it will have a freeze for some seconds, but I want it to continue after that and make it robust to a missing segment in all layers.
Do you know, before this new EXT-X-GAP tag if there was a way to implement that with Safari, I mean, to signal somehow a gap that would make Safari go to the next segment?
We were trying to use EXT-X-DISCONTINUITY but we also cannot make it work and Safari freezes anyway.
Regards,
Marco