Commit | Date | |
---|---|---|
[r1676]
by
weizhang@adobe.com
First code submission for bug FM-760, add unit tests to increase code coverage. |
2010-05-07 17:42:13 | Tree |
2010-05-07 17:41:34 | Tree | |
[r1674]
by
evrijkom@adobe.com
Reverting on statically binding the VideoQoSPlugin from OSMFPlayer, as per Brian's suggestion. In order to see the video FPS, one now needs to uncomment the "videoQoSFPS" tag in config.xml, and add custom code to load a precompiled version of the VideoQoSPlugin (from the plugins sample folder). |
2010-05-07 17:23:38 | Tree |
[r1673]
by
evrijkom@adobe.com
Attempting to fix server build (missing source path to sample plug-in), take 2. |
2010-05-07 17:07:24 | Tree |
[r1672]
by
evrijkom@adobe.com
Attempting to fix server build (missing source path to sample plug-in). |
2010-05-07 16:57:57 | Tree |
2010-05-07 16:54:21 | Tree | |
[r1670]
by
evrijkom@adobe.com
FM-807: Extending OSMF player to use the MetadataLabel widget together with the VideoQoSPlugin sample to show the video FPS for the content that is being played back. |
2010-05-07 16:32:06 | Tree |
[r1669]
by
evrijkom@adobe.com
FM-807: Adding a Proxy plug-in sample that lifts the "currentFPS" property off VideoElements, adding them as metadata to the element at hand. Serial and parallel elements are catered for by the addition of a custom synthesizer. |
2010-05-07 16:30:02 | Tree |
2010-05-07 16:25:32 | Tree | |
2010-05-07 12:43:54 | Tree |