Hello Linda,

it seems you are using WP Fastest Cache with PageSpeed on top of it. I would advice you to disable PageSpeed module and see if it helps with FV Player Pro Beta. PageSpeed is something you enabled on server level. It’s not a plugin, so you would have to ask your server admins about it.

If that won’t help, let us know what WP Fastest Cache settings you are using, we can verify if FV Player Pro works with it. I installed the free version of that plugin, enabled “Combine JS – Reduce HTTP requests through combined js files (header)” and it works.

However to fully test this I would have to enable “Combine Js Plus – Reduce HTTP requests through combined js files (footer)” which is only available in the paid version.

Also, you should not be minifying your JS with both PageSpeed and WP Fastest Cache. That just increases complexity of the setup and it’s asking for trouble. So “Minify Js” in WP Fastest Cache should be disabled.

Thanks,
Martin

Hello Linda,

are you able to disable “Force iframe Embedding” now? I can check it for another 2 hours.

Did you noticed any errors on the browser console? Here’s how to get to that console: https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors#Step_3:_Diagnosis Once you have it enabled load the page with your video and play it and see it anything comes up.

Thanks,
Martin

Hello Fzk,

please let us know where we can see these buttons. I don’t see it on YouTube.com when using desktop and I don’t see it on Android mobile either.

We were thinking about adding such buttons to the overlay of the video for mobile as on mobile you can’t tap 10 seconds back as you can with a mouse pointer on a desktop.

Thanks,
Martin

Hello Stuart,

I checked that file and in order to properly analyze it I had to download first 8 MB of it. Then I could see the data about the top level atoms:

ftyp: 24
moov: 4881545
mdat: 2811732700
ftyp (24 bytes)
moov (4881545 bytes)
mdat (2811732700 bytes)

So the moov is placed after 4th MB of the file and since our Video Checker only check first 4 MB of the video file it was not able to find it. We could adjust it to check first 8 MB to work on these long video files, but then it might be slowed down too much on other video files which are not always hosted on some CDN.

So I need to also check if anything changed in HandBrake. Are you sure you are encoding with “Web optimized” checkbox checked?

Thanks,
Martin

Hello Devin,

thank you for your notes.

In the new AB loop design in which we are working on (it will be in FV Player Pro Beta first) the player timeline moves to the top of the controlbar and is aligned with the ab loop bar perfectly. The whole controlbar also moves below the video to make sure the full video can be seen and it’s not covered too much.

We removed the display of the loop start/end time and put it into a tooltip which shows up when you drag the loop end points.

Thanks,
Martin

Hello Davide,

please post the exact [fvplayer…] shortcode you are using and also a link to your page where we can see this behavior.

Thanks,
Martin

Hello John,

thank you for the bug report! FV Player 7.2.6.727 with the fix in it has been released.

Thanks,
Martin

Hello Kim,

FV Player 7.2.6.727 with the fix in it has been released.

Thanks,
Martin

Hello Çapan,

couple more notes – the reason why FV Player loads its scripts in footer is that it’s the best practice (both for HTML structure and site speed), along with setting the scripts to load deferred.

We also only load the parts which are needed. So if your page doesn’t contain and HLS video, we won’t load the HLS.js library, if no popups are used we won’t load their configuration and so on.

So we could set FV Player to load in header, but that way we would have to load HLS.js and all the popups all the time. That way FV Player would init faster on your website, but at the same time loading our scripts in header would slow down the initial page render time.

The solution to that is to use deferred loading. Which might even help with your ad codes which brings us back to where we started – ideally all the scripts should be placed in footer and deferred.

If your ad codes don’t work with deferred loading it’s time to replace them with something else.

I also see you are using Cloudflare’s Rocket loader which might be actually making the situation worse. I would say it’s worth checking how fast FV Player is loaded when that is disabled.

I also see we wait for the document to finish loading before initializing FV Player. Perhaps we can improve that to load players as soon as possible and then check if there are any new players when the document has finished loading.

Thanks,
Martin

Hello Çapan,

are you noticing the same issue when you disable all the ad codes? Perhaps some ad code is loading it a way which prevents the footer JavaScript from executing.

Thanks,
Martin

Hello Leho,

to keep it simple we just set it to open that preview window at fixed dimensions. Fix will be introduced in the next version – 7.2.5.727.

Thanks,
Martin

Hello David,

do you mean that you are using the “Load FV Flowplayer JS everywhere” settings and want to exclude fancyBox from it?

Are you sure you had to remove both JS and CSS? Isn’t it just the CSS file?

Thanks,
Martin

Hello Leho,

thank you for the bug report, I see that you are probably using 100% for the player width and leave the height empty. That must be causing the issue. We will improve the sanitation of these inputs.

Thanks,
Martin

Hello Medal,

I was not able to reproduce the issue on iPad with iOS 12 nor iPhone iOS 11.2.

Are you using FV Player Pro Release or Beta version? Here’s how to check: https://foliovision.com/player/basic-setup/switching-fv-player-pro-to-beta We did some changed regarding YouTube on iOS in FV Player Pro 7.2.2.727.beta.

Thanks,
Martin

Hello Evélina,

next release of FV Player will come with a “Controlbar Fullscreen” setting for the custom skin which will move it to the control bar. It will also be also set that way in the Youtuby skin preset.

Thanks,
Martin

Hello David,

I tried to reproduce the bug, so I installed some plugins. First it was “ARI Fancy Lightbox”. Once it was activated I was getting “fancyBox already initialized” on console, but the lightbox still worked. The styling was a bit off though. That plugin uses fancyBox 3.2.10 while FV Player has 3.4.1, so that could be the reason for the styling mismatch.

Next I tried to use “Easy FancyBox” alongside FV Player. Not only I saw that message again, but also clicking FV Player didn’t open the lightbox at all. So that’s a problem. It was using fancyBox 1.3.23 which is really outdated – I can see 1.3 versions were released in 2010.

Next, “FancyBox for WordPress” is using fancyBox 1.3.8.

What is the fancyBox script version in your theme? Perhaps FV Player needs to detect other plugins loading fancyBox and prevent it. The last two plugins which I mentioned also seem to load fancyBox in a non-standard way, not using WordPress API which is a problem too.

Thanks,
Martin

Hello Nicola,

currently you can only post either single Vimeo videos or Vimeo channels: https://foliovision.com/player/video-hosting/how-to-use-vimeo#adding-video-channel

Please let us know if that solves your issue – can you use a channel instead of a album?

Thanks,
Martin

Hello David,

to update FV Player please click the upgrade link with right mouse button and select the option to open the link in new browser tab. There was a nasty bug like that in last version 6 release of FV Player. So we put in a written message suggesting the above as well. You should be seeing it too.

If that won’t fix the issue, please provide a link to the page where we can see the failure.

Thanks,
Martin

Hello Matt,

since the new lightbox library which FV Player users (fancyBox) has a fullscreen mode we decided to use that if FV Player is in lightbox. That way you can circle through multiple videos or images without having to leave the fullscreen mode of video.

As you are a Pro user I checked a bit deeper into the issue. Could you please reinstall FV Player from this link? https://github.com/foliovision/fv-wordpress-flowplayer/archive/master.zip To do that you will have to first deactivate and delete the current FV Player plugin you are using. WordPress will warn you that you might loose settings and data, but it’s not the case with our plugin, no settings now videos will be lost. Or you can just replace the plugin files via FTP.

That should help with your issue.

Thanks,
Martin

Hello Matt,

how do you hide the player controls? Use controlbar=”no” in the shortcode and you will get a crossed out speaker icon in the bottom right corner of the video which is a good indication of the video being muted.

Thanks,
Martin

Hello Matt,

the behavior which you are describing is correct. Chrome doesn’t permit autoplay videos to play sound. User has to unmute the video manually to hear the sound.

Once user interacts with the video like that Chrome increases the Media Engagement Index (MEI) for the website and will allow audible autoplay for that particular website in the future.

You can find out more about MEI here: https://foliovision.com/2018/05/video-autoplay-issues

Thanks,
Martin

Hello Dwayne,

the JW Player conversion process converts single videos and playlists. It works with the video file URLs.

I see that Syndicaster is something that JW Player supports, but unfortunately FV Player doesn’t work with it.

If it’s a service which you need we could add support for it into FV Player, however since it appears to be dead (no news since April 2015 here: https://www.syndicaster.tv/nab-releases/) it would have to be a custom programming job.

FV Player Pro works with a lot of different CDNs. If you are looking for video encoding and hosting in an attractive package we recommend using Vimeo Pro.

Thanks,
Martin

Hello Medal,

I guess you are asking about the license key – you have to provide the fv_flowplayer_conf JS array which you can check on your WordPress website – similar to what you do with fv_vast_conf.

Same for the YouTube issue – make sure you provide the fv_player_pro configuration JS array from the website which has the YouTube working properly.

Thanks,
Martin

Hello Dan,

I was not able to reproduce the issue on Windows 7 with Chrome 68.0.3440.106. I used the link which you provided.

Thanks,
Martin

Hello Charles,

please check this thread: https://foliovision.com/support/fv-wordpress-flowplayer/how-to/get-the-end-of-the-video

You can check our programming guide here: https://foliovision.com/player/advanced/api-programming#how-to

Thanks,
Martin

Hello comunicazioni,

please let us know if the issue is still happening with FV Player 7 when you got a minute.

Thanks,
Martin

Hello Evélina,

do you mean that when you disabled the Settings -> FV Player -> Sidewide Flowplayer Defaults -> “Fullscreen Button” setting it would not appear anymore on the course landing page, but when loading further lessons with Ajax it would still appear?

We can continue troubleshooting the issue like this or if change your mind and want this fixed in a hurry, we are happy to solve the issue right on your website, just purchase our Pro support.

Thanks,
Martin

Hello Devin,

FV Player Pro 7.2.3.727.beta supports Chromecast for Vimeo videos.

Thanks,
Martin

Hello Matt,

the issue has been fixed in FV Player 7.2.3.727 which has been released now.

Thanks,
Martin

Hello Kiran,

you need to double check the Name for validation as it can be seen on screenshot “Domain validation in ACM” in our guide: https://foliovision.com/player/video-hosting/serving-private-cloudfront

If you can’t get to that anymore, just delete the certificate and request it again.

Thanks,
Martin

Hello Willian,

there was a bug like that in one of the releases. Other way of getting past it was to click the Update link using the middle mouse button. So we put in a hint for it using the update notice:

“Brand new FV Player version. If you can’t upgrade due to a popup dialog saying ‘Are you sure you want to upgrade?’ please open the update link in a new browser tab.”

Thanks,
Martin

Hello Kiran,

you made a mistake there – the record for your video CDN domain needs to point to that Cloudfront domain. For example video-cdn-public.foliovision.com points to d1urvzk1784x0y.cloudfront.net.

The validation works differently, the record name to create is something like (in our case) _5760XYZXYZXYZXYZ.video-cdn-public and then that points to _d37XYZXYZXYZXYZ.acm-validations.aws.

So it seems you got the correct value present but you didn’t get the name right.

Thanks,
Martin

Hello Kiran,

please double check you have set the DNS record properly. Are you sure the value is set to _ee38d64f7XXYYZZ.acm-validations.aws and not _ee38d64f7XXYYZZ.acm-validations.aws.video-cdn.eturnti.com? The trailing dot in that value matters a lot.

Thanks,
Martin

Hello Evélina,

the quality switching labels have no effect on this, that is a special FV Player Pro feature which let you setup quality switching with MP4 videos. It’s not suited for HLS. But we are going to simplify that to offer fixed quality versions for which you have to enter your quality prefixes used in the filenames.

Regarding your issue – for next release we have improved it label 360p as SD if there is some lower quality suitable for mobile. And anything above 540p is considered HD.

Thanks,
Martin

Hello Christos,

so far playing YouTube over Chromecast in FV Player is not supported and there is no way for us to fix it – unless YouTube exposes that API.

Steve, are you also interested in playing YouTube videos over Chromecast?

Thanks,
Martin

Hello Michael,

FV Player Pro 7.2.2.727.beta which fixes this issue is out. To get it you first have to switch FV Player Pro to Beta: https://foliovision.com/player/basic-setup/switching-fv-player-pro-to-beta

Only then it will be available for upgrade.

You can also test on https://foliovision.com/player/demos/youtube-autoplay

Thanks,
Martin

Hello Rich,

the rotation of your image is probably based on the EXIF tag. I’m not s sure why CSS background (which we use in FV Player for player splash screen) is ignoring it.

I think this plugin will fix the issue: https://wordpress.org/plugins/fix-image-rotation/

Thanks,
Martin

Hello Harold,

I can confirm that you can use a shorcode like this to share a fixed URL:

[fvplayer src="https://cdn.foliovision.com/videos/dominika-960-31.mp4" share="https://foliovision.com"]

Thanks,
Martin

Hello encodia,

could you please post your rewrite rules? Install the https://wordpress.org/plugins/rewrite-rules-inspector/ plugin and you should be able to see the following rules:

video-sitemap\.xml$ => index.php?feed=video-sitemap-index

video-sitemap\.(\d\d\d\d)-(\d\d)\.xml$ => index.php?feed=video-sitemap&fvp_sitemap_year=$matches[1]&fvp_sitemap_monthnum=$matches[2]

video-sitemap\.(\d\d\d\d)\.xml$ => index.php?feed=video-sitemap&fvp_sitemap_year=$matches[1]

If solving this issue quickly is important, we are happy to take care of it for you directly on your website, just order our pro support: https://foliovision.com/pro-support We can also help you with further troubleshooting.

Thanks,
Martin

Hello Kevin,

if the issue doesn’t appear when you log in, then it might be some sort of caching. Perhaps you are minifying your CSS and you haven’t cleared that cache since upgrading FV Player.

Thanks,
Martin

Hello Linda,

thank you for your feedback, FV Player Pro 7.2.1.727 is out and it uses MPEG-DASH for Vimeo videos on Android as we have proved it’s more reliable than HLS on these Android phones.

Thanks,
Martin

Hello Linda,

I checked the https://shifttv.eu/shift-s5-ep10/ post in Firefox, Chrome and Safari and found no issues.

I didn’t experienced any problems on Android (5.1.1) nor iOS (11.2).

However since we did experience some issues with certain Vimeo HLS streams on Android 5 we will be switching it to use MPEG-DASH instead. If you are still having playback issues on Android, please switch FV Player Pro to beta: https://foliovision.com/player/basic-setup/switching-fv-player-pro-to-beta If that fixes your issue, then it’s clear that some HLS streams from Vimeo are not suitable for Android and we will make it use MPEG-DASH in the release version too.

Thanks,
Martin

Hello Linda,

please try upgrading to FV Player 7. Make sure you are using FV Player Pro 7 as well. You can always use Settings -> FV Player -> Help -> Rollback if you experience any issues with that upgrade.

That error sound more like a network issue with Vimeo CDN though. Can you get the video on http://foliovision.com to play?

Thanks,
Martin

Hello Marco,

if you can use a HLS stream instead of RTMP, that would be perfect.

But it’s strange that it doesn’t play on mobile. The CORS issue shouldn’t be impossible to figure out.

The Winamp issue is strange. Did you ever install that to your PC?

Thanks,
Martin

Hello Andrew,

please see the above suggestion from Lucia.

Other than than I’m not sure what could be the problem. We used similar popup boxes for years and there were never any issues. Do you get the same problem on a clean website with no other plugins?

Thanks,
Martin

Hello Harold,

I see, our JavaScript is actually putting in that video identifier on purpose.

I think we have an advanced shortcode parameter which let you use a custom URL for the sharing which is what you are trying to achive. I’ll check if the JavaScript code is adjusting that one as well and will let you know.

Thanks,
Martin

Hello bjol,

Google Chrome is making it harder and harder to use Flash. You can see the behavior when you open https://foliovision.com/player/demos/cloudfront-download-protection and try to use the “PLAYER WITH JUST THE RTMP STREAM” player. You will get the “html5: Unsupported video format. Try installing Adobe Flash.” message, even if you have it installed.

To let it run you have to click the “i” or lock icon to the left of the location URL in the location bar. There you will see a drop down menu for Flash, where you need to set it to “Allow” and reload the page.

Thanks,
Martin

Hello Devin,

FV Player Pro 7.2.1.727.beta is out, you should see it available in updates on your site. It enabled MPEG-DASH on Android version 4.4 and above. It requires latest Google Chrome too, I couldn’t get it to work in Chrome 63 for example. So hopefully your users will be able to upgrade and are not on Android 4.3 anymore.

By disabling MPEG-DASH you are only making the videos easier to download on desktop computers and users in Asia might be experiencing slower streaming. You should keep it enabled unless there is some big issues on Desktop computers. And now with the last update on Android too.

Thanks,
Martin

Hello Devin,

the MPEG-DASH option only affect desktop users. The mobile users on Android and iOS will get HLS out of Vimeo regardless of that.

As I said, since some of the HLS streams often fail on Android, we will test how it will perform when using MPEG-DASH, as that’s what Vimeo.com uses on Android anyway.

Thanks,
Martin

Hello Devin,

there is no such option, however FV Player and FV Player Pro 7.2.0.727 which is being released now improves the video loading fallback so that if the HLS fails to play from Vimeo it will go back to using MP4.

We would like to avoid these MP4s, as these are just too easy to download with browser developer tools, which are not available on mobile, but still.

Thanks,
Martin