[Live-devel] RTSPClient w/significant frame loss

Brad O'Hearne brado at bighillsoftware.com
Fri Mar 23 12:51:43 PDT 2012


Ugh typos....this quote: 

> That means that in this case, LIVE555 (Step A) is consuming a maximum of ~33ms per frame in order to achieve that frame rate. However, in the case of adding the one decode call, which dropped frame rate down to 10fps, LIVE555 (Step A) is consuming ~810ms total, or 81ms processing time per frame, because the decode consumes only 19ms. That is a 41% jump in processing time for LIVE555 (Step A) when a situation is introduced where frames cannot be processed fast enough to keep from losing frames. 

It should read that there is a 245% jump in processing time for LIVE555 (Step A) when a situation is introduced where frames cannot be processed fast enough to keep from losing frames. 

Brad

Brad O'Hearne
Founder / Lead Developer
Big Hill Software LLC
http://www.bighillsoftware.com




More information about the live-devel mailing list