hls demux emits eof packets on some tls/ssl errors

[sylware]

My IAP (french "free") hls peering with twitch.tv is accute trash (was fine with SFR IAP). While reading twitch.tv streams, the hls demuxer will generates tons of tls/ssl errors, but with some streams, not all, some tls/ssl errors will generate empty/EOF packets in the middle of valid packets.

Then when I send valid packets after those spurious(?) empty/EOF packets I get the error: non null packet after EOF packet.

Since it is a network quality issue, as a workaround, I do "clean" those empty/EOF packets from the packets queues(video and audio) before trying to read from the hls demuxer again after an error, and playback seems more than fine, namely I do not need to reset/flush the decoders.

This is nasty, because it would seems that if I reset/flush the decoders I will get probably choppy playback. It feels like normal and fine playback is expected to work around in some specific way those network errors.

[Balling]

What OS are you on? If you are on windows executable, it uses schannel (though openssl 3.0.5 already has Apache license and can be used with our GPL, even on windows, just saying).

Schannel is windows backend. As in OS's. Nothing can be done about it.

[sylware]

elf/linux, with libressl 3.5.3. I wildy guess this is related on how the hls demuxer with the https protocols handle extremely bad network connectivity with the hls servers.

[Balling]

libressl was removed even here. ​https://github.com/zhongfly/mpv-winbuild/

​https://github.com/zhongfly/mpv-winbuild/commit/dc723cd03a915da882559dfd2cb484f5d9e60df7