You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2019. It is now read-only.
Small artifacts at the top of the video player:
– 00:07 (when switching from “Auto” to “160p”),
– 00:37 (720p -> 1080p),
– 00:47 (720p -> 480p),
– 01:56 (720p -> 1080p)
01:17 (160p -> Auto) – almost the whole video
01:34 (240p -> 360p) – half of the video
Also you can test it yourself here – lustery.com/developer/testvideos (carefully – adult content).
Also the problem looks connected with video-dev/hls.js#843, but I'm not sure about that.
What could be the problem?
The text was updated successfully, but these errors were encountered:
can you reproduce the issue in https://video-dev.github.io/hls.js/demo/ ? If so it's most likely indee related to the bug in latest Safari mentioned in the issue thread.
In any case you should use FP 7.2.4 (7.2.5. out soon) with the integrated hlsjs-lite engine and the latest hls.js library.
The only way is to encode your HLS streams in a way that makes the safari mediasource implementation handle them better. Or use native HTML5 playback on safari. And report the problematic streams on the hls.js issue tracker.
Hi. We are using commercial verstion of Flowplayer (v 7.2.1) with HLS plugin (hls light, v1.1.1).
When user changes between HLS sources then periodically appear green artifacts on video player.
I recorded my screen to show you the problem – https://drive.google.com/file/d/1fIk8oVZrY2XP0eioC8R4_AcHbOciwxpT/view.
Artifacts that can be seen in the video:
– 00:07 (when switching from “Auto” to “160p”),
– 00:37 (720p -> 1080p),
– 00:47 (720p -> 480p),
– 01:56 (720p -> 1080p)
Also you can test it yourself here – lustery.com/developer/testvideos (carefully – adult content).
Also the problem looks connected with video-dev/hls.js#843, but I'm not sure about that.
What could be the problem?
The text was updated successfully, but these errors were encountered: