Hi we are uploading videos into s2member-files folder and embed them using [embed] code into our blog posts. They are okay to work on desktop but not on mobile browsers. Why?
If I upload videos into outside of s2member-files folder then they are okay for both desktop and mobile. But why would this be an issue by s2member secure folder?
So you aren’t following the s2Member instructions, and then you wonder why it doesn’t work.
In the instructions it suggests to use jwplayer and cloudfront etc for mobile and rtmp compatibility but i want to it without using amazon cloudfront and s3.
Why do you think it says that? And where does it say to use embed?
At this page:
Mobile Devices: [s2Stream /] Shortcode & JW Player Considerations
Set player_width=“100%” and player_aspectratio=“ww:hh” (not required, but definitely a good idea). Also force the primary player object to html5 which uses a tag if at all possible; as opposed to Flash™ as the default primary that s2Stream uses in order to support RTMP (not required either, but helps prevent issues in JW Player auto-detection).
Mobile Support w/ s2Stream (Example)
[s2Stream player=“jwplayer-v7” player_path="/jwplayer/jwplayer.js" player_primary=“html5” player_width=“100%” player_aspectratio=“12:5” file_download=“video.mp4” /]
See also: Browser & Device Reference
Problems Site Owners Have w/ Mobile Devices
Some site owners try to serve RTMP files on mobile devides, which is not widely supported at this time.
Or, they use the s2Stream shortcode w/o setting player_primary=“html5”. The default primary is flash, and Flash is not widely supported on mobile devices at this time.
Or, they are trying to serve audio/video files from local storage (e.g., from /s2member-files) instead of serving this media via S3 or CloudFront—which is always better. Why? Depending on server configuration, there is always a chance that s2Member’s PHP-based file delivery from local storage may not be compatible with certain versions of Android/iOS. Always better to serve media from a CDN so it can be delivered statically (i.e., what most mobile devices expect to deal with). In short, if you want to support a wide range of devices go with a dedicated media server. That’s what the S3/Cloudfront combination is.
How to Support Mobile Devices (Best Practices)
Host all of your media in an S3 bucket and do not host it locally. Not required but this helps to avoid issues. It’s always better to serve media from a CDN so it can be delivered statically (i.e., what most mobile devices expect to deal with). In short, if you want to support a wide range of devices go with a dedicated media server. That’s what the S3/Cloudfront combination is.
Set player_width=“100%” and player_aspectratio=“16:9” (or whatever aspect ratio is appropriate). Neither of these are required, but this helps to avoid issues.
Set player_primary=“html5” (not required, but this helps to avoid issues).
Don’t use RTMP at all. Or, if you do, use it with an MP4 fallback (e.g., player=“jwplayer-v7-rtmp”). You can use player=“jwplayer-v7” or player=“jwplayer-v7-rmtp”, but please avoid the use of player=“jwplayer-v7-rtmp-only” if you want to support mobile devices; i.e., if you want to support mobile devices you need to allow MP4 as a fallback. Most mobile devices can’t play files over the RTMP protocol.