Tvheadend

Steven Moschidis wrote:

So are you saying that I have to manually add all the muxes (as the predefined lists are fubar)?

No, not fubar just old. You only need to add ONE mux for DVB-T as long as you have network discovery active it should find all the others. The only exception to that is DVB-T2 those muxes aren't in the NIT.

I thought the "Force scan" option in the network tab was supposed to make tvheadend discover all available muxes direct from the tuner. Is that not the case? If not, then why not? What is it supposed to do?

"Force scan" makes tvh scan through all known muxes, if a scanned mux has NIT and that contains new mux info tvh will add it.

I have a friend who set up tvheadend on a pi (or nuc) using the same hdhomerun as I have. He fired up tvheadend, added the network, linked it to the tuners, hit the force-scan button and the muxes appeared.

Depends on the version, 3.4 used to scan through all frequencies but that was removed, I'm not 100% sure as to why but I think it was because it took an age to complete.

Thank you Mark, that's beginning to make more sense now!

Ok so I will manually add one mux and see what happens.

Thank you for taking the time to explain.

Just had to completely reinstall DSM and now I can't get the latest TVheadend install, synocommunity is only offering 3.4.27-6... Is there any way to manually install the SPK file to get me to the latest?

@Chris, it's because they're released as beta. If you enable beta packages in the package manager, you will see the latest version

Thanks. Got it back again!

Its streaming fine around the house, however I'm now unable to watch via the web interface. I get the following error:

2018-05-23 16:11:39.572 libav: Undefined constant or missing '(' in 'high'
2018-05-23 16:11:39.572 libav: Unable to parse option value "high"
2018-05-23 16:11:39.572 libav: Error setting option profile to value high.

I've never had this before and nothing has changed in terms of config.

Chris

Hi Chris,

Never seen this before. Googling for the error messages leads back to other threads on this forum. Seems to be related to VAAPI transcording. Please crosscheck, but I have not seen any solutions to this problem there either. If you cannot find anything, please open a ticket and be patient. perexg does not seem to be active these days, but maybe he looks at it when he returns...

Chris Beasley wrote:

Thanks. Got it back again!

Its streaming fine around the house, however I'm now unable to watch via the web interface. I get the following error:

2018-05-23 16:11:39.572 libav: Undefined constant or missing '(' in 'high'
2018-05-23 16:11:39.572 libav: Unable to parse option value "high"
2018-05-23 16:11:39.572 libav: Error setting option profile to value high.

I've never had this before and nothing has changed in terms of config.

Chris

In my past experience, these indeed are related VAAPI transcoding. It sounds as if you are using a version of Tvheadend that was build against a version of libav*/ffmpeg that had VAAPI support enabled. However, Tvheadend 4.2 does not know how to properly deal with options/parameters to libav* for VAAPI.

VAAPI support does work with 4.3, but I don't believe that the Synology packages are built from the master/4.3 branch, only 4.2. Therefore, I believe you need to wait until there are 4.3 packages, or use libx264 as your transcoding method as VAAPI does not work with 4.2.

@Robert Cameron
Thanks for chiming in. Your assumptions are correct. TVH is indeed built against a version with enabled VAAPI support on Intel platforms. I wasn't aware this would cause problems though.

If 4.2.5 was not built with VAAPI that would explain it. I've only just upgraded to 4.2.6 on the NAS after redoing the NAS and its not working compared to the earlier versions which playbacked fine. I've got an Intel CPU in the NAS.

Martin Walter wrote:

@Robert Cameron
Thanks for chiming in. Your assumptions are correct. TVH is indeed built against a version with enabled VAAPI support on Intel platforms. I wasn't aware this would cause problems though.

It's not really a "problem", per se. It just exposes the VAAPI codecs in the dropdown menu in Tvheadend. There may be confusion because Tvheadend 4.2 cannot properply set the options for VAAPI making it unusable from Tvheadend.

There are 2 remedies to this. The first is for the user to know not to use the VAAPI codecs. The second is to build/package Tvheadend with the --enable-ffmpeg_static option, instead of using the ffmpeg package provided by SynoCommunity.

Yes, VAAPI support has only been added relatively recently on the spksrc platform, i.e. after the 4.2.5 packages have been compiled. Static linking of ffmpeg created all kind of problems with cross-compiling it for ppc and arm platforms, which is why it has been separated out. I very much hope that just changing the codec solves it for the time being. @Chris: Can you confirm that this fixes your issue?

I have a Synology DS412 running with actual DSM Version. After upgrading TV Headend ( I guess it was 4.2-3)
to the 4.2.6-13 unfortunately I do not see much muxes.

So I uninstalled, rebooted and reinstalled several times, still no good result.

I created manual or by the assistant the network. In some cases, after the scanning started I got 6 services. But I had with the old version 150.
So somehow it is working, the SAT IP receceiver seems to work with the actual TVH version. But the scan not.

Iḿ based in Germany and using a TRIAX IP receiver. This is recognized by TVH and listed.
I choose Astra 19.2.

I do not know how to get back to the old package, that would help in the moment.

What information are needed to get a hint to the real problem?
What can I do on the commandline to force the scan?
Is the astra192. list mabye wrong or not working?

Regards

Gerald

@ Gerald

I have the same setup like you with a Triax TSS 400 Sat>IP Converter. And I had the same problem like you.

The standard mux of tvh is wrong (dont know why). You have to create a new one with the following settings:

"frequency": 11953500,
"symbol_rate": 27500000,
"fec": "3/4",
"polarisation": "Horizontal",
"modulation": "QPSK",
"delivery_system": "SYS_DVBS",

Here is the german link, which helps me to find the solution

[[https://www.kodinerds.net/index.php/Thread/52812-Keine-Muxes-f%C3%BCr-Astra-19-2E-unter-TvHeadend-4-2/?postID=321298#post321298]]

@ all
BTW: For now I am using tvh with Ubuntu. I now have a synology 418play, but in the community repo is no tvh. Where can I find it?

Thanks,

this did the job. I read some days ago about a problem with the channel conf.
But your hint is easier and saved some time.
I have now already > 100 Muxes.

Good to hear that I could help

Hi!

My Synology NAS is having problems to hibernate since I am using TVHeadend.
I found out that this is because of the Debugging/Logging in TVHeadend. When I turn it off and/or use "/dev/null" as a filename, hibernation is working well.
The problem is, that this setting is not persistent and gets lost after every restart.

Is there a possibility to turn of logging permanent or edit the logging filename?

Regards,
Christian

Yes, thats really bad. After every restart the setting is on again.

Here somebody explains how to compile tvheadend without logging, but that is too complicated for me :(
[[https://tvheadend.org/boards/5/topics/14755?r=19774]]

I have tested also a while ago to create a synology package, without success.

https://github.com/SynoCommunity/spksrc

git clone https://github.com/SynoCommunity/spksrc.git

I think this is the way to go to cross compile packages. There are several packages in, but also the tvheadend.
But my knowledge was too limtited to get it working. Some steps worked, but finally no tvheadend packages was created.

Itś a gut hint, where the hibernate issue comes from, I thought it is a general problem.
The debug is not needed, so mabye sometimes someone with more knowledge will fix it.
Probably this is more synology related, the people running on standard PC may not take care about this.

I think that its a tvheadend problem. My ubuntu pc also could not get into hibernation.

No need to recompile. Do the following:

(1) Stop the TVH package via package manager
(2) ssh into your NAS box as admin (root password)
(3) sudo su - # to obtain root rights (root password again)
(4) cd /var/packages/tvheadend/scripts
(5) Edit the file service-setup and look for the SERVICE_COMMAND line
(6) In that line delete the "-l ${LOG_FILE}" argument
(7) Save, log out and restart the package
(8) Report back if your NAS hibernates now

This change will be overwritten when you update the package but should work for the time being.

Does this also work if I restart tvheadend or my Synology?

Yes, just not when you upgrade TVH to another version...

Hello Guys,

one maybe helpful info:

If you want to update via synocommunity you must have beta access enabled in the package manager.

CU

Christian Wattengård Kneissl
@Sylvio Egal

Could you please let me know whether the workaround I gave you solves your hibernation problem or not?

Hi!

Yes, I can confirm, that deleting the "-l ${LOG_FILE}" argument solved my hibernation problem, also when I restart TVHeadend or completely reboot the NAS.
Maybe this fix could be applied to future TVHeadend installer packages!?
Thanks a lot and sorry for my late answer.

Regards