Closed brian6932 closed 4 months ago
Jumping back in time is a bug unless the request times out and it rewrites the segment. I do know of a bug where streams with lower view counts can repeat segments for some reason, I've been trying to track that down for a while. fixed
Jumping forward in time is to be expected since this isn't (yet?) a full HLS parser and can't really handle that. not anymore
Seems like e7f47b6055d429c0d1f9708d6fa200ac17b20760 fixed the Dropped (output)
frames, but I do still get the same errors logged to console sometimes
I'm seeing it jump forward but not backwards anymore. Might be time to write a full HLS parser.
Should be better now? It should only jump ahead now if it can't find the next segment.
When piping into mpv I often get the following errors
I'm not doing any proxying
I don't experience it when opening the hls playlist directly in mpv, or when using streamlink
It also seems that whenever this gets logged, some(output)
frames get dropped in mpv, no matter the settings used