[no Bug] TV scheduled recording does not stop in some cases (1 Viewer)

mm1352000

Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    my TBS tuners again
    I suspect so, yes.

    The scheduler thread deadlocks on attempting to stop recording The Keiser Report:
    [collapse]
    [2015-01-20 23:05:03,918] [Log ] [scheduler thread] [INFO ] - Scheduler: stop record RT 20/01/2015 22:25:13-20/01/2015 23:00:00 Keiser Report
    [2015-01-20 23:05:03,918] [Log ] [scheduler thread] [INFO ] - card: StopRecording card=6, user=scheduler2866
    [2015-01-20 23:05:03,919] [Log ] [scheduler thread] [INFO ] - basesubchannel.StopRecording 0
    [2015-01-20 23:05:03,919] [Log ] [scheduler thread] [INFO ] - tvdvbchannel.OnStopRecording subch=0, subch index=0
    [2015-01-20 23:05:03,919] [Log ] [scheduler thread] [INFO ] - tvdvbchannel.OnStopRecording subch:0-0 tswriter StopRecording...
    [2015-01-20 23:05:03,920] [Log ] [scheduler thread] [INFO ] - tvcard:FreeSubChannel: subchannels count 1 subch#0
    [2015-01-20 23:05:03,920] [Log ] [scheduler thread] [INFO ] - DVB subch:0 Decompose()
    [2015-01-20 23:05:03,921] [Log ] [scheduler thread] [INFO ] - FreeSubChannel CA: freeing sub channel : 0
    [2015-01-20 23:05:03,921] [Log ] [scheduler thread] [INFO ] - tvcard:FreeSubChannel : no subchannels present, pausing graph
    [2015-01-20 23:05:03,921] [Log ] [scheduler thread] [INFO ] - dvb:confused:topGraph called
    [2015-01-20 23:05:03,921] [Log ] [scheduler thread] [INFO ] - tvcard:FreeAllSubChannels
    [2015-01-20 23:05:03,922] [Log ] [scheduler thread] [INFO ] - dvb:confused:topGraph[/collapse]

    All recordings that are meant to start or stop after this point in time will fail to start/stop.
    You can see that TsWriter stops successfully:
    [collapse]
    [2015-01-20 23:05:03,922] [c6441f0] [ccc] - CMpTsFilter::pause()
    [2015-01-20 23:05:03,922] [c6441f0] [ccc] - Pause filter...
    [2015-01-20 23:05:03,922] [c6441f0] [ccc] - HRESULT = 0x0
    [2015-01-20 23:05:03,956] [c6441f0] [ccc] - CMpTsFilter::confused:top()
    [2015-01-20 23:05:03,956] [c6441f0] [ccc] - Stop streaming...
    [2015-01-20 23:05:03,956] [c6441f0] [ccc] - Stop filter...
    [2015-01-20 23:05:03,956] [c6441f0] [ccc] - HRESULT = 0x0[/collapse]

    So, some other filter in the tuner graph failed to stop. I can't prove that it was the tuner... but I strongly suspect it.

    P.S. In future I'd prefer it if you started a separate thread. martoma's issue is resolved and the bug report has been closed. While related, your problem is the start of a new discussion.
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Interestingly...
    "20/01/2015 23:02:49";"WinDefend";"(0)";"Information";"%Windows Defender scan has started. Scan ID: {59C25552-3AE4-4720-B090-2406D5C06C2C} Scan Type: %AntiSpyware Scan Parameters: %Quick Scan User: NT AUTHORITY\NETWORK SERVICE";"1000"
    "20/01/2015 23:06:01";"WinDefend";"(0)";"Information";"%Windows Defender scan has finished. Scan ID: {59C25552-3AE4-4720-B090-2406D5C06C2C} Scan Type: %AntiSpyware Scan Parameters: %Quick Scan User: NT AUTHORITY\NETWORK SERVICE Scan Time: 0:03:11";"1001"
     

    CyberSimian

    Test Group
  • Team MediaPortal
  • June 10, 2013
    2,944
    1,850
    Southampton
    Home Country
    United Kingdom United Kingdom
    Interestingly...
    "20/01/2015 23:02:49";"WinDefend";"(0)";"Information";"%Windows Defender scan has started.
    "20/01/2015 23:06:01";"WinDefend";"(0)";"Information";"%Windows Defender scan has finished.
    So "Windows Defender" was running at the time that the recordings should have stopped! It seems too much of a coincidence to be unrelated to the problem. :D

    The system is a dedicated HTPC, and it is not used for browsing the internet, so I have disabled "Windows Defender". Hopefully that will stop the problem recurring. :)

    In future I'd prefer it if you started a separate thread. martoma's issue is resolved and the bug report has been closed. While related, your problem is the start of a new discussion.
    Will do! Sorry about that. :oops:

    -- from CyberSimian in the UK
     

    Users who are viewing this thread

    Top Bottom