SWFObject 2.2 / Object code for Streaming Servers ?


I'm experiencing issues with JWplayer and IE.
(I can stream my files in Chrome, Firefox but in IE JWplayer doens't respond!)
For that reason i'm trying to create an object code which contains code for SWFObject 2.2 and hope that IE will accept this code.

Downloaded, unzipped it and placed it as a new file in my /mediamosa/mmplayer directory. It's accesible from my browser.

It try with some help of de documentation of SWFObject and JWplayer to make it work but i only get: This div will be replaced.

It looks like the code isn't responding at all, does somebody has experience with using SWFObject 2.2 instead of the standard 1.5 ?

Using the new attributes for file, streamer and type is the next challenge but for now even this wont work. I should get just a JWplayer that does nothing...(?)

<script type='text/javascript' src='http://job1.mediamosa.uvt.nl/mmplayer/swfobject2-2.js' ></script>
This div will be replaced
<script type="text/javascript">
swfobject.embedSWF('http://job1.mediamosa.uvt.nl/mmplayer/jwplayer/player.swf' , 'flashContent' , '300' , '250' , '9' , 'false');

If anybody got the solution for the JWplayer IE bug thats also welcome :)
My working code for chrome and firefox is:
<script src='http://job1.mediamosa.uvt.nl/mmplayer/swfobject.js' type='text/javascript' ></script>
This div will be replaced
<script type='text/javascript'>
var s1 = new SWFObject('http://job1.mediamosa.uvt.nl/mmplayer/jwplayer/player.swf','mpl','{WIDTH}','{HEIGHT_PLUS_20}','9');
s1.addVariable('type', 'mp4');



Hi Joost, Did you take a look

Hi Joost,

Did you take a look at the SWFObject 2.x example for JWplayer on

In IE you can find debug or error messages in the javascript console. These might be helpfull in locating the problem.
(via Developer tools F12 -> script -> console)

use jwplayer.js

Hi Joost!

why don't you goo with jwplayer.js and enable the fallback from flash to HTML5 (if U are using mp4)

our code is:
<script type='text/javascript' src='https://yourdomain.name/mmplayer/player.js'></script>
You need flash player, or use a browser that can play mp4 video using HTML (chrome&IE)
<script type="text/javascript">
'id': 'playerID',
'width': '715',
'height': '485',
'skin': 'https://yourdomain.name/mmplayer/arnes_skin/arnes_skin.zip',
'controlbar': 'over',
'provider': 'rtmp',
'streamer': 'rtmp://fms.yourdomain.name/mmosa/',
'file': 'v2px/{TICKET_URI}',
'image': '{STILL_URI}',
'modes': [
{type: 'flash', src: 'https://yourdomain.name/mmplayer/player.swf'},
type: 'html5',
config: {
'file': 'http://fms.yourdomain.name/mmosa/{TICKET_URI}',
'provider': 'video'
type: 'download',
config: {
'file': 'http://fms.yourdomain.name/mmosa/{TICKET_URI}',
'provider': 'video'

ps: make sure U have the correct FMS VOD application, the symlink on fms server from v2px to links, and the apache Alias /mmosa /video/mmosa/links on FMS server



Hi Matjaz,

Does your final remark imply you are runnig FMS (Flash Media Server) and Apache on the same server, and FMS is processing rtmp requests and Apache processes http requests? Just want to check because I'm running a similar setup with wowza and apache+mod_h264 combined.

My embed code also depends on the JW embedder (jwplayer.js) and HTML5 mode with flash fallback. It's slightly different:

<div id="{MEDIAFILE_ID}">Loading the player ...</div>
<script type="text/javascript">
function L(B,D){var A=document.createElement("script"),C=document.documentElement.firstChild;A.type="text/javascript";if(A.readyState){A.onreadystatechange=function(){if(A.readyState=="loaded"||A.readyState=="complete"){A.onreadystatechange=null;D()}}}else{A.onload=function(){D()}}A.src=B;C.insertBefore(A,C.firstChild)};

L("//yourdomain/mmplayer/jwplayer.js", function() {
var skin_height = {HEIGHT} + 38;
height: skin_height,
width: {WIDTH},
image: "{STILL_URI}",
skin: "http://yourdomain/mmplayer/skin/uva.zip",
modes: [
{ type: "html5",
"controlbar.position": "bottom",
config: {
file: "http://yourstreamer/ticket/{TICKET_URI}"
{ type: "flash",
src: "http://yourdomain/mmplayer/player.swf",
config: {
file: "{TICKET_URI}",
streamer: "rtmp://yourstreamer/ticket",
provider: "rtmp"

- Used MEDIAFILE_ID as id in div. In the case of including multiple videos on the same page the id's might interfere. Still possible however but it is less likely to include the very same video twice on a page.
- Used a loading script L() to dynamically load the jwplayer.js script. This is done to be able to request the objectcode via an Ajax call in the client application. The script gets evaluated and the player is placed in the DOM. A static reference such as <script scr="//yourdomain/mmplayer/jwplayer.js"> isn't processed and cannot always be placed in the <head/> of client applications.
- After jwplayer.js is loaded the callback function is executed, which sets up the player.
- jwplayer.js is loaded over protocol-relative protocol-relative URL (http://paulirish.com/2010/the-protocol-relative-url/) so it doesn't give mixed content warnings when script fragment is loaded in https page.
- Used correction in heigth because of specific custom skin.
- When using skins for html5 (javascript) mode be sure to set Cross-Origin Resource Sharing (CORS) Header (http://www.longtailvideo.com/support/jw-player/jw-player-for-flash-v5/12...)

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.