TVH asks to change the UDP ports to 46342-46343, but the server replied that client has ports 42998-42999.
If this is a bug in DVBViewer, is there any way I can get round it? If not, could I have an exact description of what the bug is and I will try to raise it on the DVBViewer forums. I should also say the DVBViewer log doesn't show any problems when I hit this. " I'm not sure what that means, but I did enable the trace he mentions and attached is a debug log showing the failure with the full trace. I raised this on IRC and Perexg replied " it appears that DVBViewer allocates wrong UDP ports you may enable '-trace httpc' to see the RTSP communication between TVH and server. As I have multiple Sat>IP tuners, it then switches to another and tunes ok. I only get this when TVH tries to use the same tuner as is currently used - when I switch it seems to close the existing "subscription" but then fails setting up the new one.
Using the KODI TVH Plugin I can view channels fine, but I have one issue when changing from one channel to another - I almost always get an error logged "RTSP Setup Error 9 (Unknown error -9) " followed by "subscription: 001A: service instance is bad, reason: Tuning failed". I'm quite new to TVHeadend but have spent the past few days setting it up and have finally got it configured so it all works.Īs I don't have any spare tuners to use, I was pleased to see TVH detected all five tuners that I use on DVBViewer Recording Service as SAT>IP tuners, and I found I could use them to scan for channels ok, scan EPG etc.
0 kommentar(er)
