Tvheadend

If you want a build from repo, then apt-get update, and then apt-get install tvheadend
If you want to build it, then follow the tutorial posted on the tvheadend website.
https://tvheadend.org/projects/tvheadend/wiki/Building

Is it necessary, to run the following commands before update and install, if I want a version higher than 4.0?

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 379CE192D401AB61

echo deb https://dl.bintray.com/tvheadend/ubuntu stable main | sudo tee -a /etc/apt/sources.list

It depends on the distribution. That command does the following: adds a new key to the repository and then adds a new repository.
First I would see without, I don't know if there is any tvheadend included in your distro.

Yes, those are the commands to add the current 4.0.x stable release to your system. A quick sudo apt-get update && sudo apt-get upgrade afterwards will get you the new version (along with all other updates that your system is due, of course).

Note that the upgrade isn't entirely painless because of configuration changes, so you will need to do some 'repair' work... it's not difficult, but just don't do it when you want to record or watch something in the next hour, that's all.

Once you're done, you can remove the old repository from sources.list if you like, but it doesn't harm anything to leave it there.

Greetings:

I had this happen to me recently, without realizing it until it was too late. I normally run the apt-get update/apt-get dist-upgrade periodically. Last month, tvheadend got upgraded to 4.0.8-3 and now my system doesn't work.

PLEASE, can someone explain what is required for this 'repair' work Prof Yaffle refers to???

My system runs on a Raspberry Pi/Raspbian (Wheezy) using a Hauppage 950Q WinTV-HVR Hybrid TV Stick (USB). It had worked flawlessly for over a year prior to the 'upgrade'. Now, I'm very frustrated.

I bought a new tuner stick, same exact model, thinking it had gone bad. Still no TV.

I deleted all of my muxes and services, after taking screen shots for at least some backup(dvr.rtf, attached), and entered the muxes manually. After a moment, the system populated the Services on its' own.

However, on the muxes tab, the Scan Result column shows 'Fail' for all of the muxes.

I'm also attaching the latest syslog, so the errors can be seen.

Thanks!!!

Neil

It's difficult to tell from your screenshots - despite the 48MB download (damn, I hate RTF...), your document won't open on AbiWord and crashes LibreOffice (at least on my system), so I can only see things briefly before they die... I think you have a corruption in the fourth page. Using something like snag.gy would perhaps be easier.

Broadly, you should have:

1. A tuner definition that shows that the tuner is recognised by the system. That tuner is associated with...

2. A network definition. This would normally be "Freesat", "Terrestrial", "Brian" or something simple that means something to you - it's just a way of separating networks. You have a much longer name here.

3. Mux definitions. These are the carrier signals broadcast on that network, and thus picked up by the associated tuner. They can be defined by hand or auto-detected if you "seed" the definitions with the basic parameters. There are pre-defined lists, but they're from public sources and are frequently hopelessly out of date.

4. Services. These are then the individual streams available within those muxed carrier signals. These are automatically detected on a scan.

5. Channels. These are the logical groupings of services. You can map these by hand or simply auto-map all discovered services.

The repair work is - was - really just a matter of making sure all these were in place, as that's the significant change between 3.x and 4.x. From what I can see before things crash, thought, it looks to me as if you have most of these, as you have a list of services that appear to be mapped to channels, so I'm not sure that's your problem.

What I can see is that your EPG/XMLTV configuration is complaining, but I don't see that's immediately relevant. After that, we need to start trying to play individual services (so the "Play" link off that tab) or channels (similar) to see what goes on. It may be that your config has been imported without the underlying pieces all being lined up (unlikely if you've rebuilt it)...

68 muxes seems a lot - is this normal for ATSC? It looks like anything with a TSID == 65535 has failed completely, but anything else has returned services and has those services mapped. That said, it's those "with mapped stuff" muxes that are showing in your syslog errors, so there's still something deeper.

Any chance of screenshots (via a paste site and embedded or linked, please) for the whole config - tuners and networks as well as the mux list?

Neil Carter wrote:

Greetings:

I had this happen to me recently, without realizing it until it was too late. I normally run the apt-get update/apt-get dist-upgrade periodically. Last month, tvheadend got upgraded to 4.0.8-3 and now my system doesn't work.

PLEASE, can someone explain what is required for this 'repair' work Prof Yaffle refers to???

My system runs on a Raspberry Pi/Raspbian (Wheezy) using a Hauppage 950Q WinTV-HVR Hybrid TV Stick (USB). It had worked flawlessly for over a year prior to the 'upgrade'. Now, I'm very frustrated.

I bought a new tuner stick, same exact model, thinking it had gone bad. Still no TV.

I deleted all of my muxes and services, after taking screen shots for at least some backup(dvr.rtf, attached), and entered the muxes manually. After a moment, the system populated the Services on its' own.

However, on the muxes tab, the Scan Result column shows 'Fail' for all of the muxes.

I'm also attaching the latest syslog, so the errors can be seen.

Thanks!!!

Neil

What is it with Auvitek tuners! I remember someone else using those and having the same problem!

If it's showing services it shouldn't say FAIL at all very odd.

Here are the requested images, a good deal smaller, of the current config.

To me, this all boils down to two facts:

1. The tuner IS working, as the muxes/services are coming up with data
2. The errors in the syslog indicate there's some problem with the config. The scans should not be failing.

I notice on the Channels tab, which I have NOT rebuilt, the individual channels have nothing in the Services column. Could this be an issue?

Also, I don't use the EPG at all, as I never could get it to work.

Thanks!!

Neil

OK

I've manually updated the Channels to indicate Services, or vice versa. No change, still getting syslog errors.

Help!!

Could the new version of tvheadend require a newer version of the Auvitek firmware?

It's currently running xc5000: Firmware dvb-fe-xc5000c-4.1.30.7.fw

Neil Carter wrote:

Could the new version of tvheadend require a newer version of the Auvitek firmware?

It's currently running xc5000: Firmware dvb-fe-xc5000c-4.1.30.7.fw

Having a newer firmware version shouldn't make any differences.

I recommend that you open a ticket with debugging attached.

Enter this into debugging

I'm not sure the options I've picked will be useful, so change +linuxdvb,+mpegts to +all in both fields.

Once you've entered that and applied it do a scan & post the resulting log :).

Here's the log. I'm also opening a New Issue, as instructed.

Thanks!!

And the Issue is #3483

Update:

After providing some debug logs to the above referenced ticket, I was instructed to forgo the default 'AUTO' setting for the Modulation setting in the MUX configs and set it manually to VSB/8(8VSB).

I now have 19 of 21 desired channels working. So I thank you all TREMENDOUSLY!!!!

Of course, this means I still have two channels that are AWOL.

According to my TV, they are both on 599MHZ and 8VSB with a signal strength of 87(I assume out of 100). Just as good a signal as most of the other channels. They are channels 5.1 and 5.7. They are the only channels that should be available on the 599MHz mux.

I've tried several variations in the mux config, but they continue to throw the 'scan no data, failed' error in the syslog.

Any suggestions? I've entered much this same text into the ticket as well.

Please advise.

Thanks!!

Neil

Greetings:

Thank you for your continued assistance!

I set the frequency for the 599MHz mux in the settings to 599028615Hz(as suggested by Jaroslav Kysela in the ticket), then clicked Force Scan on the Network tab while watching the Status/Stream tab in another browser window. I currently have ten muxes configured, so I watch the Muxes tab while the scan is running, paying attention to the Signal Strength column. All of the muxes return a 71% Signal Strength reading, including the now 599.028MHz mux.

The syslog file at first received a 'scan no data, failed' message and the Scan Status column still showed 'Fail', for a couple of minutes. Then it changed to 'OK'. I looked on the Services tab and two new services were listed which are the two missing channels. Hallelujah!

The final entry in the syslog file reads:

Jan 8 18:30:24 carter-pi tvheadend4536: subscription: 0049: "scan" subscribing to mux "599.028MHz", weight: 6, adapter: "Auvitek AU8522
QAM/8VSB Frontend : ATSC #0", network: "_dev_dvb_adapter0_Auvitek_AU8522_QAM_8VSB_Frontend", service: "Raw PID Subscription"
Jan 8 18:30:29 carter-pi tvheadend4536: mpegts: 599.028MHz in _dev_dvb_adapter0_Auvitek_AU8522_QAM_8VSB_Frontend - scan complete
Jan 8 18:30:29 carter-pi tvheadend4536: subscription: 0049: "scan" unsubscribing

Woohoo!!

The moral of the story is not to trust 'AUTO' for a setting, I guess.

At this time, my system is working as I think it should! Thank you, thank you, thank you!!!

Neil