Bug: Powerscheduler does not work anymore after running DVB Grabber (1 Viewer)


MP Donator
  • Premium Supporter
  • January 7, 2009
    Home Country
    Belgium Belgium
    TV-Server Version: Final
    MediaPortal Version: Final
    MediaPortal Skin: Blue3 wide
    Windows Version: Vista Ultimate SP1
    CPU Type: Intel Core2 Duo E4400
    HDD: Samsung SpinPoint 300GB
    Memory: 1GB DDR2
    Motherboard: Asrock 775i945GZ
    Video Card: Asus 8500GT 512Mb
    Video Card Driver: NVidea 8500GT 181.20
    Sound Card: Internal
    Sound Card AC3: N/A
    Sound Card Driver: N/A
    1. TV Card: TechnoTrend S2-3200
    1. TV Card Type: DVB-S2
    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: ffdshow rev 2447
    MPEG2 Audio Codec: ffdshow rev 2447
    h.264 Video Codec: PDVD8
    Satelite/CableTV Provider: Astra 2
    HTPC Case: Antec Fusion
    Cooling: N/A
    Power Supply: N/A
    Remote: Windows MCE Remote
    TV: Sony
    TV - HTPC Connection: Sub-D


    I use Powerscheduler to shutdown MP after 5 mins of inactivity and when on the Home screen. This works quite well and has not provided too many issues.
    Next to this I use the DVB EPG Grabber to download the EPG data from Sat. The EPG Grabber is set to update itself every 720 mins.

    Now, from time to time, I have an issue that MP does not shutdown properly after completing a scheduled recording. This happens when the EPG grabber hasn't updated itself since some time and thus is past its 720 mins update cycle. The enclosed log shows what is happening.

    1. MP resumes from S3 sleep in order to start a recording
    2. MP records - as instructed - the correct program
    3. Powerscheduler initiates the shutdown as is required [2009-02-17 23:10:21.502000]
    4. [2009-02-17 23:10:23.835000] approx. 2 secs after the instruction for shutdown has been given, the EPG Grabber kicks in and starts updating
    5. After it finishes updating, the Powerscheduler somehow doesn't react anymore and the machine stays on indefintely.

    Can anyone explain this behaviour? Is this a bug? Any workarounds?
    If I need to provide more logs, please let me now.



    Users who are viewing this thread

    Top Bottom