Projekktor releases are published spontaneously. This is (still) no full time project so I can´t give guarantees for anything at this point. Nevertheless the project is still under active development and will be at least till end 2012.

If you need a special feature you can buy support. If this is an option for you please feel free to contact me.

In some browsers “Fullscreen” is “full viewport” only because they don´t (yet) support HTML fullscreen. Due to the underlying least common denominator principle Flash- and HTML5- fullscreen are handled the same way.

The file extension it is. Usually OGV is used for ogg/theora encoded video while OGA is for ogg/vorbis encoded audio. For historical reasons sometimes OGG is used instead of OGA and in order to guarantee perfect confusions OGG is also used for OGV. At the end its up to you to clean up the mess.

This is a known issue with some browsers. Some browsers initialize their native players before they fire the contentLoaded or similar event which triggers Projekktor to initialize. As such, if you apply the autostart attribute the affected videos will start playback instantly for a glimpse, stop and the new Projekktor instance is started. This behavior causes some interesting effects but most of time this ends up in a total mess.

To avoid that you should use the autoplay = true config.option of Projekktor itself, e.g.:

 projekktor('#player_a', {
     volume: 0.8,
     autoplay: true
 });

This projekkt is all about HTML5 and future orientated, re-liberalized media delivery and not Flash. Deciding to use HTML5 video/audio (or maybe even Projekktor) is not just choosing an other player. It´s more like a strategic reorientation. “In for a penny, in for a pound.” So, Jarisplayer can be used to stream progressively and has very basic RTMP support. There are no plans to enlarge the feature set of it. If you want to learn why Projekktor uses Jarisplayer and not JWplayer or Flowplayer please check this blog entry: http://www.projekktor.com/blog/2010/11/thanks-for-jarisplayer/

Nevertheless for business users we offer alternate Flash models for both, JWPlayer and Flowplayer. If you are interested in one of them please feel free to get in touch.

The used browser of course. Projekktor should work on IE6 but there´s no guarantee because we do not check this. Building the player for modern environmentsand especially for more recent Internet Explorer´s is painful enough.

<audio> and <video> tags are not natively supported in IE7+8 and Projekktor uses a dirty trick to bypass this. Unfortunately this trick doesn´t work if the tag is wrapped by an other DOM container, make sure it´s a block styled one and under no circumstances a <p>aragraph.

Simply forget it. Autostart video and audio playback doesn´t work on the mentioned devices. This is not a bug but a limitation by Apple. Most likely this is to protect the users from enervating ads and similar spam and to save battery power.

It is true that there are workarounds to force autoplay e.g. on an iPad. But they are what they are: Workarounds to bypass an intended feature. There is no guarantee that they will work after the next iOS update. As such it doesn´t make any sense to be part of this cat-and-mouse game.

This happens thanx to an ancient bug which forces any embedded Flash object to reinitialize in some very special situations. Projekktor unfortunately forces such a situation while expanding the flash fallback component to full viewport. There is a basic workaround implemented but the general issue persists. As such any MP4 and MP3 will restart from the very beginning when ever the user toggles fullscreen. Please refer to bugzilla for detailed information about this.

Most likely you´re using Firefox 5 with Firebug enabled. Just disable Firebug and all is good. Please don´t ask. Took my hours to get the trick.

The video could not be loaded, either because the server or network failed or because the format is not supported.

Firefox´ native player requires proper type header responses by the web server. Some older server setups do not know how to handle the *.oga, *.ogg,. *.ogv and / or *.webm extension. In order to make things work create an .htaccess file in your video / audio directory and hack the following lines into it:

AddType audio/ogg .oga
AddType video/ogg .ogv .ogg
AddType video/webm .webm

In some browsers with native video support this happens if the media delivering web server uses GZIP compression. Usually this compression makes sense only for text based files (CSS, HTML, Javascripts etc.pp.). So you have to check your server setup in order to make sure that at least your media content is NOT being compressed.

If you do not have access to your httpd.conf you can try to bypass this by adding a .htaccess with the following line:

AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/x-javascript

Note that this is a positive list and only text files are compressed now - no video/ogg etc. pp.

Youtube allows its premium users to disable embedding. This feature not only affects the players you can find in blogs or similar but also the ones provided by the Javascript API. The latter one is used to projekktorize Youtube-videos and as such the mentioned option also affects Projekktor. So, in case you stumble upon a “this media can not be…” …something error while using a Youtube video you´ve choosen one which can not be embedded - that´s all.