Tvheadend

Doctor Eggs wrote:

Here is my setup:

• HTS Tvheadend 4.2.2-32 ~ LibreELEC Tvh-addon v8.1.111
• Raspberry Pi 2
• 2 Hauppauge 950Q Tuners on a powered USB dock

I can watch TV just fine when running on one cleint, but if I try to watch a different channel on a different client, I get "TVHEADEND HTSP CLIENT - No Signal" alert in Kodi. Occasionally it will work, but more often than not I can't watch TV on more than one client.

Here is the log when things go wrong:
[...]

If I go to the Status tab on http://192.168.1.10:9981, I can see that it tries to tune to the channel. The Stream, Subs No., and Weight all show up with numbers as well as being able to see the Signal Strength. When it works, the Bandwidth column immediately shows up with a numnber. When it fails, there is a 0 in the Bandwidth column.

Any help on this would be greatly appreciated.

Thanks.

Hi,
I also have the same problem, but with an Afatech Technologies, Inc. AF9015 DVB-T USB2.0 stick as dual tuner, directly plugged to the RPi2.
I would also appreciate some help.
Thank you

@Jose.

I have one of those AF9015 devices and they are known to die after a certain number of tunes on Linux. It's one of the reasons why I replaced mine.

But for both of you. What does dmesg say when they stop working?

Here's mine:
https://pastebin.com/wVP2thSz

Edit: moved the dmesg from the post over to pastebin to avoid the long scroll...rookie mistake.

Does restarting tvheadend.

sudo service tvheadend restart

get the tuner running again?

I'm running TVHeadend on LibreELEC and I couldn't get that command to work. I tried the following and it seemed to work as I can see each of the Kodi media centers rerun the initialization of TVH:

systemctl restart service.tvheadend42

I tried it but I still can't have both tuners run at the same time.

Mark Clarkstone wrote:

@Jose.

I have one of those AF9015 devices and they are known to die after a certain number of tunes on Linux. It's one of the reasons why I replaced mine.

But for both of you. What does dmesg say when they stop working?

Hi Mark, thanks for your feedback and sorry for the delay.
I downgraded from 4.2 to HTS Tvheadend 4.0.9 ~ LibreELEC Tvh-addon v.102 and it works perfectly. The problem appears with versions higher than 4.0.9. I attach some screenshots where you can see that I can display simultaneously up to 8 different channels belonging to two different muxes.
It is a pitty, because the new versions have interesting functionalities.

@Jose
Did you restart after the downgrade? I suspect after a while you'll have the same issue with 4.0.9.

@Doctor
When the tuner dies have you tried w_scan to see if the tuner is still responding?

First off, thanks for the help in troubleshooting this Mark. It's much appreciated.

I can occasionally get it to use both tuners by having one run on a client and then using a different client to try to use the other tuner. I'll try to tune to a channel, have it fail, try a different channel, have it fail, then try the previous channel again and it will work. Normally it takes between 5-10 failures before it will successfully play the channel. Then when hit stop and try to tune to the same channel on client #2, it fails again.

Doctor Eggs wrote:

First off, thanks for the help in troubleshooting this Mark. It's much appreciated.

I can occasionally get it to use both tuners by having one run on a client and then using a different client to try to use the other tuner. I'll try to tune to a channel, have it fail, try a different channel, have it fail, then try the previous channel again and it will work. Normally it takes between 5-10 failures before it will successfully play the channel. Then when hit stop and try to tune to the same channel on client #2, it fails again.

This really sounds like a dodgy driver. Have you tried enabling Linked input?

Mark Clarkstone wrote:

@Jose
Did you restart after the downgrade? I suspect after a while you'll have the same issue with 4.0.9.

@Doctor
When the tuner dies have you tried w_scan to see if the tuner is still responding?

Yes, I did, and it still works fine.
I'm tempted to do an upgrade again, but I do not trust...

Mark Clarkstone wrote:

This really sounds like a dodgy driver. Have you tried enabling Linked input?

I have but that doesn't seem to have any effect.