Tvheadend

same situation here

managed to set it up to watch it chanel at a time using the iptv method but no guide data

In case anyone stumbles across this in the future, this issue can be worked around by changing the QAM64 settings to "Auto" for each mux.

https://forum.silicondust.com/forum/viewtopic.php?f=116&t=73320

Cannot confirm this bug/behaviour on HDHomerun Expand/HDHR3-4DC with Firmware: 20200225, all muxes are QAM256 except the initial discovery mux which is QAM64 and are set to their static values. Upgrading the firmware still makes channel tune work for HTS Tvheadend 4.2.8-36~g5bdcfd8ac on x86 and HTS Tvheadend 4.2.8-34~g24a2f59e9 on Raspberry Pi.

I suspect we'll start seeing more things like this creep in as TVH goes on being unmaintained for 4+ months. Anyone have a good exit strategy yet?

No problems here after upgrade but I forgot to say I'm using DVB-C and not DVB-T(2)!

I suspect it is a problem for uk Freeview as both of us experiencing this are on that system but as said above changing modulation to auto fixes it

Hi all,

I have made the recommended changes to the Modulation (QAM/AUTO) and I'm still getting the "No input source available" message.

Version is:
HTS Tvheadend 4.2.8-36 ~ CoreELEC Tvh-addon v9.2.121

Network:
DVB-T

Can anyone offer any suggestions on how I can get this working.

TIA

Greg

update to lates 4.3 there is new drivers included in TVH

Unfortunately updating to 4.3 did not help.

Any other suggestions?

EDIT: Don't know if this is important or helpful. With the old HDHR firmware I could not detect any Muxes with a scan with the default modulation setting of QAM/AUTO. I had to set modulation to QAM/64 for HDHR to find any Muxes. Now I'm told to use QAM/AUTO for this new firmware when previously it never worked.

I am using CoreELEC 9.2.2 tvheadend 4.3
I had the 'no free adapter' error.
I set Auto for QAM for DVB-S and I get a lot of the muxes scanned but 34 muxes remain in the queue.
They do not get scanned.

For DVB-T I use a HDHomerun quattro and have that working on DVB-T in Ireland.

BUT ..... it has a problem. It has lots of transport & continuity errors.

Loglevel debug: enabled

2020-04-18 13:25:15.766 TS: DVB-T Network/674MHz/RTÉ One Transport error indicator (total 16)
2020-04-18 13:25:15.766 TS: DVB-T Network/674MHz/RTÉ One: H264 @ #2101 Continuity counter error (total 11)
2020-04-18 13:25:15.766 TS: DVB-T Network/674MHz/RTÉ One: MPEG2AUDIO @ #2201 Continuity counter error (total 8)
2020-04-18 13:25:15.766 TS: DVB-T Network/674MHz/RTÉ One: MPEG2AUDIO @ #2501 Continuity counter error (total 8)
2020-04-18 13:25:15.797 TS: DVB-T Network/674MHz/RTÉ One: TELETEXT @ #2301 Continuity counter error (total 7)
2020-04-18 13:25:15.797 TS: DVB-T Network/674MHz/RTÉ One: MPEG2AUDIO @ #2401 Continuity counter error (total 7)
2020-04-18 13:25:55.345 TS: DVB-T Network/674MHz/RTÉ One: H264 @ #2101 Continuity counter error (total 12)
2020-04-18 13:25:55.377 TS: DVB-T Network/674MHz/RTÉ One: TELETEXT @ #2301 Continuity counter error (total 8)
2020-04-18 13:26:03.599 TS: DVB-T Network/674MHz/RTÉ One Transport error indicator (total 17)
2020-04-18 13:26:03.599 TS: DVB-T Network/674MHz/RTÉ One: MPEG2AUDIO @ #2201 Continuity counter error (total 9)
2020-04-18 13:26:03.599 TS: DVB-T Network/674MHz/RTÉ One: MPEG2AUDIO @ #2501 Continuity counter error (total 9)
2020-04-18 13:26:03.645 TS: DVB-T Network/674MHz/RTÉ One: MPEG2AUDIO @ #2401 Continuity counter error (total 8)
2020-04-18 13:26:45.803 TS: DVB-T Network/674MHz/RTÉ One Transport error indicator (total 20)
2020-04-18 13:26:45.803 TS: DVB-T Network/674MHz/RTÉ One: H264 @ #2101 Continuity counter error (total 14)
2020-04-18 13:26:45.803 TS: DVB-T Network/674MHz/RTÉ One: MPEG2AUDIO @ #2201 Continuity counter error (total 10)
2020-04-18 13:26:45.803 TS: DVB-T Network/674MHz/RTÉ One: MPEG2AUDIO @ #2501 Continuity counter error (total 10)
2020-04-18 13:26:45.804 TS: DVB-T Network/674MHz/RTÉ One: TELETEXT @ #2301 Continuity counter error (total 10)
2020-04-18 13:26:45.820 TS: DVB-T Network/674MHz/RTÉ One: MPEG2AUDIO @ #2401 Continuity counter error (total 9)
2020-04-18 13:27:07.052 TS: DVB-T Network/674MHz/RTÉ One Transport error indicator (total 22)
2020-04-18 13:27:07.052 TS: DVB-T Network/674MHz/RTÉ One: H264 @ #2101 Continuity counter error (total 16)
2020-04-18 13:27:07.082 TS: DVB-T Network/674MHz/RTÉ One: MPEG2AUDIO @ #2201 Continuity counter error (total 11)
2020-04-18 13:27:07.083 TS: DVB-T Network/674MHz/RTÉ One: TELETEXT @ #2301 Continuity counter error (total 11)
2020-04-18 13:27:07.083 TS: DVB-T Network/674MHz/RTÉ One: MPEG2AUDIO @ #2501 Continuity counter error (total 11)
2020-04-18 13:27:15.749 TS: DVB-T Network/674MHz/RTÉ One: MPEG2AUDIO @ #2401 Continuity counter error (total 10)

This results in the break up of the stream, making the channels unwatchable.

@Greg ........ did you get yours sorted?

My problem was caused by a recent firmware update to HDHR that killed TvH. See:

https://forum.silicondust.com/forum/viewtopic.php?f=116&t=73320

Greg H wrote:

My problem was caused by a recent firmware update to HDHR that killed TvH. See:

https://forum.silicondust.com/forum/viewtopic.php?f=116&t=73320

Thanks.
Not pretty.

They could easily offer a temporary roll back on firmware if they wished.

A week later it begins to smell deliberate!

Mon Apr 13, 2020 11:19 pm
We should have a beta firmware available soon. Things are just stretched a bit thin at the moment, but I will get out my poking stick and poke the developers. A lot.