Hello Bryan,

you can use a CSS like this to control the logo position:

#content .flowplayer .fp-logo {

top: 10px;

right: 10px;

bottom: auto;

left: auto;

}

The above positions it to top right corner. Notice that you have to set the bottom and left attributes to auto. Also, you have to add some element ID to the selector, in the above example it’s #content as that’s what most of the templates use. So you just check what element ID is your template using for one of the wrapping DIV elements.

Thanks,
Martin

Hi Jinobi,

there were some issues with the insert video dialog before, but they were all resolved.

This may be some conflict with some other plugin.

1. Could you please send us a list of your plugins?
2. Could you please open the error console of your browser, then try to insert a video and let us know if any error message pops up in the console? If you are not sure how to use the error console, read the Step 3 of WordPress “Using Your Browser to Diagnose JavaScript Errors” guide

Thanks,
Martin

Hello M.,

it works for us both in Wordpres 3.5 and 3.6. Please let us know what plugins are you using, so we can look for any conflict.

Please also try to visit Settings -> Permalinks and check for your issues again. That will flush the rewrite rules.

Thanks,
Martin

Hello David,

you should try the same video – the one which is making you trouble – in other browser and also on some other computer. Then you will see if your video is not compatible with HTML5, or if there is some strange issue with your computer.

Thanks,
Martin

Hello Wendy,

if you can provide at least a HTML sample of the site (copy the HTML source from the browser and save it as a text file, then send to our email), then we can have a look if it’s some generic issue.

If it’s some problem specific to your site, we can fix the problem for you, just order our pro support.

If it’s a complete custom script which you need for the site, then that’s completely different story. We will be adding a playlist feature into our plugin, perhaps that could help you. Also, here’s a programmer’s guide for our plugin, so you can check how to initialize our player using JavaScript: http://foliovision.com/wordpress/plugins/fv-wordpress-flowplayer/api-programming

Thanks,
Martin

Hello Chris,

I think that it won’t recognize closing of the modal box as user leaving the page, but it should not matter as the user will leave the page anyway.

However you are using Ajax to load the box content, so I’m not so sure about that.

What’s worse is that you are using the audio player. That one unfortunately doesn’t come with Google Analytics support, it only works with video. So we will add support for Google Analytics in audio player too.

If this is important for your work, you can buy our pro support and we will accelerate development of this feature.

Thanks,
Martin

Hello Jason,

version 2.1.34 with this fix and couple of others was released.

Thanks,
Martin

Hello Roger,

this has been fixed, please double check.

1. the video player is placed inside of an element which has no real dimensions. The player is responsive, so it fits into the element. And because none of the elements has real dimensions, it just shrinks.

We have a JavaScript failsafe code for this, so I improved it and now the player is visible with the right size. This could be fixed in CSS too, but it appears some templates are built this way, so we must count on that.

2. the wp_footer() is present, but for not logged in users it was behaving strangely. I had to change the way I’m initializing the variable and now it works.

Tested in Chrome, Safari, Firefox, iPhone.

Thanks,
Martin

Hello Fkuhrog,

please make sure you are using wp_footer() hook in your footer template.

Could you also let us know what is the domain name used in the FV Flowplayer license? I was not able to find you in our licensing system.

Thanks,
Martin

Hello Jason,

sorry about that, it’s really a rookie level mistake. I only tested installing the plugin from scratch and not the upgrading from one of the recent versions.

It’s fixed now and it will go into new version today.

We are happy if you like the plugin. If you could check out what happens if you open a post, then wait for an hour (needs to be longer than the video duration or 15minutes – we want to lower it to 5 minutes actually) or so and try to play it, that would be great. You should get a nice message that you need to reload the page.

Thanks,
Martin

Hello Jason,

we just released version 2.1.32 which has support for Amazon S3 protected URLs.

You can enter your bucket name and API keys in Settings -> FV WordPress Flowplayer -> Amazon S3 Protected Content box.

Then just paste the full file URL as a source of the video, like this:

[fvplayer src="https://s3-eu-west-1.amazonaws.com/flowplayer500600/videos/31-alderbrook-branded-1.mp4"]

When you save the post, the file is examined and the expire time is set to its length, otherwise the default is 5 minutes.

If the site visitor comes to the video later that day and tries to play it, it will fail gracefully – telling him that the video expired and he needs to reload the page.

If you have some time to check this out, that would be great. Now I need to put up a proper documentation for this.

Thanks,
Martin

Hello Peter,

is this also happening with the default template and no other plugins installed?

Does the video on the plugin settings screen play for you?

Does the video on our homepage play for you? http://foliovision.com

Thanks,
Martin

Hello Wendy,

we had a look at the site to see any weird plugin behavior after you sent us information privately:

It works fine for us in Chrome 28.0.1500.95 m on Windows 7 and Windows 8 and on Chrome 21.0.1180.90 on Mac OS X 10.5.8. We can’t reproduce the problem, so it’s hard for us to troubleshoot.

Both videos are MOV and since this format is not officially supported by HTML5, it might be the reason why Chrome has issues playing it (issues on the Films page) or why the fullscreen mode misbehaves.

For troubleshooting, you should:

1. try to replace both videos with this one and see if the problem persists: http://foliovision.com/videos/example.mp4

2. try to save the page as HTML and then try taking out the scripts one by one – if you have some JavaScript programming experience.

Also, don’t forget to listen what the video checker says:

The videos won’t play on Firefox on Windows, as that browser doesn’t like video/quicktime mime type on MOV files, you have to fix it to video/mp4.

Thanks,
Martin

Hello Ramy,

here’s how a typical .htaccess looks like, normally there is no “# Video” section: http://codex.wordpress.org/Using_Permalinks#htaccess_sample

If you edited the .htaccess file properly, our video checker should not report any issues with mime type.

If editing .htaccess doesn’t seem to help, I recommend that you contact your web host – perhaps they are blocking the “AddType” commands in .htaccess.

Also, planosciencetutor.com doesn’t load any site.

Thanks,
Martin

Hello Ramy,

is the admin video checker showing any warnings about bad mime type of the video? Please read its usage instructions in our FV Flowplayer FAQ, it’s the “How to check my video properties using the built-in checker and how to report video not playing” question.

Thanks,
Martin

Hello Peter,

could you please check if:

1. you have any zero width or height attributes in the shortcode, like:

[flowplayer src="...." width="640" height="0"]

2. check the width and height in Settings -> FV WordPress Flowplayer -> Default video size.

Thanks,
Martin

Hello Paul,

we still received some bug reports from Chrome 28, so we just released version 2.1.30, where if the player fails in Chrome due to HTML5 video error, it loads the Flash player automatically and plays in that. The whole process is pretty much seamless.

This should help people who have Chrome which won’t play MP4 files for them – this appears to be a bug in core of Chrome.

Please let us know if you had a browser which had these issues and if it works for you now.

Thanks,
Martin

Hello Jason,

yes, that’s roughly the same experience with Google as we have. They simply provide little or no support for the products.

Your page appears to really use a nice schema.org/VideoObject markup. These tags are metatags, so of course they are not visible. What Google means is that they might not index the video, if the entire video is not visible – so nobody should be able to promote his video by placing it into some hidden HTML on every page or so.

Thanks,
Martin

Hello Empty Mind Films,

we are not sure if we want to include any “pay for the video” feature in our plugin.

We use s2Member (free version available) on our membership sites and it does the job well. So we will put up a quick guide about how to sell your protected pages to users using s2Member and about the added benefit that they do get an user account which then can be used for other purposes. Like they are able to get a lifetime access to videos, buy more videos and so on.

The secure URLs will use Amazon S3 – each URL is only valid for a certain period of time. So you set your videos to “private” and then post them onto a member-only page and that way only members can see the video and if they try to share it, it expires in few minutes.

Thanks,
Martin

Hello Sozo,

could you please use the built-in video checker and send the video details report from there?

The required steps are in “How to check my video properties using the built-in checker” question of our FAQ, just make sure you hit the “Send to Foliovision” after you open the video checker message.

This will allow us to check details of your video file and double check that you are not using the bad mime type for serving of MOV files (Firefox on Windows does not like MOV files with video/quicktime mime type).

Thanks,
Martin

Hello Ted,

we will work full speed on VAST/VPAID right after we finish integration of Amazon S3 signed URLs and playlists. Both are currently in beta testing stage.

Thanks,
Martin

Hello Peter,

perhaps you use some other plugin which also adds Flowplayer JavaScript into the page.

You should check your HTML source of the page where the video is and see if you can find multiple occurrences of flowplayer.min.js or flowplayer.js.

Thanks,
Martin

Hello Wendy,

We are releasing a new version 2.1.27, which automatically disables auto buffering when video is MOV and is opened in Chrome.

However we also noticed that in previous versions the auto buffering was broken. So it will turn itself off after the upgrade as you might waste a lot of bandwidth now that it really works.

Please check our notes in Change Log for more information.

Thanks,
Martin

Hi Paul,

could you please check if you have Settings -> FV WordPress Flowplayer -> Auto Buffering enabled? Could you please check if disabling this helps with your Chrome issues?

Please let us know, hopefully we can finally narrow down to the cause of this issue.

Thanks, Paul

Hello Empty Mind Films,

thank you for the tip!

Setting the “height” should really work, but you must make sure it’s not overruled by some other rule, while there seems to be no other rule for “display”, so perhaps that’s why it works for you.

Thanks,
Martin

Hello Jason,

we decided that we want to see if the schema.org markup actually works before we put it into our plugin. We create a test page for this and will check it again in a week or so to see if our video appears.

We are very interested in the video sitemap. We will see if we can integrate with some other plugin or will make our plugin self-sufficient.

Thanks,
Martin

Hello Jason,

version 2.1.26 was released. It includes improved icons – better visibility on white background.

Thanks,
Martin

Hello HTA,

sorry about the delayed reply.

I’m not sure what feature are you really looking for. Here are features we want to include in the plugin, which might give you just what you need:

• Playlist support – allowing you to put multiple videos into the same player, so you can play them continuously.
• Cuepoints – allowing you to divide the video into subsections and show a list of these – clicking the section name seeks to it in the video

Thanks,
Martin

Hello Empty Mind Films,

1. first of all, we need to figure what is the problem with your video. It takes few minutes to start playing for us (we are in Europe, it might be better overseas).

We put the video on our test site and found that our video checker is not working on it, because it’s too big. This bug was fixed and will be released today.

This bug was caused because we had to switch the video checker from using HEAD request to GET, because Amazon didn’t seem to like using HEAD. However we forgot to exclude the body.

Now here’s what the checker says:

“Bad mime type: Video served with a bad mime type video/quicktime! Firefox on Windows does not like MOV files with video/quicktime mime type. (Please check 4th question in our FAQ)

Error: Meta Data (moov) not found at the start of the file (found at 108,874,353 byte)! Please move the meta data to the start of video, otherwise it might have a slow start up time.

Warning: We recommend that you re-encode your MOV video into MP4 format. MOV is not be 100% compatible with HTML5 and might not play in Google Chrome. Read our article about video encoding“

In short – you really need to re-encode the video into MP4 format, MOV is not a fully supported HTML5 format and there might be issues in different browsers. You need to fix the Moov location anyway, so you might as well re-encode the video. Our article (linked above) contains screenshot of a free application called HandBrake which will do the video encoding for you.

If the video starts playing fast for you, it’s because you have it in browser cache. Or Quicktime cache, if you are on Mac on Safari.

2. Video dimensions – the player container is set to 691px wide and 379px tall. That’s 1.8232 ratio, while video is 1280x720px which is 1.7778 ratio. So you need to set the container to 691x388px and it should be just fine. You can use enter the dimensions into the shortcode, as it works with responsive design.

Just double check if Settings -> FV WordPress Flowplayer -> “Video player size” is set to “Default (responsive)”

Thanks,
Martin

Hello Kingkongdu,

sorry about the delay here.

Please follow the step number 4. from installation instructions here: http://foliovision.com/wordpress/plugins/fv-wordpress-flowplayer/installation

That will check your template and figure out any conflicts.

Please let us know what results you get, then we can help.

Thanks,
Martin

Hi Andrew,

we haven’t found Bluehost to be the most reliable web host, so we would recommend that you check your video buffering speed throughly.

I liked your video, it shows the basics nicely and it certainly makes sense to go through these basics from time to time. I play guitar in a band, but things were going very slowly for a couple of months, so hopefully we recover and play again.

Thank you for your kind words, we are glad if we can help people use our plugin.

Thanks,
Martin

Hello Jason,

thank you for the kind words!

We will update this thread when our own code to deal with secure Amazon URLs is ready, so you can give it a try.

We will probably disable autobuffer for Chrome for these secure Amazon URLs. And also MOV files as it was causing issues in other thread (.mov videos?).

Thanks,
Martin

Hello Wendy,

3. you asked about a platform where you can see this fail. We noticed that Chrome has issues with MOV when the autobuffering is enabled and it seems to affect MP4 too. So perhaps we need to disable the autobuffering in Chrome for MOV and it will be fine.

I wrote about in this support thread here: http://foliovision.com/support/fv-wordpress-flowplayer/troubleshooting/mov-videos#post-1906

And also more recently here: http://foliovision.com/support/fv-wordpress-flowplayer/troubleshooting/mov-videos#post-1982

Thanks,
Martin

Hello Wendy,

1. Your original warning was like this, it listed multiple issues:

Bad mime type: Video served with a bad mime type video/quicktime!  ...



Warning: We recommend that you re-encode your MOV video into MP4 format. ...

So now that you fixed the mime type, the second issue needs to be fixed too:

`Warning: We recommend that you re-encode your MOV video into MP4 format. …`

At least that’s what I was able to notice.

2. We a bit behind on documenting the WebM, as we are actually trying to make the MP4 the single winning format here. Google Chrome promised to remove the HTML5 support for MP4 for some time now, but it’s still there, so this is bit of an open question right now. On the other hand some older versions of Chrome have problems with playback of MP4.

You can use WinFF for WebM (Windows and Linux) or Miro Video Converted (Mac). List of WebM converters can be found here: http://www.webmproject.org/tools/ The settings are similar to HandBrake which is described in the article: foliovision.com/wordpress/plugins/fv-wordpress-flowplayer/encoding

Thanks,
Martin

Hello Wendy,

please read my last message in this thread. There is link to a guide on how to fix mime type on Amazon S3 for multiple files at once.

It does require the access to the Amazon account though. I’m afraid that if you don’t have access, you can’t change it. You can perhaps ask the Amazon S3 support to fix it for you, but they will probably want to make sure you own the account too.

Thanks,
Martin

Hello Jason and Jeremy,

I forgot to add – you really should be using our fix and remove the Jeremy’s hot-fix. Otherwise the Amazon S3 signed URLs won’t work in HTML5 player.

Thanks,
Martin

Hello Wendy,

thank you for the video details submission.

1. You are serving the files with the video/quicktime mime type. This has to be set to video/mp4 as we suggest, otherwise they won’t play in Firefox on PC. I tested it on Windows 8 just now and it was not playing. I also updated our video checker to say “Firefox on Windows does not like MOV files with video/quicktime mime type” instead of just “Firefox does not like MOV files with video/quicktime mime type”.

Full guide about how to fix the mime type on many files on Amazon S3 was posted here, so you can follow that: http://foliovision.com/wordpress/plugins/fv-wordpress-flowplayer/fix-amazon-mime-type

2. Next, we recommend to re-encode the file into MP4 as there might be issue in Google Chrome browser. I was not able to replicate this issue with your video on neither Chrome 21.0.1180.90 on Mac OS X 10.5.8 nor on Chrome 28.0.1500.72 m on Windows 8, but all the technical details of the video look the same as the video which was giving us trouble.

Actually – the Chrome issue only appears when Auto Buffering is set to yes. So we can either only show this warning when auto buffering is on, or always disable auto buffering for MOV videos, or only disable it for Chrome. We are releasing a new version today, this will have to wait however. If you test this, don’t forget to clear your browser cache between tests.

Anyway, MOV is not an official HTML5 format, many players just don’t play it at all, so we don’t recommend it.

Thanks,
Martin

Hello Wendy,

we had issues with MOV videos on Chrome, but not all the time. It appears that the HTML5 player in Chrome has some bugs. And MOV is also not officially supported by HTML5, as it might contain weird codecs, not just the right ones like MP4.

Please post the detailed MOV information (you can use the “Send to Foliovision” feature of the video checker), so we can then check what codecs it is using and figure out if it’s the same troublesome codec which was giving us and Graeme trouble.

Thanks,
Martin

Hello Acel,

sorry about the delay here, we are still working on this.

There are weird issues with MP4 videos on Chrome. It’s mostly Chrome 25 on Linux and sometimes also 26 and 27 on Windows. I appears to be a problem with the Chrome HTTP protocol implementation, you should see that the video stops download in Tools -> Developer Tools -> “Network” tab.

Thanks,
Martin

Hi Jason and Jeremy,

thank to both of you for your input.

Today we worked on adding the Amazon S3 protection support straight in to our plugin but I was not able to replicate your bug yet.

But I’ll have one more look at Jeremy’s code to figure out what could it be that it’s breaking for you.

Thanks,
Martin

Hello David,

Google shut down the Feedburner API: https://developers.google.com/feedburner/

Also there was very little support to Feedburner users once it was acquired by Google. All the Feedburner logins were canceled and you had to login using your Google account and say which feeds belong to your (claim your feeds). It was pretty rough for some of our clients, so we find it difficult to trust this service.

Here’s a full article about what happened: http://foliovision.com/2012/09/zero-feedburner-subscribers-solution

Thanks,
Martin

Hello Chris,

version 2.1.23 with this fix was released.

Please let us know how it works for your M3U8 videos.

Thanks,
Martin

Hello Chris,

thank you for the bug report!

We will fix this and release a new version today.

Flash can be set as a default, but we don’t recommend that, as the HTML5 player in each browser has a better support for seeking when using normal videos served via HTTP.

We recommend that when you put in a M3U8 video, you also provide at least an alternative MP4 version of it.

Thanks,
Martin

Hello Jake,

that sounds strange, perhaps you should ask the Crazy Egg support about how they track these tooltips. Perhaps the data is not accurate, or it triggers automatically for everybody on the website.

Thanks,
Martin

Hello Wendy,

the warning doesn’t stop your video from playing. It’s just a note for you to check your video if it plays. We had issues with the above video format and mime type in Firefox, so we added that one.

If these videos play for you, could you please let us know what operating system and Firefox version are you using? Then we can narrow down our check.

Also, there was no change on the player controls recently. Or do you mean that it’s different from version 1.x? If so, here’s how to add the play/pause button on the control bar:

add_filter( 'fv_flowplayer_attributes', 'tweak_fv_flowplayer_attributes', 10, 2 );

function tweak_fv_flowplayer_attributes( $attrs ) {

$attrs['class'] .= ' play-button';

return $attrs;

}

Just put the above code into the template’s functions.php file.

Thanks,
Martin

Hello Dirk,

we tested how this works.

1. Unfortunately, none of the videos loads for us on iPad once we enable the “Lock files” option of the plugin. It just says “Video file not found”.

It doesn’t matter if we use “Download type” of “Normal” or “fopen”. It doesn’t matter if the actual media item has the access restriction enabled or disabled.

There must be something wrong in the HTTP response headers. I checked these HTTP headers of these files with “Lock files” enabled and disabled. The plugin seems to add following:

Content-Description

Content-Disposition

Content-Transfer-Encoding

2. Another issue is with seeking. You can’t see to a part of the video which is not yet buffered. This works nicely in the HTML5 player, as you can see what’s buffered and what’s not (Safari 5.0.4). However in HTML5 player of Google Chrome (21) if won’t let you seek even in the buffered part.

That’s simply because the file is served via a PHP script (which checks the access restriction) and it doesn’t support range requests (no “Accept-Ranges” in HTTP response headers).

Thanks,
Martin

Hello Graeme,

there should be no big size difference between MOV and MP4. If there is, it suggests that you used bad encoding settings – too much bitrate.

Thanks,
Martin