Do you have a test page?
We tested with: http://demo.teleosmedia.com/edmtv/chrome.html and can't see the issue.
The default HTTP timeout is 15 seconds. You can control it by passing an argument to Viblast player config.
We are having the same problem when the server responds with a 304 (not modified) instead of 200 the player needs 15 secondes unitl it begins to play.
viblast.js:48 [16:17:08] [vb] Error(HlsPlaylistManager.cc:86): Cannot get playlist. Response code = -524
viblast.js:48 [16:17:08] [vb] Error(HlsPlaylistManager.cc:137): Getting the playlist will be retried in 2 s.
In your demo the server always responses with a modified header, so the behavior of the player is not the same.
Any Ideas how to solve this?
It seems we have a bug with single quality streams which do not have master playlist.
We will try to fix it ASAP.
Thank you for the feedback.
After further investigation we founded that the issue is related to the latest versions of Chrome. The issue is reported and they are working on the fix.
As a workaround you can set the Viblast Player parameter append-timestamps to true. More about this parameter you can read here.
This will prevent the browser from caching the resource and can be used as a workaround of the issue.
I tried it, but It does not append timestamps to the m3u8 file.
Can you share your test page?
When I try loading player it takes 10 sec to load console shows errors as follows:
This appears to be Chrome viblast.js:48 [12:49:25] [vb] Error(HlsPlaylistManager.cc:86): Cannot get playlist. Response code = -524 viblast.js:48 [12:49:25] [vb] Error(HlsPlaylistManager.cc:137): Getting the playlist will be retried in 2 s.
Then it starts playing without problem