[Helix-client-dev] CR-Client: Player core start-up thread hopping

[Helix-client-dev] CR-Client: Player core start-up thread hopping

Milko Boic milko at real.com
Thu Sep 7 01:10:26 PDT 2006


At 11:56 AM 9/6/2006, Greg Wright wrote:


>Milko Boic wrote:
>>Modified by: milko at real.com
>>Date: 9:06:06
>>Project: Atlas
>>Synopsis: Player core yielding and quick seek performance
>>Overview:
>>The change streamilnes thread-hopping the core performs on start-up for 
>>the purpose of having various actions performed on different threads 
>>(AudioPlayer setup on interrupt thread, audio device resumption on system 
>>thread).
>>When a need for hop to a different thread is detected, player main loop 
>>(ProcessIdle) is immediately recscheduled to an appropriate thread.
>>Other threads are not scheduled.
>>This also incloudes a correction in file source which registers the 
>>source that is added on the fly.  Previously, local file source were not 
>>registered which resulted in non-functional fast start and failure to 
>>account for used bandwidth.
>
>>@@ -9673,6 +9704,7 @@
>>      {
>>          m_ulActiveSureStreamSource++;
>>+    /*** Do not tunr off fast start if multiple sure-streams present
>>          if (m_ulActiveSureStreamSource > 1 && m_bFastStart)
>>          {
>>              HXLOGL2(HXLOG_TRAN, "SureStreams > 1 - TurboPlay Off");
>>@@ -9690,6 +9722,7 @@
>>                  }
>>              }
>>          }
>>+    ***/
>>      }
>
>Did you mean to keep all that code commented out?

Yes as an aide in troubleshooting/debugging issues later on.

Thanks,
Milko


>rest looks good.
>
>--greg.





More information about the Helix-client-dev mailing list
 

Site Map   |   Terms of Use   |   Privacy Policy   |   Contact Us

Copyright © 1995-2007 RealNetworks, Inc. All rights reserved. RealNetworks and Helix are trademarks of RealNetworks.
All other trademarks or registered trademarks are the property of their respective holders.