bbb0
Forum Replies Created
-
Forum: Plugins
In reply to: [Flowplayer HTML5 for WordPress] Drive Connectionwhat theme are you using? can you try with a standard theme to see if it makes a difference?
Currently ads do not follow the set rules, there is a 10sec midroll even if there are no ads defined at all for the video, and sometimes they show as a video ad.
Please post a link to an actual webpage showing the problem.
Unfortunately stampederanch.com is currently not reachable from Europe, hopefully this is just a temporary DNS problem.
for this you’ll need the VAST plugin https://flowplayer.org/vast , which should be supported in the next version of the WP plugin.
Forum: Plugins
In reply to: [Flowplayer HTML5 for WordPress] Unsupported video formatThe example link is empty now, can you re-create it please?
To play HLS on PC browsers, you need either Flash or enable the hlsjs plugin (can be set for each video). For the latter, your media server must send the correct CORS headers (see https://flowplayer.org/docs/plugins.html#hlsjs-server-side )
Forum: Plugins
In reply to: [Flowplayer HTML5 for WordPress] Issues with CDNhmm, I can confirm this. Ulrich?
Forum: Plugins
In reply to: [Flowplayer HTML5 for WordPress] Issues with HLS, Android and Skin Settingthe hlsjs error is most likely caused by missing CORS headers from your server. See https://flowplayer.org/docs/plugins.html#hlsjs-stream-compatibility for details. If you can’t set them, disable the hlsjs plugin in the Configuration tab of the video post. There is also an option to set the stream as “live” which should get rid of the 0:00 .
Wrt. Android: not all Android browsers support HLS, with hlsjs you should be able to play it in the majority of current browsers (Chrome, Firefox, Opera, Dolphin) though. If it does not work after fixing the CORS issue, please provide a link to a real test page.
You cannot play rtsp in html5 video tags, so the player does not recognize it as a valid fallback. You could offer a simple to it though; rtsp will open in the Andorid mediaplayer anyway.
you don’t have a valid HLS stream. The m3u8 points to a mp4 file, not .ts fragments. You need to segment the MP4 file and create an appropriate chunklist.
[2016-03-25 10:50.17] ~
[bernd.osiris] ? curl https://stream.creativeconsciousness.com/restricted/video/m1/video1.m3u8
#EXTM3U
#EXTINF:1,Video 1
[video src="https://stream.creativeconsciousness.com/restricted/video/m1/video1.mp4" /]makes no sense anyway, you could just point to the plain MP4…
check the note and links in https://flowplayer.org/docs/plugins.html#hlsjs-assets : Since CORS is http header class, you need to enable them on your webserver.
https://enable-cors.org/server.html has example configurations for various server types, since you seem to be using Apache, https://enable-cors.org/server_apache.html explains the needed changes.
as Ulrich wrote: you need to set the CORS headers required by the hlsjs plugin. The crossdomain.xml is only valid for the FlashHLS component.
Forum: Plugins
In reply to: [Flowplayer HTML5 for WordPress] RTMP Live / Display a default messageyou could adapt the script from https://demos.flowplayer.org/api/live-check.html ; but this would require some custom coding on your side.
Forum: Plugins
In reply to: [Flowplayer HTML5 for WordPress] Logo to fullscreen viewFYI: this will be fixed in FP 6.0.5
the crossdomain.xml is important for playing HLS in the Flash engine.
For hlsjs (play HLS in html5 mode) you _additionally_ need the CORS headers.
sorry no idea how to do this with Wowza. The important point is that each and every request for m3u8 and ts files. I don’t think adding this to the root configuration will hurt though.
Just add the correct CORS header to your media server, see https://flowplayer.org/docs/plugins.html#hlsjs
<?xml version="1.0" encoding="UTF-8"?> <CORSConfiguration xmlns="https://s3.amazonaws.com/doc/2006-03-01/"> <CORSRule> <AllowedOrigin>*</AllowedOrigin> <AllowedMethod>GET</AllowedMethod> <MaxAgeSeconds>3000</MaxAgeSeconds> <AllowedHeader>*</AllowedHeader> </CORSRule> </CORSConfiguration>
Similary to Flash requiring crossdomain.xml, the Javascript based hlsjs needs the headers to play HLS without Flash.
You can forget about the F4M, Flowplayer HTML5 does not support HDS. I’d discourage the DASH stream for now, it only works with Media Source Extensions, ie the same browser technology required as for hlsjs.