Unable to watch live TV Mediaplayer 2.1 Final (1 Viewer)

Pat@MeCee

Portal Member
March 10, 2017
16
0
Home Country
Australia Australia
Hi there,

I'm unable to watch live TV using MediaPortal 2.1 Final
Channels and the EPG is fine, but when I go to watch live tv it just shows the revolving dots.
Happy to send any logs or info - but just can't find any sort of error message or reason why it's not working.
I'm sure there is some way of diagnosing what's going on - it just isn't that obvious where to start.....

Here are the logs.
 

HTPCSourcer

Retired Team Member
  • Premium Supporter
  • May 16, 2008
    11,418
    2,335
    Home Country
    Germany Germany
    Any update on this based on the log files sent through ?
    Sorry for the late reaction, but when you edit a post no message gets generated and I am unaware that you have posted anything.

    The main problem is this
    [2017-06-09 18:02:28,334] [68941 ] [102 ] [ERROR] - Starting timeshifting failed with result AllCardsBusy

    Unfortunately the logs were been taken at INFO level. Can you set the log level to DEBUG please (see Wiki Bug Reports and Log Files)? After that it would be good if you restarted the MP2 Server service so that a new log file is started. Then reproduce the issue, collect new logs and upload the file.

    Can you tell something about your tuner hardware? I can see only one single tuner.
    The other thing that intrigues me is your network environment:
    [2017-06-09 18:01:24,865] [5472 ] [TVService] [INFO ] - Controller: local ip address:10.0.0.29
    [2017-06-09 18:01:24,866] [5473 ] [TVService] [INFO ] - Controller: local ip address:192.168.137.1
    [2017-06-09 18:01:24,866] [5473 ] [TVService] [INFO ] - Controller: local ip address:192.168.2.14
    [2017-06-09 18:01:25,155] [5762 ] [TVService] [INFO ] - Controller: server running on Main_PC
    How many IP's does your server have?
     

    Pat@MeCee

    Portal Member
    March 10, 2017
    16
    0
    Home Country
    Australia Australia
    Hi There ,
    The tuner is a
    • AVLabs AVL680HD - USB High Definition - but it does not appear as this in device manager - it seems to appear as "legacy device"
    The Main_PC (server) has two IP addresses - one for hard wired ethernet ,the other for wireless.

    The log files in DEBUG mode are attached.

    Cheers
     

    HTPCSourcer

    Retired Team Member
  • Premium Supporter
  • May 16, 2008
    11,418
    2,335
    Home Country
    Germany Germany
    I am not sure what is happening.

    Both client and server are flooded by a repeated SSDP error message:

    [2017-06-18 12:35:45,383] [21577 ] [31 ] [DEBUG] - SSDPClientController: Cannot handle notify request from 192.168.2.1:1900 - Invalid message:
    NOTIFY * HTTP/1.1
    HOST: 239.255.255.250:1900
    CACHE-CONTROL: max-age=1800
    LOCATION: http://192.168.2.1:1780/WFADevice2.xml
    NTS: ssdp:alive
    SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00
    NT: urn:schemas-wifialliance-org:device:WFADevice:1
    USN: uuid:31da958f-40ad-5935-da37-a457b8e519c9::urn:schemas-wifialliance-org:device:WFADevice:1
    What is this address? Judging from the last line it has to do with WiFi.

    I can't see any attempt to watch TV.
     

    Pat@MeCee

    Portal Member
    March 10, 2017
    16
    0
    Home Country
    Australia Australia
    Please see attached - the192.168.2.1 address is the router which has both hard wired ethernet and wi-fi
     

    HTPCSourcer

    Retired Team Member
  • Premium Supporter
  • May 16, 2008
    11,418
    2,335
    Home Country
    Germany Germany
    Nothing changed. Logs still flooded by
    [2017-06-20 07:54:45,427] [3956 ] [52 ] [DEBUG] - Debug: SSDPClientController: Cannot handle SSDP response from 192.168.2.1:1900 - Invalid message:
    HTTP/1.1 200 Ok
    CACHE-CONTROL: max-age=1800
    DATE: Mon, 19 Jun 2017 21:54:47 GMT
    EXT:
    LOCATION: http://192.168.2.1:1780/WFADevice2.xml
    SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00
    ST: urn:schemas-wifialliance-org:device:WFADevice:1
    USN: uuid:31da958f-40ad-5935-da37-a457b8e519c9::urn:schemas-wifialliance-org:device:WFADevice:1
    This is a message from the network discovery process and your router appears to not act correctly. Try to switch off any UPnP function on your router and try again please.
     

    morpheus_xx

    Retired Team Member
  • Team MediaPortal
  • March 24, 2007
    12,073
    7,459
    Home Country
    Germany Germany
    @mm1352000 The posted errors above are coming out of our UPnP library.

    The cause are missing header entries
    C#:
          string bi = header["BOOTID.UPNP.ORG"];
          string ci = header["CONFIGID.UPNP.ORG"];
          string sp = header["SEARCHPORT.UPNP.ORG"];
    that are checked against here.

    The incoming SSDP responses look like:
    Code:
    [2017-06-20 07:54:56,183] [3375   ] [31       ] [DEBUG] - SSDPClientController: Cannot handle SSDP response from 192.168.2.1:1900 - Invalid message:
    HTTP/1.1 200 Ok
    CACHE-CONTROL: max-age=1800
    DATE: Mon, 19 Jun 2017 21:54:58 GMT
    EXT:
    LOCATION: http://192.168.2.1:1780/WFADevice2.xml
    SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00
    ST: urn:schemas-wifialliance-org:device:WFADevice:1
    USN: uuid:31da958f-40ad-5935-da37-a457b8e519c9::urn:schemas-wifialliance-org:device:WFADevice:1
    
    
    [2017-06-20 07:54:56,183] [3375   ] [31       ] [DEBUG] - SSDPClientController: Cannot handle SSDP response from 192.168.2.1:1900 - Invalid message:
    HTTP/1.1 200 Ok
    CACHE-CONTROL: max-age=1800
    DATE: Mon, 19 Jun 2017 21:54:58 GMT
    EXT:
    LOCATION: http://192.168.2.1:1780/WFADevice2.xml
    SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00
    ST: upnp:rootdevice
    USN: uuid:31da958f-40ad-5935-da37-a457b8e519c9::upnp:rootdevice
    
    
    [2017-06-20 07:54:56,184] [3376   ] [52       ] [DEBUG] - SSDPClientController: Cannot handle SSDP response from 192.168.2.1:1900 - Invalid message:
    HTTP/1.1 200 Ok
    CACHE-CONTROL: max-age=1800
    DATE: Mon, 19 Jun 2017 21:54:58 GMT
    EXT:
    LOCATION: http://192.168.2.1:1780/WFADevice2.xml
    SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00
    ST: urn:schemas-wifialliance-org:service:WFAWLANConfig:1
    USN: uuid:31da958f-40ad-5935-da37-a457b8e519c9::urn:schemas-wifialliance-org:service:WFAWLANConfig:1
    So they are not part of our code.

    Question is: are those 3 headers mandatory in all cases? Could we allow them to be null to detect more devices? Especially if the UPnP library is used for non-MP2 services...

    Note to @HTPCSourcer the logging in DEBUG mode was only added to trace exactly that kind of format issues. They should not affect MP functions, our services are working to our rules ;)
    Only negative aspect now is, that they are causing quite lot logging overhead (in DEBUG level only!)
     

    Users who are viewing this thread

    Top Bottom