If you are new to jPlayer, check out the Quick Start Guide.
Having problems? Check out the FAQ on the Support page.
Need help with the playlist add-on? Check the jPlayerPlaylist guide.
The media formats that are essential to jPlayer are those that are supported by both the Flash solution and the HTML5 browsers that do not support Flash, such as iOS.
It is important that one of these formats is supplied to jPlayer so that popular browsers will be able to play your media.
After an essential format has been supplied, additional counterpart formats may be supplied to increase cross-browser support of the HTML5 solution.
See the jPlayer({"supplied": "formats"})
option for more details.
One of the following audio formats must be supplied:
Note that, there is little to no benefit in providing both, due to the way support pans out with HTML5 browsers supporting either both or neither.
The following video format must be supplied:
Set the width and height of jPlayer using the jPlayer({size:Object})
constructor option.
The full-screen size is set using the jPlayer({sizeFull:Object})
constructor option.
Note that the background-color may be set using the constructor option jPlayer({backgroundColor:"#RRGGBB"})
The security rules for jPlayer's SWF file have been relaxed using the following code and may be called from any domain.
flash.system.Security.allowDomain("*"); flash.system.Security.allowInsecureDomain("*");
Generally, you will upload the SWF file with the JavaScript file to a directory called "js" on your domain. Use the constructor option jPlayer({"swfPath":path})
to change the path.
Technically, the plugin files may be linked to remotely at jplayer.org.
However, we request that you don't link to the files on jplayer.com, since we do not have sufficient resources to become a CDN just now.
Additionally, the Flash fallback on the remote server would require the use of absolute URLs for all jPlayer("setMedia", media)
URLs.
Attempting to run jPlayer locally on your computer will generate Flash security violations and you would need to enable the local file access using the Flash Settings Manager. See the Flash Player Help for more information.
To develop locally, install a server on your system, such as Apache, to enable a localhost on your computer.
The media supplied must conform with the codecs supported by HTML5 browsers. The essential jPlayer formats (MP3 or M4A for audio and M4V for video) must also conform with the codecs supported by the Adobe Flash plugin.
jPlayer needs to distinguish between audio and video. This is because jPlayer behaves slightly differently for the two different media types. For example, the video needs to be shown. As a result, formats that are containers have an audio and video type included in their abbreviation to make them unique. For example, M4A and M4V are both MP4 files, and jPlayer knows to play them as audio and video respectively.
Since some browsers use the Flash element of jPlayer, the MP3 files used must be encoded according to the browser's Adobe Flash Plugin limitations:
The MP4 file is a container that supports both audio and video. The M4A format is an audio MP4, and the M4V format is a video MP4. The recommended encoding options for standard and mobile browsers are:
The metadata should be at the start of the encoded data, since the Flash solution must have the metadata in order to begin playling. The option for this varies from encoder to encoder, but usually refers to optimizing for either web or streaming. This 3rd party link might help if you are having problems with the metadata: MetaData Mover
The OGG file is a container that supports both audio and video. The OGA format is an audio OGG, and the OGV format is a video OGG. The Vorbis and Theora codecs appear to have full support.
The WebM file is a container that supports both audio and video. The WEBMA format is an audio WebM, and the WEBMV format is a video WebM. The Vorbis and VP8 codecs appear to have full support.
The WAV format is supported by many HTML5 browsers. We recommend that you avoid it though as a counterpart format. The recommended encoding options are:
The Flash FLV file is a container that supports both audio and video. The FLA format is an audio FLV, and the FLV format is a video FLV. The FLA/FLV format is supported by the Flash fallback.
The RTMP protocol uses a Flash Media Server (FMS) to stream media to jPlayer's Flash solution. The RTMPA format is an audio RTMP stream, and the RTMPV format is a video RTMP stream. The HTML solution does not support RTMP.
The M3U8 playlist format is an Apple HLS (HTTP Live Streaming) file. m3u8a for audio and m3u8v for video. This format works well on Apple devices and browsers (Safari), but has limited support elsewhere.
The M3U playlist format is am MPEG URL file. m3ua for audio and m3uv for video.
The flac audio format.
Your domain's server must give the correct MIME type (content type) for all media URLs.
Failure to give the correct MIME type will stop the media from working on some HTML5 browsers. This is a common cause of problems that only affect Firefox and Opera. Other browsers are less strict, but the MIME type should always be checked that it is correct if you having problems getting media to play on any browser.
If you use a common extension for both audio and video media, for example audio.mp4 and video.mp4, then simply use the video version of the MIME type for both of them. ie., video/mp4
On Apache servers, you can use the .htaccess file to set the MIME type based on the file extension:
# AddType TYPE/SUBTYPE EXTENSION AddType audio/mpeg mp3 AddType audio/mp4 m4a AddType audio/ogg ogg AddType audio/ogg oga AddType audio/webm webma AddType audio/wav wav AddType video/mp4 mp4 AddType video/mp4 m4v AddType video/ogg ogv AddType video/webm webm AddType video/webm webmv
Disable GZIP encoding of all the media files. Media files are already compressed and the GZIP will just waste CPU on your server.
The Adobe Flash Plugin will experience issues if you GZIP the media.
Do not GZIP the Jplayer.swf file either. Feel free to GZIP the JavaScript.
Your server must enable Range
requests.
This is easy to check for by seeing if your server's response includes the Accept-Ranges
in its header.
Most HTML5 browsers enable seeking to new file positions during a download, so the server must allow the new Range
to be requested.
Failure to accept byte Range
requests will cause problems on some HTML5 browsers.
Often the duration cannot be read from the file as some formats require that the start and end of the file is read to know its duration.
Chrome tends to be the browser that has most problems if the Range
request is not enabled on the server,
but all browsers will have some issue even if it is only that you have to wait for all the media to load before jumping close to the end.
This problem is known to affect Jetty 6 servers with their default configuration.
A PHP function has been written by the jPlayer community that can serve media files with support for Range requests. See this jPlayer Support Group Post on the topic.
Be careful when trying to restrict access to your media files. The media URL must be accessible over the internet by the user and its response must be in the format expected.
Using the server response to disable the local cache of media can cause problems with some HTML5 browsers. This can cause the duration of the media to be unknown, which will show as a NaN in the duration of jPlayer.
If you do some magic on the backend to make it more secure, them make sure you are accepting the byte Range
requests described above.
Since jPlayer uses Flash on some browsers, the jPlayer <div> must not be hidden. Mobile browsers do not appear to like their HTML5 media being hidden either.
You can change the size of the jPlayer <div> to zero if you want to make it invisible. You should also be careful that any jQuery animations, such as fadeIn() or fadeOut(), are not acting on the jPlayer <div> or any of its parents.
jPlayer will attempt to recover and reconfigure the Flash solution when shown again after being hidden. However, this assumes that you did not issue any commands to jPlayer while it was hidden.
For example, do not do the following:
<head> <style> #jquery_jplayer { display:none; /* Disables jPlayer when using Flash */ } </style> <script type="text/javascript"> $("#jquery_jplayer").hide(); /* Disables jPlayer when using Flash */ </script> </head> <body> <div id="jquery_jplayer"></div> </body>
In order to eliminate cross site scripting (XSS), there are some limitations placed on the
{noConflict}
option and on the ID name of the jPlayer element.
These restrictions are due to the communication between the Flash fallback and the JavaScript in the page,
which require the jQuery variable name and the ID of the jPlayer element.
This exposed a potential vulnerability through direct access to the Jplayer.swf file, which has been eliminated through the addition of these rules.
The whitelisted characters are:
A-Z
a-z
0-9
_
-
.
Or in other words, the alpha-numeric characters, underscore, hyphen/minus and period.
The jPlayer data is usually accessed via the event object, since the internal data tends to be updated before events are generated. An example of how a timeupdate event handler can be created through the constructor option is:
$('#jp').jPlayer({ timeupdate: function(event) { // 4Hz // Restrict playback to first 60 seconds. if (event.jPlayer.status.currentTime > 60) { $(this).jPlayer('stop'); } } // Then other options, such as: ready, swfPath, supplied and so on. });
The jPlayer object itself may also be accessed through $('#jp').data('jPlayer')
.
However, since this gives full read/write access to all data and access to all the methods, even the internal methods, this is only recommended for advanced developers.
Reading data is fine, but setting data might have unexpected side effects.
The previous timeupdate event code could be (crudely) emulated using an interval with the following code:
var jp = $('#jp'), jpData = jp.data('jPlayer'); setInterval(function() { // Restrict playback to first 60 seconds. if (jpData.status.currentTime > 60) { jp.jPlayer('stop'); } },100); // 10Hz
See also: jPlayer("option")
jPlayer has been tweaked so that you can now use Zepto instead of jQuery.
Zepto 1.0+ compiled with the data module is required.
If you want to use jPlayer as an AMD module for Zepto, then you will need to edit lines of code in the source. By default, the AMD module has its dependencies set to jQuery, not Zepto. The following is the top of the jPlayer code and you can clearly see the two lines that need to be switched.
(function (root, factory) { if (typeof define === 'function' && define.amd) { // AMD. Register as an anonymous module. define(['jquery'], factory); // jQuery Switch // define(['zepto'], factory); // Zepto Switch } else { // Browser globals if(root.jQuery) { // Use jQuery if available factory(root.jQuery); } else { // Otherwise, use Zepto factory(root.Zepto); } } }(this, function ($, undefined) {
But to avoid presumption... These lines here:
define(['jquery'], factory); // jQuery Switch // define(['zepto'], factory); // Zepto Switch
Change to:
// define(['jquery'], factory); // jQuery Switch define(['zepto'], factory); // Zepto Switch
If you are not using the AMD module, then jPlayer is setup ready to use Zepto. Simply include Zepto in your page instead of jQuery.
Zepto support was officially released in jPlayer 2.4.0
jPlayer requires that two files are uploaded to your server.
jquery.jplayer.min.js
Jplayer.swf
When updating jPlayer, ensure that both files are uploaded from the plugin ZIP, since both files are subject to change.
61KB (Gzip: 14KB)
The plugin's JavaScript file, minified using Uglifier during the grunt build process.
The jquery.jplayer.min.js file should be added to the <head>
of the HTML file after the jQuery JavaScript file.
Below is how to include the JavaScript file using an absolute path, relative to the server root.
<head> <script type="text/javascript" src="//code.jquery.com/jquery-1.11.1.min.js"> </script> <script type="text/javascript" src="/jPlayer/js/jquery.jplayer.min.js"> </script> </head>
14KB
The jPlayer plugin's Flash 10.1 file, compiled by the Adobe Flex 4.6 SDK using the grunt mxmlc module.
This file is used in browsers that do not support HTML5 <video>
and <audio>
.
The Jplayer.swf file must be uploaded to your server. The default location is relative to your current page in a folder named "js".
To modify the location of the Flash file, use the swfPath
constructor option.
Below is how to set the swfPath
to a path relative to the server root.
See the jPlayer({swfPath})
constructor option for more information.
$("#jpId").jPlayer( { swfPath: "/scripts/jPlayer" });
jPlayer's JavaScript source file. This file may be switched with the jquery.jplayer.min.js file. The operation is identical, but the file size is larger.
The JavaScript source is verified using JSHint and the options can be found in the source.
This file is readable by humans, assuming they understand JavaScript and jQuery.
This file is no longer needed, as the Flex compiler is now being used to compile the ActionScript. It is left in the source as you can use it to compile the ActionScript if you choose.
jPlayer's Adobe Flash CS4 Professional editor file. This file can be compiled using Adobe Flash CS4 Professional into the Jplayer.swf file used in the jPlayer plugin. The Jplayer.fla file is not required for jPlayer, and does nothing unless compiled.
This file is empty, except for setting its class to Jplayer.as.
jPlayer's ActionScript 3 source file. The Jplayer.as file is not required for jPlayer, and does nothing unless compiled.
This file is readable by humans, assuming they understand Flash's ActionScript 3.
Contains jPlayer's ActionScript 3 source files for classes used in Jplayer.as. These files are not required for jPlayer, and do nothing unless compiled.
These files are readable by humans, assuming they understand Flash's ActionScript 3.
The jPlayer constructor is applied to the given jQuery selector (normally an ID css selector) and uses the options, if provided. The <div> used by jPlayer should be empty and not used for anything else.
In some cases, the jPlayer div can be placed at the top level of the <body> to help avoid effects on the page corrupting jPlayer's operation. This applies to an audio player that does not use the poster feature of jPlayer.
Note that the most important option is the ready
event handler, which is a function defining the actions to perform once jPlayer is ready for use.
Attempting to issue commands to jPlayer before the ready
event occurs will result in jPlayer raising error events if the Flash fallback is used and commands will be ignored.
The next most important option is the swfPath
element, which defines the path of jPlayer's SWF file. Remember to upload the SWF file to your server!
Options that may be changed using the jPlayer("option", key, value)
method after instancing jPlayer, are indicated by the † symbol.
Event handlers that may be created through the jPlayer constructor options, are not really options. They are event handlers bound to the jPlayer element, with the ".jPlayer" jQuery event namespace, and are included in the options as an easy way to bind a handler to an event. Event handlers that are listed here in the options are indicated by the ‡ symbol.
Object defining any changes to the default configuration of jPlayer.
Function : (Default: undefined) : Defines an event handler function that is bound to the $.jPlayer.event.ready event.
To reference the current instance, use $(this)
.
Generally, it is recommended to use a function here to at least $(this).jPlayer("setMedia",media)
the instance to a valid url ready for use.
The ready event handler is defined at creation to eliminate a race condition between the JavaScript code and Flash code.
Thus ensuring the Flash function definitions exist when the JavaScript code is executed.
The handler is bound with the .jPlayer
namespace.
String : (Default: "js") : Defines the path of jPlayer's Jplayer.swf file. This allows the developer to place the SWF file wherever they choose by using an alternative relative path, absolute path or server root relative path.
The swfPath option may be a path or a URL to the SWF file with extension .swf
.
For example, jPlayer({swfPath:"/scripts/banana.swf"})
where you renamed the Jplayer.swf file to "banana.swf".
Do not rename the .swf
extension, or a path will be assumed.
You can test that your swfPath is correct on an HTML5 browser that supports flash, by using the constructor option jPlayer({solution:"flash, html")
.
An incorrect swfPath will generate $.jPlayer.event.error
events with error type $.jPlayer.error.FLASH
when you issue commands like jPlayer("setMedia", media)
Independent of trailing slash, ie., "myPath/" is the same as "myPath".
The URL given must conform to standard URL Encoding Rules.
String : (Default: "html, flash") : Defines the priority of the html and flash solutions. The default is to use HTML first, with a Flash fallback. Swapping the order to "flash, html"
causes the Flash to be used first, with an HTML fallback.
Depending on the supplied
formats, jPlayer may even use both solutions. For example, using jPlayer as a media player with {supplied:"mp3,oga,m4v"}
would on browsers like Firefox require the Flash solution to play the video media format, while the audio media can be played in the HTML solution.
While you could specify only one solution, we do not recommend that you do it!
The solution picked by jPlayer depends on your brower and the formats in the supplied option.
There is an experimental aurora.js solution, that may be enabled by:
<script src="aurora.js"></script>
<script src="flac.js"></script> <script src="ogg.js"></script> <script src="vorbis.js"></script> <script src="opus.js"></script>
aurora
to the solution
option.
For example, {solution:"html,flash,aurora"}
will put the aurora player solution in 3rd priority.
auroraFormats
option so jPlayer knows which codecs the Aurora solution can play.
For example, {auroraFormats:"wav,flac,oga"}
tells jPlayer the Aurora player can play those formats.
The formats defined should be in the same manner as jPlayers naming convention of the supplied options formats.
For example, the Aurora codec aac.js
enables the jPlayer m4a
format, adding to the {auroraFormats:"m4a"}
option
Remember that the inclusion of the Aurora player solution is experimental,
and only experienced developers should try using it.
The author doubts anyone else will need it, in part due to the Aurora Library needing its internal seek()
method fixed for external library usage.
String : (Default: "mp3") : Defines the formats supplied to jPlayer. The order defines the priority, with the left most format being highest. Formats to the right are lower priority.
See Media Encoding for more details on the formats. See Essential Formats for more details on why some formats are manditory.
Essential Audio formats: mp3 or m4a.
Essential Video format: m4v.
Counterpart formats: webma, webmv, oga, ogv, wav, fla, flv, rtmpa, rtmpv.
All formats in the supplied option must be given in every jPlayer("setMedia",media)
command.
The exception to this rule applies to a Media Player. ie., A player that plays both video and audio.
Both the video and audio formats are defined in the supplied option.
Then use either the video or audio media when using jPlayer("setMedia",media)
command.
(You must give all the audio formats or all the video formats defined in the supplied option.)
The solution
priority dominates the priority of the supplied
formats.
jPlayer works by finding the first working format in a given solution.
So in Chrome with {solution:"html,flash"}
and {supplied:"mp3,oga"}
the mp3 file would play in native HTML, even though Chrome could play either.
The format picked by jPlayer depends on your brower and the solution option.
Essential formats are those supported by Flash and (luckily) by browsers that do not allow Flash. ie., iPad/iPhone
Counterpart formats are supplied to improve x-browser HTML5 media support.
object : Sets the size of the restored screen mode. The defaults depend on whether audio or video formats are supplied. The video defaults are used when both media types are supplied.
Object Properties:
object : Sets the size of the full screen mode. The defaults depend on whether audio or video formats are supplied. The video defaults are used when both media types are supplied.
Object Properties:
Boolean : (Default: false) : Smooths the play bar transitions.
The play bar width changes are animated over 250ms to smooth the change, rather than a step change. This also affects clicks on the play bar, where the bar animates to the new position.
Short duration media benefits the most, since their step changes are the largest.
The 250ms animation period approximately matches the period of the timeupdate event for both the html and flash solutions.
Boolean : (Default: false) : Sets the inital state of the full screen mode.
This option is normally changed through the full screen and restore screen buttons on the interface. The video will be displayed in true full screen mode if supported by the browser, otherwise the display will be full window.
This option affects the jPlayer({cssSelectorAncestor})
element, so that the jPlayer display tracks the GUI display.
Changing the fullScreen
option will change the fullWindow
option to match it.
The exception to this rule is when WebKit Video is being used on iOS, where the fullWindow
option will not be changed.
The full screen mode uses the W3C Full Screen API, which means both the HTML and Flash solutions are displayed using this mechanism. This allows the GUI defined in the CSS to be used over the Flash while in full screen mode. Remember that the Flash has no GUI controls built into it, which is why it is not displayed full screen through the Adobe Flash plugin.
Boolean : (Default: false) : Sets the inital state of the full window mode.
This option is a fallback for when full screen is not available and is set automatically when attempting to go full screen.
In general, you will not use this option and instead use the fullScreen
option to control how the video is displayed.
This option has been left here since you can use the full window system for other uses, where you do not want to activate the full screen code as well.
This option affects the jPlayer({cssSelectorAncestor})
element, so that the jPlayer display tracks the GUI display.
Changing the fullWindow
option will not affect the fullScreen
option,
but may affect the full screen GUI display, since the CSS classes would be changed.
ie., If you were in full screen mode when you unset the fullWindow option.
Boolean : (Default: false) : Enables keyboard controls to enter full screen with audio media.
This option allows key controls to display audio poster images in full screen, which is useful for media players. eg., A player that has both video and audio media in a playlist.
For more information on keyboard controls see the
jPlayer({keyEnabled})
option.
object : Sets the auto-hide options for the GUI in the screen display states.
Object Properties:
String : (Default: "metadata") : Valid values are "none", "metadata" and "auto", which matches the HTML5 draft standard. Use "auto" to preload the file.
Preload is a hint to the user agent, not a command. Some browsers ignore this option.
Number : (Default: 0.8) : Defines the initial volume as a value from 0 to 1.
Boolean : (Default: false) : Defines the initial muted state.
Boolean : (Default: false) : Enabling causes
the volume
option to be shared with other jPlayer instances
that have the globalVolume
option enabled.
Boolean : (Default: false) : By default, clicks on the volume bar are calculated from the left. Setting this option to true, causes the calculation to be from the bottom.
If this option is used, then the following CSS styles are required on the volume bar elements to make them display vertically:
<style> .jp-volume-bar { position:relative; } .jp-volume-bar-value { position:absolute; bottom: 0; } </style>
Boolean : (Default: false) : When true, the remaining time is shown in the duration GUI element.
Boolean : (Default: false) : When true, clicks on the duration GUI element toggles the jPlayer({remainingDuration})
option.
Boolean : (Default: true) : When true and jPlayer({toggleDuration})
is true, clicks on the duration GUI element are not propagated up the DOM.
This can help the operation of the jPlayer({toggleDuration})
option in some designs.
For example, when the duration element is nested inside the seekBar element,
you may not want clicks on the duration affecting the current point being played.
Boolean : (Default: true) : When true, GUI interations are blur()
after executing their action.
When false, GUI interations gain focus()
instead.
For example, when the user clicks on the play button, you may not want the browser to maintain focus on the play button.
This can be for CSS styling reasons, but the primary reason for this option is to improve
accessibility by disabling this feature.
Your skin will need to be designed for the jPlayer({useStateClassSkin})
skin type.
This is important, because the state class skin type does not show and hide the different GUI elements, allowing focus to be maintained after executing actions.
The ARIA user may then navigate to the play button using the standard screen reader controls and execute play, which visually switches to the pause button and maintains focus, allowing the ARIA user to simply press the execute button again to pause. Common screen reader controls are tab to select the element and then Enter to effectively click on it.
Number : (Default: 1) : Defines the playback rate.
Recommend that the jPlayer({defaultPlaybackRate})
matches this value during initilization.
The playbackRate
is only available with the HTML solution.
There is a status
flag to indicate whether the browser has this feature enabled:
status.playbackRateEnabled
.
This is primarily used to show and hide the playbackRate GUI controls,
and will always be hidden if the Flash solution is used.
It appears that Android 4.3 Chrome feature tests as enabled,
but the playbackRate has no effect.
While the GUI predefined cssSelectors and methods have been added to the code, they have not been added to the skin HTML nor CSS. This is because the author feels the operation of playbackRate is not stable enough cross-brower. You, the developer, are welcome to add the control if you see fit. You can model it on the volume HTML/CSS.
The operation of playbackRate
varies cross-browser, with some of the variations including:
jPlayer("setMedia")
resets the playbackRate
to defaultPlaybackRate
(Chrome/Firefox)
playbackRate
to defaultPlaybackRate
(IE9/IE10)
ratechange
event does not occur when
the playbackRate
is reset to defaultPlaybackRate
(Chrome/IE9/IE10)
playbackRate
only take effect when paused.
(iOS 7.0.3)
playbackRate
has no effect.
(Android 4.3 Chrome)
This list is purely some of the authors observations and is likely to change as the browser developers dedicate more attention to this media feature.
Number : (Default: 1) : Defines the default playback rate.
Recommend that the jPlayer({playbackRate})
matches this value during initilization.
Number : (Default: 0.5) : Defines the min playback rate. Primarily for use with the GUI. Hardcoded min of 0.1
Number : (Default: 4) : Defines the max playback rate. Primarily for use with the GUI. Hardcoded max of 16
Boolean : (Default: false) : By default, clicks on the volume bar are calculated from the left.
Setting this option to true, causes the calculation to be from the bottom.
For example CSS see: jPlayer({verticalVolume})
String : (Default: "#000000") : Defines the background color of the jPlayer <div> and the Flash. The string is an RGB hash of the form "#RRGGBB".
String : (Default: "#jp_container_1") : Defines the cssSelector of an ancestor of all cssSelectors. Usually an id selector, which is the outer divider wrapper of the skin HTML.
This GUI wrapper will have classes added to it and removed from it based on the state of jPlayer.
The state class names are defined through the
jPlayer({stateClass})
option.
See also: Predefined CSS Selectors,
jPlayer({fullScreen})
and jPlayer({fullWindow})
Object : (Default: {cssSelector}) : This object defines the selectors used to associate the jPlayer GUI controls and feedback with the HTML in the page.
See also: Predefined CSS Selectors.
Object : (Default: {stateClass}) :
This object defines the class names used by jPlayer to indicate state on the
jPlayer({cssSelectorAncestor})
element.
See also: Predefined CSS Selectors.
Boolean : (Default: false) : Controls how jPlayer uses its HTML GUI skin.
The original skins designed for jPlayer required an HTML element for each control command. For example, there would be a play button HTML element and a pause button HTML element and only one of these would be shown, depending on the state of jPlayer. This lead to HTML control pairs being the norm for most GUI elements, which worked, but over time we discovered this had some rather annoying implications to accessibility.
Example of an original skin: useStateClassSkin = false
<style> .jp-play { background-image: url("play.png"); } .jp-pause { background-image: url("pause.png"); } </style> <div id="jp_container_1"> <div class="jp-play"></div> <div class="jp-pause"></div> </div>
The so called "State Class" skins were developed to improve the accessibility of the jPlayer GUI. The key differences are:
Example of a state class skin: useStateClassSkin = true
<style> .jp-play { background-image: url("play.png"); } .jp-state-playing .jp-play { background-image: url("pause.png"); } </style> <div id="jp_container_1"> <div class="jp-play"></div> </div>
To improve accessibility further, disable the
jPlayer({autoBlur})
feature.
See also: Accessibility.
String : (Default: "jQuery") : Allows the global variable name of jQuery to be set.
This option can be changed to what you require after using the jQuery.noConflict(true)
command.
The jQuery variable name is important for the Flash fallback to communicate with jPlayer's JavaScript.
Due to a security requirement, the variable name given to the new jQuery variable must have the term jQuery
in it.
For example:
var lib = { jQuery: jQuery.noConflict(true) } $('#jp').jPlayer({noConflict: 'lib.jQuery'});
See also: Security Restrictions.
String : (Default: "opaque") : Allows the wmode of the Flash fallback to be set.
Valid wmode values: window, transparent, opaque, direct, gpu
Note that audio players in Firefox 3.6 using the Flash solution will require that the {wmode:"window"}
option is set.
Otherwise, the browser does not put the Flash in the page properly.
This problem does not effect Firefox 4+, nor does it affect video players in Firefox 3.6.
For example, if you used the option setting {supplied:"mp3"}
,
then you must set the {wmode:"window"}
option to ensure Firefox 3.6 instances the Flash solution correctly.
For example, if you used the option setting {solution:"flash,html"}
,
then you must set the {wmode:"window"}
option to ensure Firefox 3.6 instances the Flash solution correctly.
For example, if you used the option setting {supplied:"mp3,oga"}
,
then the wmode
option does not matter, as the HTML solution will be used to play the OGA format in Firefox 3.6.
This problem will be addressed in the future, where supplying only audio formats will change the default wmode value to "window".
Boolean : (Default: false) : Sets the initial loop state.
The loop option works in tandem with the default repeat event handler. Clicks on the GUI repeat/repeat-off buttons, toggles the loop option and then generates a repeat event.
Function : (Default: event handler) : Handler function for the repeat event.
The default repeat event handler works in tandem with the loop option. Clicks on the GUI repeat/repeat-off buttons, toggles the loop option and then generates a repeat event.
Unlike other events, the repeat event has a default handler. The default handler is shown below:
repeat: function(event) { if(event.jPlayer.options.loop) { $(this).unbind(".jPlayerRepeat").bind($.jPlayer.event.ended + ".jPlayer.jPlayerRepeat", function() { $(this).jPlayer("play"); }); } else { $(this).unbind(".jPlayerRepeat"); } }
To change the repeat event handler after instancing jPlayer, unbind the handler and then bind a new handler to the event. Note that the jPlayer namespace is used to only unbind the repeat handler added by jPlayer.
$("#my-jplayer").unbind($.jPlayer.event.repeat + ".jPlayer"); $("#my-jplayer").bind($.jPlayer.event.repeat + ".jPlayer", function() { // Your new repeat handler code });
Remember that you may need to clean up the old handler's actions too. There may still be that ended event handler that the repeat handler generates.
$("#my-jplayer").unbind(".jPlayerRepeat");
The author cannot think of an example where you would want to change the repeat handler after instancing jPlayer, but it has been documented here just in case.
Boolean : (Default: false) : Enables the HTML bridge.
This option enables a bridge that emulates the HTML media properties and events on the jPlayer element. All properties are read only. The majority of the useful media properties are emulated.
Example use with Popcorn.js. Note that this code is for an audio player.
ready: function(event) { if(event.jPlayer.html.used && event.jPlayer.html.audio.available) { // Use the actual HTML media element p = Popcorn('#' + $(this).data("jPlayer").internal.audio.id); } else { // Enable and use the HTML bridge with the Flash fallback $(this).jPlayer("option","emulateHtml",true); p = Popcorn('#' + $(this).attr("id")); } }
Object : Defines the user agent blocklist, which contains regular expressions, which cause the native controls to be used if a match is found.
Native video controls are disabled when audio media is supplied and jPlayer({noFullWindow})
is set if nativeVideoControls found a matched.
The default object is empty:
nativeVideoControls: { // Works well on standard browsers. // Phone and tablet browsers can have problems with the controls disappearing. }
Object : Defines the user agent blocklist, which contains regular expressions, which cause the full-screen and restore-screen buttons to be hidden if a match is found.
The default object is:
noFullWindow: { msie: /msie [0-6]\./, ipad: /ipad.*?os [0-4]\./, iphone: /iphone/, ipod: /ipod/, android_pad: /android [0-3]\.(?!.*?mobile)/, android_phone: /android.*?mobile/, blackberry: /blackberry/, windows_ce: /windows ce/, iemobile: /iemobile/, webos: /webos/ }
Object : Defines the user agent blocklist, which contains regular expressions, which cause the volume controls to be hidden if a match is found.
The default object is:
noVolume: { ipad: /ipad/, iphone: /iphone/, ipod: /ipod/, android_pad: /android(?!.*?mobile)/, android_phone: /android.*?mobile/, blackberry: /blackberry/, windows_ce: /windows ce/, iemobile: /iemobile/, webos: /webos/, playbook: /playbook/ }
Object : Defines the display format of the currentTime and duration times.
The default object is whatever the
$.jPlayer.timeFormat
object is at the time of instancing.
Boolean : (Default: false) : Enables the keyboard controls feature for this instance.
The last instance played has focus. During jPlayer instancing, the first instance with the feature enabled gains focus. Only instances with the feature enabled may gain focus.
The keyboard commands are directed at the jPlayer instance in focus.
See also:
jPlayer({keyBindings})
jPlayer({audioFullScreen})
jPlayer("focus")
$.jPlayer.keys(enabled)
Object : Defines the event.which
key codes and their actions.
The keyBindings object is made up of objects of the following structure:
helloWorld: { // A unique name or override the default with the name. key: 72, // The event.which key code for h fn: function(f) { // f is the instance in focus, which is this instance. // f.status is the status object. // f.play() to execute methods, such as play(). alert("Hello World"); } }
The instance in focus parameter f
relates to the current instance,
since the function is only called when this instance is in focus.
Basically, it is a mechanism for passing through the pointer to this
of the instance.
The this
is the JavaScript object pointer, not the DOM pointer used in the jQuery $(this)
coding.
The key
may be a Number
representing the
event.which
code, or a String
specifying
the KeyboardEvent.key
.
At the time of writing, browser support for KeyboardEvent.key
is limited.
The jPlayerPlaylist add-on adds 3 key controls to the list, [
and ]
keys to move to the previous and next tracks.
The s
key will shuffle the playlist.
The jPlayerPlaylist source code may help you understand how the system works.
The jPlayerPlaylist key bindings are written into its coding. ie., They are not options.
The default object is:
keyBindings: { play: { key: 80, // p fn: function(f) { if(f.status.paused) { f.play(); } else { f.pause(); } } }, fullScreen: { key: 70, // f fn: function(f) { if(f.status.video || f.options.audioFullScreen) { f._setOption("fullScreen", !f.options.fullScreen); } } }, muted: { key: 77, // m fn: function(f) { f._muted(!f.options.muted); } }, volumeUp: { key: 190, // . fn: function(f) { f.volume(f.options.volume + 0.1); } }, volumeDown: { key: 188, // , fn: function(f) { f.volume(f.options.volume - 0.1); } }, loop: { key: 76, // l fn: function(f) { f._loop(!f.options.loop); } } }
String : (Default: "jp") : Defines the Id prefix for jPlayer's internally generated HTML code.
Useful if you have a naming conflict, but it is unlikely that the developer will need to change this setting.
Boolean : (Default: true) : Enabling forces the alerts generated by
jPlayer({errorAlerts})
and jPlayer({warningAlerts})
to be written to the console instead.
When the console is not supported and this option is enabled, no alert will occur.
Alert messages are sent to the console.log() instead of alert().
Boolean : (Default: false) : Enables error reporting through alerts.
See also:
jPlayer({consoleAlerts})
Enable this option to help debug your jPlayer application.
Boolean : (Default: false) : Enables warning reporting through alerts.
Warnings are useful for the developer and will inform you of css selectors that are not found, and some other warning types. Often warnings can be ignored, such as the videoPlay selector not being found with an audio player.
See also: jPlayer({consoleAlerts})
Enable this option to help debug your jPlayer application.
Function : (Default: undefined) : Just like the jPlayer ready event, you can bind a handler to any of the jPlayer Events Types. The events include the HTML5 media events.
You can bind handlers to events like timeupdate
to perform an action when it occurs. See Using jPlayer Events for more information and examples.
Note that eventType itself is not a constructor option. Eg., The ready
constructor option is an eventType.
Warning: The flash fallback does not emulate all events.
Warning: HTML5 media events vary x-browser.
HTML entry, with an example id for jPlayer:
<head> <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4/jquery.min.js"> </script> <script type="text/javascript" src="js/jquery.jplayer.min.js"> </script> <script> $(document).ready(function() { /* Your Code */ }); </script> </head> <body> <div id="jpId"></div> </body>
Code Example #1:
$(document).ready(function() { $("#jpId").jPlayer( { ready: function () { $(this).jPlayer("setMedia", { mp3: "/mp3/elvis.mp3" // Defines the mp3 url }); } }); });
Code Example #2:
$(document).ready(function() { $("#jpId").jPlayer( { ready: function () { $(this).jPlayer("setMedia", { m4a: "/mp3/elvis.m4a", // Defines the m4a (AAC) url oga: "/ogg/elvis.ogg" // Defines the counterpart oga url }); }, supplied: "m4a, oga", swfPath: "/jPlayer/js" }); });
Code Example #3:
$(function() { // executed when $(document).ready() $("#jpId").jPlayer( { ready: function () { $(this).jPlayer("setMedia", { m4v: "http://www.myDomain.com/myVideo.m4v" // Defines the m4v url }).jPlayer("play"); // Attempts to Auto-Play the media }, supplied: "m4v", swfPath: "jPlayer/js" }); });
Code Example #4:
$(function() { // executed when $(document).ready() $("#jpId").jPlayer( { ready: function () { $(this).jPlayer("setMedia", { m4v: "/media/myVideo.m4v", // Defines the m4v url ogv: "/media/myVideo.ogv" // Defines the counterpart ogv url }).jPlayer("play"); // Attempts to Auto-Play the media }, solution: "flash, html", // Flash with an HTML5 fallback. supplied: "m4v, ogv", swfPath: "/scripts" }); });
Code Example #5: Bad Code!
$(document).ready(function() { $("#jpId").jPlayer( { ready: function () { $(this).jPlayer("setMedia", { mp3: "/mp3/elvis.mp3" }); } }); $("#jpId").jPlayer("play"); // BAD: The plugin is not ready yet });
jPlayer is controlled by sending the method name through the $(id).jPlayer()
plugin method.
Methods that are a shortcut/alias to change options using the jPlayer("option", key, value)
method, are indicated by the † symbol.
This method is used to define the media to play. The media parameter is an object that has properties defining the different encoding formats and a poster image.
The jPlayer("setMedia", media)
method must be used to define the media before jPlayer will be able perform other methods like jPlayer("play")
.
All media URLs are converted to their absolute URL.
The converted URLs are stored in the event.jPlayer.status.media
object, even if you supplied relative URLs.
This convertion to absolute URLs fixes a problem with the Flash MP4 player and the m4a/m4v/flv formats being relative to the SWF, not the page.
All formats defined in the constructor option jPlayer({supplied: "f1, f2, fN"})
must be given a valid url to the media encoded in that format.
The exception is when using both video and audio media types in a single jPlayer.
Then either all the supplied
audio formats or all the supplied
video formats must be defined.
The constructor option jPlayer({solution: "s1, s2")
can be used to define the priority of the HTML and Flash solutions used by jPlayer.
jPlayer distinguishes between the media types, and using both video and audio together in a single setMedia
command makes it difficult to determine what actually plays. The decision is based on the priority of solution
and supplied
and the browser being used.
ie., The 1st one supplied
that can work in the solution
, will work, be that video or audio.
The point at which jPlayer begins downloading the media is complicated by changes in the by changes in the W3C HTML5 media spec for the media.load()
method and the media.src
property.
In order for older HTML5 browsers to work with jPlayer, the media.load()
command is still used, where really it should be removed as it is no longer required.
The jPlayer constructor option jPlayer({preload})
is used to control when jPlayer begins downloading new media.
Some browsers will begin the download for the whole media when the preload option is "metadata". Others will require that "auto" is used.
The only way to ensure download does not begin automatically is to use the preload option "none".
Remember that, the media may not download as it depends on the browser you are using.
Mobile browser such as Mobile Safari on iOS 4.2 require a gesture before any media is downloaded or played. ie., The user must press a button to initiate the load or play operations the 1st time.
Any media playing when the command is issued will be paused. The the download may not be cancelled as it depends on whether the browser follows the recent W3C HTML media spec. In practice, except for the first time setMedia is used in the ready event, the setMedia command is followed by a play command which stops the old download. The exception is with the media player, where the old media of different type (audio or video), will continue downloading. Otherwise the iPhone's built in video player hangs when the src is cleared to cancel the download.
The URLs given must conform to standard URL Encoding Rules.
Object : Defines the media format URLs and poster
<track>
element.jPlayer({nativeVideoControls})
option is used
and your target browser support is specific to those with WebVTT support.
Note that only the properties listed are used by jPlayer, so you could store all kinds of other info in the same object if your project works better that way. For example, the title and album names of an audio track. However, we do plan to expand the media object properties in the future Properties may one day include: stream, chapters, subtitles.
Code Examples:
$("#jpId").jPlayer( { ready: function() { $(this).jPlayer( "setMedia", { m4a: "m4a/elvis.m4a", oga: "oga/elvis.oga", webma: "webm/elvis.webm" }); }, supplied: "webma, m4a, oga" );
This method is used to clear the media and stop playback. If a media file is downloading at the time, the download will be cancelled.
After this command is issued, playback commands such as jPlayer("play")
will be ignored and raise error events until after new media has been specified using the jPlayer("setMedia",media)
method.
There are very few circumstances when it is appropriate to use this method. In general when you are changing media, this action is automatically performed.
Using this clearMedia by itself on the iOS iPhone or iPod Touch will corrupt the built in video player if it is open at the time the command executes.
This method has no parameters.
Code Examples:
$("#jpId").jPlayer( "clearMedia" );
This method is used to preload the media before the play command is given.
There is no point using load
if you are going to jPlayer("play", [time])
immediately afterwards, just play
it.
Likewise, with jPlayer("pause", [time])
, if a time greater than zero is given.
This method allows you to selectively preload the files you choose after changing the file using setMedia. If you want all files to preload by default, use the jPlayer constructor option {preload:"auto"}
.
This command is affected by browser and some ignore the command, or require a gesture to initiate it the 1st time.
This method has no parameters.
Code Examples:
$("#jpId").jPlayer("load");
This method is used to play the media specified using jPlayer("setMedia", media)
.
If necessary, the file will begin downloading.
Without the time
parameter, new media will play from the start.
Open media will play from where the play-head was when previously paused using jPlayer("pause", [time])
.
The optional time
paramater will move the play-head position to the time given in seconds.
jPlayer("play", 0)
is useful for forcing play from the start of the track, but is redundant for new media, which always starts from the beginning.
This can be used to jump immediately to a play time afer changing media.
jPlayer will seek to the time given and play when able to.
If issued immediately after a setMedia
command, with the time
parameter, and when the browser is using the HTML5 solution, this command will initially fail and an internal timeout is setup to retry the command every 100ms until it succeeds.
[Optional] Number : Defines the new play-head position in seconds.
If used while downloading, play will begin once the media is seekable to that point.
To make media playback loop, add jPlayer("play")
to the ended event. jPlayer deals with reseting the media to the start in the ended event, so the time
equals zero is not required.
Code Examples:
$("#jpId").jPlayer( { ready: function() { // The $.jPlayer.event.ready event $(this).jPlayer("setMedia", { // Set the media m4v: "m4v/presentation.m4v" }).jPlayer("play"); // Attempt to auto play the media }, ended: function() { // The $.jPlayer.event.ended event $(this).jPlayer("play"); // Repeat the media }, supplied: "m4v" ); $("#jumpToTime").click( function() { $("#jpId").jPlayer("play", 42); // Begins playing 42 seconds into the media. });
This method is used to pause the media.
The jPlayer("pause", time)
can be used to jump immediately to a play-head time afer changing media.
The media will begin downloading, and cue the media ready when able to.
Without the time
parameter, new media that has not been loaded or played will ignore this command.
This avoids downloading the new media when the redundant command is given.
Open media will pause if it was playing, otherwise there will be no effect.
The optional time
paramater will move the play-head position to the time given in seconds and if necessary, the file will begin downloading.
jPlayer("pause", 0)
is the same as jPlayer("stop")
.
New media will ignore the jPlayer("pause", 0)
commmand until after the media has started loading.
This avoids downloading the new media when the redundant command is given.
If issued immediately after a setMedia
command, with the time
parameter, and when the browser is using the HTML5 solution, this command will initially fail and an internal timeout is setup to retry the command every 100ms until it succeeds.
[Optional] Number : Defines the new play-head position in seconds.
If used while downloading, the play-head will cue once the media is seekable to that point.
Using a jPlayer("pause", 0)
in the ended
event is redundant and should not be used.
Code Examples:
$("#jpId").jPlayer("pause", 10); // Pauses and moves the play-head 10 seconds into the song.
This method pauses all instances except the instance that invoked the command. This is useful in events such as the play event to pause all the other players on the page when an instance starts playing.
See jPlayer("pause")
for more information,
since this is one instance telling another instance to pause.
The play event handler can be defined in the constructor options.
[Optional] Number : Defines the new play-head position in seconds.
Code Examples:
// Bind an event handler to the instance's play event. $("#jpId").bind($.jPlayer.event.play, function() { $(this).jPlayer("pauseOthers"); // pause all players except this one. }); // Same again, but through the options (only the play option is shown) $("#jpId").jPlayer({ play: function() { $(this).jPlayer("pauseOthers"); // pause all players except this one. } }); // Equivalent to "stop others", passing time as zero. $("#jpId").jPlayer({ play: function() { $(this).jPlayer("pauseOthers", 0); // stop all players except this one. } });
This method sends the command to all instances except the instance that invoked tellOthers
.
This method is used internally by jPlayer("pauseOthers")
and by the {globalVolume}
system.
It is made available to the developer, since maybe it is of use in some novel way.
String : Defines the command to be sent. EG., "pause"
[Optional] Function : Defines a function that returns true or false. Executes in the other instance's context. Has the invoker's context passed as a parameter.
function( invoker ) { // The "this" context is the other instance. return this.options.muted && invoker.options.muted; }
[Optional] Mixed : The arguments for the command. EG., 0, 1, "two", 3
Code Examples:
// Equivalent to pauseOthers $("#jpId").jPlayer("tellOthers", "pause", function() { // The "this" context is the other instance's jPlayer object. return this.status.srcSet; });
This method is used to stop the media and reset the play-head to the start of the media.
This command is the same as jPlayer("pause", 0)
.
The method is available so that a stop button can be used in your interface, if you want one.
If issued immediately after a setMedia
command, this command is ignored.
This method has no parameters.
Using a jPlayer("stop")
in the ended
event is redundant and should not be used.
This avoids a fatal bug on Chrome (Win/OSX), where the browser crashes if you were to follow the jPlayer("stop")
with a jPlayer("setMedia")
in the ended
event.
Code Examples:
$("#jpId").jPlayer("stop");
This method moves the play-head to a new position. The primary use is internal to the plugin to handle clicks on the seekBar and move the play-head to the new position.
Note that this only moves the play-head. Whether the media plays from that point depends on its current state. ie., If it was playing, play continues from the new play-head. If it was paused, the media is cued to the new play-head position.
If issued immediately after a setMedia
command, the effect is the same as jPlayer("pause", 0)
, which is ignored.
Number (0 to 100) defining the percentage played when compared to the current percentage seekable.
Only when completely seekable does the percentage relate to the total length of the media.
Most HTML5 browsers have seeking enabled, so the seekable value jumps to 100% when the media starts downloading.
Code Examples:
$("#jpId").jPlayer("playHead", 0); // Move play-head to start. $("#jpId").jPlayer("playHead", 10); // Move play-head to 10% of the seekable length.
This method is used to access configuration information inside jPlayer.
The options are defined in the constructor. Full get access is enabled, where a copy of the option is returned. However you may currently only set a limited number of options after instancing jPlayer. These are indicated by the † symbol. See also, the jPlayer Options.
String defining the option property name. Supports dot notation.
The returned value can is either a Boolean, Number, String, or an Object, depending on the data requested.
Event handlers defined in the constructor are not included, since they can be removed using the ".jPlayer" namepspace.
The new value of the option.
Code Examples:
var solution = $("#jpId").jPlayer("option", "solution"); // Get the solution string, "html, flash" by default. var cssSelector = $("#jpId").jPlayer("option", "cssSelector"); // Get the cssSelector object. var playSelector = $("#jpId").jPlayer("option", "cssSelector.play"); // Get the cssSelector for the play method. var playSelector = $("#jpId").jPlayer("option", "cssSelector").play; // Get the cssSelector for the play method. $("#jpId").jPlayer("option", "cssSelector.play", ".my-new-class"); // Set the cssSelector for the play method. $("#jpId").jPlayer("option", "cssSelector", {play:".my-new-class"}); // Set the cssSelector for the play method. (Can set multiple selectors in the object.) $("#jpId").jPlayer("option", "cssSelectorAncestor", "#my-new-interface"); // Set the cssSelectorAncestor and refresh all associations.
This method is used to gain the focus of keyboard controls without playing.
For more information on keyboard controls see the
jPlayer({keyEnabled})
option.
This method has no parameters.
Code Examples:
$("#jpId").jPlayer("focus");
This method removes jPlayer. All event and interface bindings created by jPlayer are removed. After destroying the instance, a new jPlayer can be instanced on the element.
All event handlers with the .jPlayer
namespace are removed by this method.
This method has no parameters.
Code Examples:
$("#jpId").jPlayer("destroy");
This method is used to control the volume of the media being played.
Note that the initial volume is set through the constructor option: jPlayer({volume}:ratio)
.
The volume can be changed through the option method: jPlayer({option}, "volume", ratio)
.
While muted you can change this value, but the media will remain muted.
Setting the volume to zero is not the same as using mute
. The two systems are independent.
Number (0 to 1) defining the ratio of maximum volume.
Silence: 0
Half: 0.5
Maximum: 1
Code Examples:
$("#jpId").jPlayer("volume", 0.75);
This method mutes the media's sounds.
Note that the initial muted state is set through the constructor option: jPlayer({muted}:Boolean)
.
The mute state can be changed through the option method: jPlayer({option}, "muted", Boolean)
.
Boolean : (Default: true) : The muted state.
Code Examples:
$("#jpId").jPlayer("mute");
This method unmutes the media's sounds.
Note that the initial muted state is set through the constructor option: jPlayer({muted:false})
The mute state can be changed through the option method: jPlayer({option}, "muted", Boolean)
.
Boolean : (Default: true) : The oposite of the muted state.
Code Examples:
$("#jpId").jPlayer("unmute");
jPlayer allows you to change certain options after instancing. These are indicated by the † symbol. All other options must be defined at creation through the constructor options.
Due to the nature of the cssSelector and cssSelectorAncestor options, there are described here in more detail.
This option allows developers to change the cssSelector associations after jPlayer has been instanced on the page.
The cssSelector
method is used with the jPlayer constructor option cssSelectorAncestor
to create associations between jPlayer methods and CSS entities on the webpage.
For example, this enables a play button graphic on the webpage to be associated with the method that executes the play command.
By default, jPlayer uses a predefined set of cssSelectors, where all the css selectors are class selectors.
The strings are added to the end of the cssSelectorAncestor
string, with a space in between. The default cssSelectorAncestor
is an id selector.
By using a single id and a common class structure, multiple instances of jPlayer are easy to add to the page.
The idea is that jPlayer is associated with a unique interface, hence the id, and then the rest of the structure is common, hence the classes.
The method
may only have one selector
associated with it through jPlayer. An existing association will be removed if a new association is given. An empty string clears exisiting associations.
jPlayer uses the ".jPlayer"
event namespace for binding and unbinding methods to CSS entities.
String containing the name of the method to associate with the selector
.
See the predefined cssSelectors for the list of valid method names.
String containing the CSS Selector to associate with the method
.
Usually a class selector. Eg., ".jp-play"
Code Examples:
$(document).ready(function() { $("#jpId").jPlayer( { ready: function () { $(this).jPlayer("setMedia", {mp3: "mp3/elvis.mp3"}); }, cssSelectorAncestor: "", // Remove the ancestor css selector clause cssSelector: { play:"#myOldPlayButton" // Set a custom css selector for the play button // The other defaults remain unchanged } }) // ... Some time later, otherwise you'd just set it in the constructor ... $("#jpId").jPlayer( "option", "cssSelector", "play", "#myNewPlayButton" ); });
This option allows the developers to change the associations after jPlayer has been instanced on the page.
Setting this option causes all the cssSelector associations to be refreshed with the new ancestor. Allowing you to switch between interfaces easily. I am not sure why you would want to do that, but it's here if you need it.
String containing the CSS Selector to associate with the cssSelectorAncestor
Usually an id selector. Eg., "#jp_container_1"
Code Examples:
$(document).ready(function() { $("#jpId").jPlayer( { ready: function () { $(this).jPlayer("setMedia", {mp3: "mp3/elvis.mp3"}); }, cssSelectorAncestor: "#interface-on-the-left" // Define the ancestor css selector }) // ... Some time later, otherwise you'd just set it in the constructor ... $("#jpId").jPlayer( "option", "cssSelectorAncestor", "#interface-on-the-right" ); });
jPlayer communicates with your code via events.
All jPlayer events can have a handler defined using the constructor option of the same name:
jPlayer({eventName:function(e){...}})
Event handlers created by constructor options have the ".jPlayer"
namespace.
We plan to expand the emulation of HTML5 Media events in the Flash.
display:none
setMedia
. Equivilent to the HTML5 Media error event. (Not exactly true... The HTML error event can occur due to decoding errors too.)
jPlayer constructor option jPlayer({errorAlerts:true})
will create alerts when an error event occurs.
jPlayer constructor option jPlayer({warningAlerts:true})
will create alerts when a warning event occurs.
Just like any other event in jQuery, jPlayer events are bound to handler functions using jQuery.bind()
.
To remove an event use jQuery.unbind()
.
Use the $.jPlayer.event object to access event type strings. All events have a jPlayer Event Object with easy access to information at the time the event occured.
All jPlayer events can have a handler defined using the constructor option of the same name.
jPlayer({eventType:handler})
Note that, the event type used in the constructor is the property name of the event, not the event string code.
For example, the event type $.jPlayer.event.ready
has the constructor option jPlayer({ready:handler})
:
Event handlers created by constructor options have the ".jPlayer"
namespace.
Code Examples:
$("#repeat-on").click( function() { $("#jpId").bind($.jPlayer.event.ended + ".jp-repeat", function(event) { // Using ".jp-repeat" namespace so we can easily remove this event $(this).jPlayer("play"); // Add a repeat behaviour so media replays when it ends. (Loops) }); return false; }); $("#repeat-off").click( function() { $("#jpId").unbind($.jPlayer.event.ended + ".jp-repeat"); // Remove the ended events with the ".jp-repeat" namespace return false; }); $("#jpId").bind($.jPlayer.event.play, function(event) { // Add a listener to report the time play began $("#playBeganAtTime").text("Play began at time = " + event.jPlayer.status.currentTime); }); $("#jpId").unbind($.jPlayer.event.play); // Remove all play event listeners $("#jpId").bind($.jPlayer.event.error + ".myProject", function(event) { // Using ".myProject" namespace alert("Error Event: type = " + event.jPlayer.error.type); // The actual error code string. Eg., "e_url" for $.jPlayer.error.URL error. switch(event.jPlayer.error.type) { case $.jPlayer.error.URL: reportBrokenMedia(event.jPlayer.error); // A function you might create to report the broken link to a server log. getNextMedia(); // A function you might create to move on to the next media item when an error occurs. break; case $.jPlayer.error.NO_SOLUTION: // Do something break; } }); $("#jpId").unbind(".myProject"); { // Remove ".myProject" namespace event listeners using standard jQuery method
Pauses all instances of jPlayer on the current page. If using frames, then only the the frame the command is issued in is affected.
This method has no parameters.
Code Examples:
$.jPlayer.pause(); // Pause all instances of jPlayer on the page
This function is used to convert a time, in seconds, to a string formatted in hours, minutes and seconds.
The format of the conversion is defined using the object
$.jPlayer.timeFormat
.
This function is used to format the text jPlayer writes to the css selectors for currentTime and duration,
however, a jPlayer instance uses it own
jPlayer({timeFormat:Object})
option.
String : The formatted time.
Code Examples:
$("#myTime").text($.jPlayer.convertTime(60)); // One minute
By default, this function has been executed with enable
set true.
This generates the keyboard event handler on the document,
which is used to detect key bindings and direct them to the jPlayer instance in focus.
In general, you should not need to use this function. It has been documented since it may be of use if you wish to globally toggle keyboard controls on and off for multiple instances.
For more information on keyboard controls see the
jPlayer({keyEnabled})
option.
When enabled, the keydown.jPlayer
event is bound to the
document.documentElement
element.
Code Examples:
$.jPlayer.keys(false); // Turn off all key controls $.jPlayer.keys(true); // Turn on key controls for instances with keyEnabled set.
This object is used to format the time returned by the function:
$.jPlayer.convertTime( seconds )
The formating is cumulative.
For example, the default settings display the minutes and seconds, so a time that is over an hour value will be added on to the minutes.
In this case, a time of 1 hour 45 minutes and 10 seconds, would display as 105:10.
To make the time display as 1:45:10 then set
$.jPlayer.timeFormatshowHour = true;
This object defines the default value of the
jPlayer({timeFormat:Object})
option.
Code Example:
$.jPlayer.timeFormat.showHour = true; $.jPlayer.timeFormat.sepHour = " hours "; $.jPlayer.timeFormat.sepMin = " minutes "; $.jPlayer.timeFormat.sepSec = " seconds";
This object is the result of a user agent sniffer and gives information for mobile and tablet platforms.
When detected, the properties are true:
Code Example:
if($.jPlayer.platform.tablet) { // Do something for all tablet devices if($.jPlayer.platform.ipad) { // Do something on ipad devices } if($.jPlayer.platform.android) { // Do something on android tablet devices } }
jPlayer has a predefined set of CSS selectors built in. Below are the default associations between the jPlayer method and the CSS selector.
To define custom CSS selectors use the constructor options:
jPlayer({cssSelectorAncestor: "#my-unique-id", cssSelector: {...}})
To change CSS selectors after instancing, use jPlayer("option", key, value)
:
jPlayer("option", "cssSelector", method, selector)
jPlayer("option", "cssSelectorAncestor", selector)
cssSelectorAncestor: "#jp_container_1"
method: "selector"
cssSelector: { videoPlay: ".jp-video-play", play: ".jp-play", pause: ".jp-pause", stop: ".jp-stop", seekBar: ".jp-seek-bar", playBar: ".jp-play-bar", mute: ".jp-mute", unmute: ".jp-unmute", volumeBar: ".jp-volume-bar", volumeBarValue: ".jp-volume-bar-value", volumeMax: ".jp-volume-max", playbackRateBar: ".jp-playback-rate-bar", playbackRateBarValue: ".jp-playback-rate-bar-value", currentTime: ".jp-current-time", duration: ".jp-duration", title: ".jp-title", fullScreen: ".jp-full-screen", restoreScreen: ".jp-restore-screen", repeat: ".jp-repeat", repeatOff: ".jp-repeat-off", gui: ".jp-gui", noSolution: ".jp-no-solution" }
To disable a selector, use an empty string.
cssSelector: { title: "" }
selector = cssSelectorAncestor + " " + cssSelector[method];
For example, the play method's default actual selector is: "#jp_container_1 .jp-play"
In English, this means select the entity with class jp-play
that has an ancestor with the id jp_container_1
.
Remember that ids are unique, while classes are common. An id should only ever be used once in the HTML.
jPlayer represents its state by adding classes to the
jPlayer({cssSelectorAncestor})
.
For example, when jPlayer is playing, the class jp-state-playing
is added to the cssSelectorAncestor,
and it is removed when jPlayer is paused.
These state classes are maintained for both skin types,
irrespective of the jPlayer({useStateClassSkin})
option.
This class state system cannot be disabled.
Do not attempt to disable a state class by using an empty string, since that may break your design by removing all classes on the
jPlayer({cssSelectorAncestor})
.
state: "classname"
stateClass: { playing: "jp-state-playing", seeking: "jp-state-seeking", muted: "jp-state-muted", looped: "jp-state-looped", fullScreen: "jp-state-full-screen", noVolume: "jp-state-no-volume" }
There is currently some duplication in the options for the full-screen classes
stateClass.fullScreen
and sizeFull.cssClass
.
Currently, both classes are added when entering full-screen and removed when leaving it.
The difference being that the size.cssClass
is added when not in full-screen.
The HTML and CSS/Artwork varies from skin to skin. The CSS/Artwork is a designed to work with all of that skin's HTML structures. You should get the HTML structure from the demo ZIP, available on the download page. The PSD files are also available for each skin.
This section is in due for an update. Plan to review this section after the 2.7 release.
See: jPlayer({useStateClassSkin})
and jPlayer({autoBlur})
While the skin conforms with the HTML 4.01 Spec, unfortunately some browsers do not adhere to the spec.
For example, Safari does not include <a>
elements in the tab order.
If you wish to correct this, the <a>
can be replaced with <input>
or <button>
elements.
Using these form elements requires an empty transparent GIF file to be specified for each element, which complicates use when used in dynamic web apps such as WordPress.
The <input>
and <button>
elements also behave differently cross-browser, in particular where Internet Explorer moves the artwork down and to the right when it is clicked on.
For these reason, our standard skin uses the <a>
element.
The accesskey
attribute may be added to each <a>
element to provide access key support.
The use of access keys depends on your target users.
Most users do not even know how to initiate an access key and it varies from browser to browser.
The key itself also needs to be conveyed to the user in some manner.
Since access keys can interfere with the operation of some browsers we have not used the attribute in the default skin.
After invesigation, a clearly labled link is prefered by the majority of screen reader users.
ie., Our play button has the word "play" in the link, even though the text is not visible when using a standard browser.
Compatibility verified with:
† The jPlayerPlaylist add-on requires jQuery 1.7+
‡ Deprecated.
Compatibility verified with:
Compatibility verified with:
Tested using the latest browser release when this jPlayer version was released.
Apple dropped support for Windows in Safari 5.1.7
Compatibility verified with:
Tested using the latest browser release when this jPlayer version was released.
The incomplete implementation of the HTML5 Media Spec on Android 2.3 causes problems with jPlayer's behaviour.
Issues with Android 2.3:
setMedia
is followed by play
.
Take a look at this jPlayer Demo to see a working solution to these issues.
The GUI autohide animations crash the browser.
Issues with Android 2.3.4 and jQuery 1.8.1 and jQuery 1.8.2. Fixed in jQuery 1.8.3
jQuery bug Ticket #12497
The Flash solution in jPlayer has problems playing the MP4 and FLV type formats when the metadata is missing or at the wrong end of the file.
Issues with jPlayer's Flash solution:
jPlayer does not work on the following browsers:
The following Mobile browsers require user gestures to trigger commands that effect media playback.
jPlayer("play")
in the ready event handler.
The browser will ignore the command. jPlayer will simply wait until the user presses the play button.
jPlayer("load")
and jPlayer("pause", time)
Here are details on the supported formats by HTML5 browsers. All browser versions are their latest official release.
Format names relate to the supplied and setMedia format property names used by jPlayer. For example: WEBMA is an audio WebM, OGV is a video OGG, and M4A is an audio MP4. For more details on the formats, see Media Encoding.
An audio WebM file uses the same Vorbis codec as an OGG file.
HTML5 browsers and their supported audio file formats:
The video WebM (VP8) codec is superior to the video OGG (Theora) codec.
HTML5 browsers and their supported video file formats:
HTML5 browsers and their support for audio streams. (Note that, jPlayer's Flash fall-back for non-HTML5 browsers works with MP3 streams.)
Audio streams work on:
Audio streams fail on:
Some links to resources about HTML5 video and audio support: