Maybe I'm looking at something wrong but...When I compare OSMF that comes with Flex 4 with the one on from standalone version from the OSMF download site (opensource.adobe.com) I see that the packages are very different. For example the standalone download of OSMF has an elements package where things like VideoElement (org.osmf.elements.VideoElement) etc. lives, but in the Flex 4 version it lives in (org.osmf.video.VideoElement) . And in the Flex 4 version there is no MediaContainer (org.osmf.container.MediaContainer) class. Actually there is no container package like the standalone version. And if you wanted them both to match you would have to copy the standalone version to your Flex 4.0 SDK folder, then you would have to update OSMFClasses.as to the new package locations so you won't get runtime complier errors when it can't find the classes. Is this by design? I ran into this trying to do some of the examples on the OSMF site. The last I download the Flex 4 SDK was 04/11/2010 the same would be for OSMF.
Flex 4 ships with an earlier version of OSMF, and there have been some changes between then and now. If you want to use the latest version of OSMF with Flex 4, then you might need to remove the osmf.swf file from the directory in your Flex project.
Can we have this in BIG RED LETTERS. Now FB is released it is going to cause no end of problems - I just spent a couple of hours faffing around trying to sort out where all the classes have gone
What I've done is remove osmf.swc from the Flex 4.0 sdk, then I added the new osmf.swc file to my libs folder for my project. Is there a for updating osmf in Flex 4.0 it works nativly with the sdk. The original reason why I got errors was because the frameworks/projects/osmf/src/OSMFClasses.as packages in Flex 4 were not the same as the new osmf.swc (most of the flex 4 swc have these package reference files). So those would have to be updated every time the osmf packages change.