-
Hey Eduard
Wanted to know if we can have it so people can only upload mp4 files(like an option in WP to select this)
Also, we are currently trying to use the WP Offload to S3 Pro plugin alongside your media player & was wondering if you knew what could be causing this error. Currently, when we upload a new file with the plugin enabled, it will go ahead and auto switch the URL so videos stream off of Amazon S3. However, if we try to use the Migrate Old Media to S3, it does not replace our old video URLs with the updated amazon URLs, the video is still coming from the server. The developer of the plugin mentioned:
“It looks to me that FV Player Pro isn’t using the standard WordPress API for getting a Media Library item’s URL, you should probably contact the authors of that plugin to see whether they use the
wp_get_attachment_url()function or similar, as it looks like they always retrieve the local URL instead.”Are there any solutions regarding this?
Thanks!!Ryan
-
-
Hello Ryan,
it looks to me like you created some custom functionality for your website around FV Player, which handles the file uploads and then shows them with FV Player. Could you please confirm?
How are you passing the video URL to FV Player? Do you just create a [fvplayer…] shortcode with the URL in it? Seems to me you should be doing that dynamically with wp_get_attachment_url() as the WP Offload to S3 Pro authors suggested. The code might look like the second code sample in FV Player API guide: https://foliovision.com/player/advanced/api-programming
We are reworking the way how FV Player stores the video information. There will be a set of database tables with the player properties, video information and video meta information. We can certainly let the WP Media Library items hook to the player via their IDs rather than URLs there. In fact, is the src parameter in [fvplayer] shortcode has a numerical value, it could just load that media item.
Thanks,
Martin
Hi Ryan’s Teammate,
You wrote:
Our largest issue is it’s a website where users can publicly upload, so people are definitely not rendering it in several different codecs for the best options. So we were curious if you had any server-side solutions? And if so how much something like this could run?
I’d suggest you piggyback on Vimeo’s API and keep the videos there. It’s much simpler infrastructure than Amazon AWS. We do have some experience with Elastic Transcoder of course. We’d be delighted to create either a Vimeo Pro upload solution or an Elastic Transcoder safety net for you.
Making the web work for you, Alec
Hi Ryan,
An automated workflow of uploading, archiving and transcoding to a single clean .mp4 file which your site would serve would take us two days which normally would be $3200. As I’d like to do this project, I’m happy to give you a 25% discount, i.e. $2400.
A Vimeo implementation would be easier, just a day of coding so $1500. The plus with Vimeo is that there’s less long term maintenance and a lot more infrastructure built out into the API if you decide you want extra features later.
You can have all the control over content and advertisements you want when using Vimeo Pro. It’s just a hosting platform with files. The two downsides of Vimeo Pro:
1. you can’t really get away with illegal or heavily pornographic content. There’s no reason you would shut down right away but you’ll have to worry about at some point being flagged if someone figures out you are using Vimeo hosting and complains.
2. the DRM protection is not as extensive as Cloudfront.But at $200/year for unlimited hosting with a working API and CDN all over the world, Vimeo Pro is a steal.
Let me know.
Making the web work for you, Alec
