Channel switching between 2 tunres failed. (1 Viewer)

Helios61

Retired Team Member
  • Premium Supporter
  • January 30, 2008
    4,587
    873
    62
    NRW
    Home Country
    Germany Germany
    Build: 1.15.100.0

    Hi community, Hi @mm1352000
    I've noticed an odd issue with channel switching between 2 tuners. For testing i've mapped 2 different channels to respectively one tuner on my Digital Devices Cine C/C2/T/T2 (V7). If i try to switch between these channels, unfortunately it fails -> Log_1. It is working fine, if i first stop playback of tuner 1 and then start the other channel with tuner 2 -> Log_2.
    Maybe you can help to solve this issue.
    Best regards
    Helios61
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Log 1 shows successful channel change on the TV Server side, so I'm the wrong person to tag. ;)

    In the client log it looks like your HDMI connection or GPU drop out part way through the channel change:
    [2017-02-19 12:37:27,319] [Log ] [MPMain ] [INFO ] - TVHome.ViewChannelAndCheck(): View channel=QVC Plus HD
    [2017-02-19 12:37:27,465] [Log ] [MPMain ] [DEBUG] - TVHome.ViewChannelAndCheck(): Stopping player. CardId:6/3, RTSP:rtsp://BACH:554/stream6.0
    [2017-02-19 12:37:27,470] [Log ] [MPMain ] [DEBUG] - TVHome.ViewChannelAndCheck(): Stopping player. Timeshifting:R:\Timeshift\live6-0.ts.tsbuffer
    [2017-02-19 12:37:27,475] [Log ] [MPMain ] [DEBUG] - TVHome.ViewChannelAndCheck(): rebuilding graph (card changed) - timeshifting continueing.
    ...
    [2017-02-19 12:37:29,184] [Log ] [MPMain ] [INFO ] - succeeded:confused:ucceeded TvControl.VirtualCard
    [2017-02-19 12:37:29,187] [Log ] [MPMain ] [INFO ] - TSReaderPlayer:Continue graph
    ...
    [2017-02-19 12:37:31,992] [Log ] [MPMain ] [DEBUG] - Main: WM_DEVICECHANGE (Event: DBT_DEVICEREMOVECOMPLETE)
    [2017-02-19 12:37:31,995] [Log ] [MPMain ] [DEBUG] - Main: Device type is DBT_DEVTYP_DEVICEINTERFACE - Name: Intel(R) HD Graphics 630
    [2017-02-19 12:37:31,997] [Log ] [MPMain ] [INFO ] - Main: Video Device or Screen Intel(R) HD Graphics 630 removed
    ...
    [2017-02-19 12:37:32,015] [Log ] [MPMain ] [DEBUG] - Main: WM_DEVICECHANGE (Event: DBT_DEVICEREMOVECOMPLETE)
    [2017-02-19 12:37:32,018] [Log ] [MPMain ] [DEBUG] - Main: Device type is DBT_DEVTYP_DEVICEINTERFACE - Name: Intel(R) Display-Audio
    [2017-02-19 12:37:32,022] [Log ] [MPMain ] [INFO ] - Main: Audio Renderer Intel(R) Display-Audio removed

    That's what's causing the failure.
     

    Helios61

    Retired Team Member
  • Premium Supporter
  • January 30, 2008
    4,587
    873
    62
    NRW
    Home Country
    Germany Germany
    It is odd, switching between channels is workink fine on the same tuner. The issue occures since 1.16 pre.
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    This refresh rate change in the middle of the channel change seems suspicious to me:
    [2017-02-19 12:37:29,238] [Log ] [MPMain ] [INFO ] - RefreshRateChanger.SetRefreshRateBasedOnFPS: current refreshrate is 50hz - changing it to 60hz
    ...
    [2017-02-19 12:37:31,021] [Log ] [MPMain ] [INFO ] - RefreshRateChanger.SetRefreshRateBasedOnFPS: current refreshrate is 60hz - changing it to 50hz

    Perhaps the GPU driver doesn't like such fast changes.
    Have you checked what happens if you disable the refresh rate changer?

    @Sebastiii
    I don't recall this happening in older versions of MP. Do the madVR changes in MP 1.16 PR affect the refresh rate changer?

    The other thing is...
    Are you certain that the problem started with MP 1.16 PR?
    It's easy to think the new MP version is the problem, but your GPU driver is reasonably new:
    Card name: Intel(R) HD Graphics 630
    ...
    Driver Date/Size: 18.01.2017 01:00:00, 94237888 bytes

    ...and of course W10 automatically installs updates relatively frequently. Any or all of these may potentially have caused the problem. The only way to know for sure would be to roll back to MP 1.15 final and confirm whether the problem still occurs.
     

    Helios61

    Retired Team Member
  • Premium Supporter
  • January 30, 2008
    4,587
    873
    62
    NRW
    Home Country
    Germany Germany
    I will do some tests with refresh rate changer.
    Are you certain that the problem started with MP 1.16 PR?
    Not 100%. I've noticed that first after the update to 1.16 pre.
    ...and of course W10 automatically installs updates relatively frequently.
    Automatic driver updates are deactivatet.
     

    Helios61

    Retired Team Member
  • Premium Supporter
  • January 30, 2008
    4,587
    873
    62
    NRW
    Home Country
    Germany Germany

    Users who are viewing this thread

    Top Bottom