[TV] PowerScheduler doesn't detect network traffic. (1 Viewer)

Leftover

Portal Member
September 28, 2009
12
0
MediaPortal Version: 1.0.4.23684 (supposed to be latest SVN for 1.1 BETA)
MediaPortal Skin: StreamedMP
Windows Version: XP32 SP3
CPU Type: Atom n330
HDD: 320Gb
Memory: 2Gb
Motherboard: Nvidia ION
Video Card: Nvidia ION
Video Card Driver:
Sound Card:
Sound Card AC3:
Sound Card Driver:
1. TV Card: AVerTV Hybrid Ultra USB
1. TV Card Type: Analog/DVB-T
1. TV Card Driver:
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: Cyberlink
MPEG2 Audio Codec:
h.264 Video Codec: MPC-HT
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote: MCE
TV:
TV - HTPC Connection:

I got a problem with PowerScheduler plugin. While Network Monitor (one that based on same code as PS plugin, at least i was told so:)) and Perfmon.exe can detect and measure ongoing network traffic, PowerScheduler doesn't detect any traffic most of a time. There were few report in the forum about similar problem but in all cases nor Network Monitor, nor Perfmon were show any traffic, so looks like this case is different.

There's screenshot of Network Mon. and Perfmon running and corresponding snippet from tv.log.

Traffic stays about a same. 100kb/s - outgoing, 10kb/s - incoming. PS Detects it at beginning, then values go down, and finally i get "NetworkMonitorHandler: idle limit in KB/s: 2" all the time. And computer goes to standby mode...

Any directions where to look for possible solution, please :)
 

Attachments

  • traffic_mon.jpg
    traffic_mon.jpg
    100.4 KB

arion_p

Retired Team Member
  • Premium Supporter
  • February 7, 2007
    3,373
    1,626
    Athens
    Home Country
    Greece Greece
    I can confirm this is a bug. Also found the problem in the code and fixed. Last sample time was not reset propertly. As a result traffic was measured over an increasing time interval which coincides with your observations.

    Fix will be in next SVN.
    :D
     

    Users who are viewing this thread

    Top Bottom