-
Greetings,
I’ve decided to try out HLS with FV Player.
Im running Version 7.5.11.727 (and Pro)I’ve created a .m3u8 and .ts compilation, and I can play it via VLC.
I use Digital Ocean, and the bucket is setup is not to allow directory listing. This setup worked for me fo about 2 years. CDN is also turned on and working. (I also tested this setup with streamloader + only authenticated users, and it worked fine.)
Now, when I add the video link in FV Player:
https://bucket.fra1.digitaloceanspaces.com/dir1/dir2/video/prog_index.m3u8
nothing happens: black screen.
I’ve re-checked CDN and permissions. Everything seems to be fine. For the sake of troubleshooting I set the permissions to read:world on the .m3u8 and .ts files.
In dev console I see failed (403 – forbidden) requests going to:
https://bucket.fra1.digitaloceanspaces.com/dir1/dir2/video/
Please note, that this is requesting the directory(which is not going to igve listing), not .ts or .m3u8 files.
In an example, in one for your docs, I saw the same request going to …dir/file.m3u8
In the initiated chain I see that hls.min.js is trying to make that request.
Now, before this 403 request, I also see a request to steam_loader:
https://mywebsite/?stream_loader=101&expire=1642606757&track=1&signature=ad856653e40da909855bee08741f7d8b
If I check the preview of the request, I see the following:
#EXTM3U #EXT-X-TARGETDURATION:10 #EXT-X-VERSION:3 #EXT-X-MEDIA-SEQUENCE:0 #EXT-X-PLAYLIST-TYPE:VOD #EXTINF:10.00000, https://bucket.fra1.digitaloceanspaces.com/dir1/dir2/video/#EXT-X-BITRATE:423?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=SYF7HCV72GHMQCF7QT6N%2F20220117%2Ffra1%2Fs3%2Faws4_request&X-Amz-Date=20220117T153920Z&X-Amz-Expires=7200&X-Amz-SignedHeaders=host&X-Amz-Signature=0cf9b09c5f5b1d00200ed9525af6c38689e54f50db7630c199b2b441445e53bf fileSequence0.ts #EXTINF:10.00000, https://bucket.fra1.digitaloceanspaces.com/dir1/dir2/video/#EXT-X-BITRATE:495?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=SYF7HCV72GHMQCF7QT6N%2F20220117%2Ffra1%2Fs3%2Faws4_request&X-Amz-Date=20220117T153920Z&X-Amz-Expires=7200&X-Amz-SignedHeaders=host&X-Amz-Signature=0cf9b09c5f5b1d00200ed9525af6c38689e54f50db7630c199b2b441445e53bf fileSequence1.ts ...
To me it seems like the URL is broken here, notice the “fileSequence0.ts” is at the end of the URL. Shouldn’t it be like:
https://bucket.fra1.digitaloceanspaces.com/dir1/dir2/video/fileSequence0.ts#EXT-X-BITRATE:423...
?
The original .m3u8 file looks like this:
#EXTM3U #EXT-X-TARGETDURATION:10 #EXT-X-VERSION:3 #EXT-X-MEDIA-SEQUENCE:0 #EXT-X-PLAYLIST-TYPE:VOD #EXTINF:10.00000, #EXT-X-BITRATE:423 fileSequence0.ts #EXTINF:10.00000, #EXT-X-BITRATE:495 fileSequence1.ts ...
What am I missing here?
-
-
Hello Julia,
thank you for reaching out to us!
Do you have CORS headers enabled? If not, here’s how: https://foliovision.com/player/video-hosting/how-to-enable-cors-headers#dos
If that doesn’t help, could you please send us a report via our built-in video checker? https://foliovision.com/player/basic-setup/how-to-use-video-checker
The way the video checker works is that you need to come in as admin and open the video checker and send us a report about the video. It works on desktops.Thanks,
Maria
Hello Julia,
I prepared a fix for Stream Loader for the next FV Player Pro release. We didn’t count on EXT-X-BITRATE tag.
Please deactivate and delete the FV Player Pro plugin you are using, then hit “Install Pro extension” at the top of the wp-admin -> Settings -> FV Player screen. That will reinstall the plugin and will give you the latest version.
Then switch to the Beta release using the steps from here: https://foliovision.com/player/basic-setup/switching-fv-player-pro-to-beta
And finally it should be working for you. Please let us know.
Thanks,
Martin
Thank you Martin,
I already manually stripped EXT-X-BITRATE from my file, and everything started working perfectly. I was a bit confused at first since it’s the official spec since 2018 and I was using the official/latest mediafilesegmenter binary.
On another note, HLS in FV Player does not work (does not start, (stutters, stops, does not load, etc) on devices with M1 architecture (some iPads and newer Macbooks). More info here:
https://github.com/video-dev/hls.js/issues/3834
I’ve manually updates hls.min.js to the latest version (1.1.3), and now everything works perfectly. It might be time to update it in FV Player plugin as well.
Hello Julia,
thank you for the heads up. We are currently experimenting with Apple Silicon M1 and we do run into different issues, but in this case we should just upgrade Hls.js. We only need to double-check the behavior on HLS streams with multiple audio tracks.
Thanks,
Martin
Hello Julia,
we encountered no issues, so Hls.js 1.1.3 will be part of the next FV Player release.
Thanks,
Martin
