• OSMF.swc - directly built from the latest OSMF source @ svn://svn.code.sf.net/adobe/osmf/svn/osmf/trunk/framework/OSMF
• SMPLibrary_NoLogging.swc - built as a library from the Strobe Media Playback source @svn://svn.code.sf.net/adobe/osmf/svn/osmf/trunk/player/StrobeMediaPlayback with disabled logging (for performance gains)
• MASTPluginLibrary.swc - built as a library from the MAST Plugin source @svn://svn.code.sf.net/adobe/osmf/svn/osmf/trunk/samples/MASTPlugin w/ bundled VAST (svn://svn.code.sf.net/adobe/osmf/svn/osmf/trunk/samples/VASTLibrary ) and VPAID (svn://svn.code.sf.net/adobe/osmf/svn/osmf/trunk/samples/VPAIDLibrary ) libraries

Therefore the upstream compatibility is preserved, with only a couple of exceptions (the core SMP, JavaScript bridge and VAST media processing classes) that had to be augmented/replaced in order to make it work as the OSMF is not as extendable as Adobe would have you believe. I've attached the built release version of the player with this email, so unless you want to build it yourself you can use it for your testing purposes. You can see live examples of it at http://www.whitecitysoft.com/sx/mbrix_mast/tmobile.html andhttp://www.whitecitysoft.com/sx/mbrix_mast/vita.html , and you can use http://www.whitecitysoft.com/sx/mbrix_mast/MBPlayer.html as a template for embedding the player (it uses the SWFObject libary, but you can build the tags any which way you prefer).

That being said, I'll try to summarize  bellow the usage basics that should cover your use cases so that we can decide on what needs to be changed/added in further upgrades.

First of all, since it comes bundled with the MAST plugin, the main point of entry for serving ads is a MAST structure - the standard is open and you can read more about it @ http://openvideoplayer.sourceforge.net/mast/mast_specification.pdf . It essentially replaces the structure you were using for the OVA configuration 'til now, but for a quick look of the basic MAST structure you can check the Vita example @http://www.whitecitysoft.com/sx/mbrix_mast/mast/vita.xml - for the most basic setup, just replace the VAST source entry with another VAST entry and it should do it. If needed be, I can create a dynamic MAST structure generator to feed to the MAST Plugin stack based on passed variables from HTML/JS.

To make a MAST/VAST structure load into the player, you need to declare two variables passed as FlashVars to it:

• src_namespace_mast (String) - declares a special namespace for the MAST structure source
• src_mast_uri (String) - location to the MAST file to load

You can also use all standard variables (even to load additional plugins) that the Strobe Media Playback provides, listed @http://help.adobe.com/en_US/FMPSMP/Dev/WS3fd35e178bb08cb3-49a02f129f1468bd6-8000.html . Further, I've added three more variables to the stack in order to control the deployment more easily without a need to rebuild the player:

• allowHost (String) - host to allow for cross-scripting, used in mixed HTTP/HTTPS contexts to prevent sandbox errors, the same way we use it in the current build of the JWPlayer.
• policyFilesNum (Integer) - Number of specifically declared crossdomain policy files to load, used for hosts from which Flash has to obtain content that have a crossdomain.xml placed on some other location from the server root.
• policyFile[0 .. policyFilesNum] (String) - A list of locations for the external crossdomain.xml files to load, zero indexed (i.e. ifpolicyFilesNum is set to 2, you need to provide policyFile0 and policyFile1 variables which point to locations of crossdomain.xml files)

To control the player from JavaScript is quite a straight-forward process - you need to obtain the player object from the DOM and then you can call directly a plethora of methods exposed to JavaScript like:

• play(), play2() - Plays the current video (to be on the safe side, you should use play2() method as there are reports of IE panicking when calling play() on a DOM object for whatever reason; same goes for the stop() method as well)
• stop(), stop2() - Stops the current video
• pause() - Pauses the current video
• setMute(true/false) - controls the mute state of the current video
• getDuration() - returns the video duration
• etc.
  

If you need some specific method or functionality, ask and I'll look if it's already provided by the SMP or if should be added on top of it. When it comes to Flash->JS communication, specifically the events, you need to pass additional variable to Flash through the FlashVars calledjavascriptCallbackFunction, containing a name of the method to be invoked in JavaScript, once the JavaScript bridge is established. After that, you can start listening for events using the addEventListener("eventName", "eventCallback") exposed method. Here is a quick example of that:

There is also a plethora of events available, to list the most useful ones: emptied, loadStart, play, pause, waiting, loadedMetadata,seeking, seeked, volumeChange, durationChange, timeUpdate, currentTimeChange, progress, complete.

To see a live example of Player<->JS<->Player interaction with the base SMP player (rules applicable in this player as well), you can check one of the sample pages @ http://osmf.org/dev/1.5gm/hello-world-javascript.html

Happy testing, and get back to me with a list of the things you need from the player so I can plan the further updates.