- June 8, 2014
- 57
- 5
- Home Country
- United States of America
We're having an issue where it appears that when trying to watch Live TV from XBMC (on a Linux box), every so often the tuner appears to get "hung" - specifically MediaPortal thinks it's in use even though it isn't, and at that point even the MedialPortal frontend can't access the card until we reboot. This happens even if XBMC is no longer running on the network.
Three questions: One, if it is time for a scheduled recording , will MediaPortal dump this "zombie" connection and begin the recording, or would this prevent any recordings until a reboot? Second, any way to prevent this from happening? And third, is there any way to break this "zombie" connection without rebooting the entire system? Just stopping and restarting the TV Server manually doesn't work - it appears to dump the connection and shows the card as idle, but still won't let anything use it until you reboot.
Note that we are not 100% sure that this only happens with the XBMC client, it's just that when we've seen this the backend always says that the XBMC plugin is in use, with whatever the last channel was that we tried to tune. But that is usually the failed attempt that made me aware of the problem, so it could have a cause totally unrelated to XBMC.[DOUBLEPOST=1402951627][/DOUBLEPOST]By the way I posted an XBMC log file excerpt from when this problem occurred at http://pastebin.ca/2809575
I find the references to the timeshift buffer puzzling.
Three questions: One, if it is time for a scheduled recording , will MediaPortal dump this "zombie" connection and begin the recording, or would this prevent any recordings until a reboot? Second, any way to prevent this from happening? And third, is there any way to break this "zombie" connection without rebooting the entire system? Just stopping and restarting the TV Server manually doesn't work - it appears to dump the connection and shows the card as idle, but still won't let anything use it until you reboot.
Note that we are not 100% sure that this only happens with the XBMC client, it's just that when we've seen this the backend always says that the XBMC plugin is in use, with whatever the last channel was that we tried to tune. But that is usually the failed attempt that made me aware of the problem, so it could have a cause totally unrelated to XBMC.[DOUBLEPOST=1402951627][/DOUBLEPOST]By the way I posted an XBMC log file excerpt from when this problem occurred at http://pastebin.ca/2809575
I find the references to the timeshift buffer puzzling.
Last edited: