Commit | Date | |
---|---|---|
2010-05-07 23:14:58 | Tree | |
2010-05-07 23:08:37 | Tree | |
[r1680]
by
weizhang@adobe.com
Fix bug FM-836 and FM-823 For FM-836, there is a problem with HTTPNetStream when an external buffer manager changes the bufferTime of the stream to be larger than 3.75 for fast bandwidth and 7.5 for slow bandwidth. When OSMFPlayer runs into buffer empty event, the buffer manager will increment the bufferTime. After a few empty buffer events, the bufferTime will be larger than 3.75 or 7.5, at which point the next buffer empty event will put FP into the buffering state but never comes out because HTTPNetStream will stop downloading fragments and send the tc messages to appendBytes. The fix takes the bufferTime into consideration and choose the max of buffer time and 3.75/7.5 as the threshold. For FM-823, we set the default to enable enhanced seek. |
2010-05-07 22:39:54 | Tree |
[r1679]
by
briggs@adobe.com
Various ASDoc updates (no code changes): |
2010-05-07 20:54:50 | Tree |
2010-05-07 19:43:13 | Tree | |
2010-05-07 19:22:49 | Tree | |
[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 |