This release of the JW Player 5.7 focuses heavily on lifting HTML5 support closer to parity with Flash. The most glaring gap had been the lack of support for XML playlists and for a visual playlist UI component. We're happy to announce that those features are now available. Read more to find out what's new.
One of the tools that we've come to rely on quite heavily over the past several years is a web proxy. Frequently, we see support requests come in where a publisher has misconfigured the player by pointing it at a video file or skin which does not exist on their server. Using a web proxy, it's possible to log all requests, making it quite easy to see when requests are failing because the file they're trying to load isn't there. Additionally, since some web proxies allow you to modify requests, publishers can test out new player versions, plugins, or skins without modifying any code on their live site. In this blog post, we'll show you how to use a web proxy called Charles to help you debug your current JW Player configuration and test out new configurations.
The amount of video content on the Internet has exploded over the last few years. This is due in large part to products like the JW Player and services like YouTube and Vimeo. More and more users have come to expect the sites they visit to contain video content. As a result many bloggers are seeing the value in having video content on their site. Not only does it make their site more engaging for their users, it can also be a source of revenue for them through the use of video advertising.
Over the past few months, you may have noticed that an increasing number of items in your Facebook News Feed had a play icon in the bottom left hand corner, like so:
One of the most often asked questions when discussing transcoding is How do I support iPads, iPhones, Blackberries and Android phones?. The goal of this blogpost is to remove some of the mystery behind transcoding for devices and present a solution that will work across a wide range of them.
Many popular video formats, like FLV or WMV, will not play on devices like the iPhone. Even videos encoded in MP4 may not play back, resulting in the following screen:
Error playing video on an iPhone
Publishing a few on-demand videos can be cheap and simple: just upload the videos to your site and use a tool like the JW Player to embed them on your site. Historically, publishing a live stream has been challenging and a lot more expensive.
Is your goal to increase the total number of video views on your site? Are you having trouble ranking high within search engine results? This blog post will present some basic guidelines for achieving this goal — and building a robust Video Sitemap for your site.
One of the most effective ways to drive traffic to your videos, and site in general, is through the use of a sitemap, or in this case, a video sitemap. A sitemap provides search engines with information about your site, and a video sitemap provides information on your videos. In essence, it makes it easier for search engines (i.e. Google) to understand the content of your site, and assign the appropriate rankings.
Prior to the JW 5.3 release, the most common methods used to embed the JW Player on your website were object/embed code and swfobejct (1.5 or 2.X). With the release of JW 5.3, we also introduced our own embed method, the JW Embedder, referenced as jwplayer.js. We recommend the JW Embedder when you’re looking to achieve the following: