TheBlueVoice

TVheadend continuity errors 1.04b 918

Recommended Posts

Hi!

 

Just switched from 3617xs to the 918+ loader to take advantage of the hardware encoding for plex.

 

That works great BUT now getting lots of continuity errors in tvheadend.

 

Not the hardware as nothing else changed - just the boot stick and reinstall appollolake version of tvh.

 

Googled but couldn't turn up anything...

 

Anyone have any ideas? 

 

Anyone using tvheadend ok with the 918+ loader ?

 

Cheers!


EDIT: 

 

Left it running for a while to see if it would settle but it crashed:

 

19-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH: Signal: 11 in PRG: /usr/local/tvheadend-testing/bin/tvheadend (4.4.20181215) [465759dfd7f360533cb733afa6267add1945fea9] CWD: /  
2019-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH: Fault address 0x10 (Address not mapped)
2019-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH: Loaded libraries: linux-vdso.so.1 /usr/local/tvheadend-testing/lib/libdvbcsa.so.1 /usr/local/tvheadend-testing/lib/libssl.so.1.0.0 /usr/local/tvheadend-testing/lib/libcrypto.so.1.0.0 /usr/local/tvheadend-testing/lib/libz.so /usr/local/tvheadend-testing/lib/liburiparser.so.1 /usr/local/tvheadend-testing/lib/libavfilter.so.6 /usr/local/tvheadend-testing/lib/libswresample.so.2 /usr/local/tvheadend-testing/lib/libavresample.so.3 /usr/local/tvheadend-testing/lib/libswscale.so.4 /usr/local/tvheadend-testing/lib/libavformat.so.57 /usr/local/tvheadend-testing/lib/libavcodec.so.57 /usr/local/tvheadend-testing/lib/libavutil.so.55 /lib/libdl.so.2 /lib/libpthread.so.0 /lib/libm.so.6 /usr/local/tvheadend-testing/lib/libiconv.so.2 /lib/librt.so.1 /lib/libc.so.6 /usr/local/tvheadend-testing/lib/libpostproc.so.54 /usr/local/tvheadend-testing/lib/libfontconfig.so.1 /usr/local/tvheadend-testing/lib/libfreetype.so.6 /usr/local/tvheadend-testing/lib/libass.so.9 /usr/local/tvheadend-testing/lib/libfribidi.so.0 /usr/local/
2019-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH: Register dump [23]: 00007f7408005d600000000000000000fffffffffffff74c00007f7490708460000055f9c81b168000007f740c00197000007f7470001fd0000055f9c6f79bc8000000000000000000007f7408000030000055f9c81b16d000000000000000000000000000000021000000000000001200007f740800240100007f7489c989d0000055f9c6252e44000000000001024600000000000000330000000000000004000000000000000efffffffe7ffbba130000000000000010
2019-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH: STACKTRACE
2019-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH:  0x55f9c61aa21a 0x55f9c5fbd000
2019-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH:  0x7f749114a1c0 0x7f749113a000
2019-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH:  0x55f9c6252e44 0x55f9c5fbd000
2019-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH:  0x55f9c624f067 0x55f9c5fbd000
2019-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH:  0x55f9c615fc50 0x55f9c5fbd000
2019-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH:  0x55f9c616cab4 0x55f9c5fbd000
2019-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH:  0x7f74911412c4 0x7f749113a000
2019-04-08T19:34:51+01:00 CheStation tvheadend[25798]: CRASH: clone+0x6d  (/lib/libc.so.6)
2019-04-08T19:34:51+01:00 CheStation kernel: [ 1290.824864] tvh:mtimer[25806]: segfault at 10 ip 000055f9c6252e44 sp 00007f7489c989d0 error 4 in tvheadend[55f9c5fbd000+cce000]

 

Share this post


Link to post
Share on other sites

Try tvheadend from linuxserver.io on docker.
It has vaapi enabled, and all libraries ready.
On creating docker comand you just need to map yout dvb device, to be available inside docker, simple as that.

They have all steps on their site, and its very simple.


Sent from my iPad using Tapatalk

Share this post


Link to post
Share on other sites
11 hours ago, JMRR said:

Try tvheadend from linuxserver.io on docker.
It has vaapi enabled, and all libraries ready.
On creating docker comand you just need to map yout dvb device, to be available inside docker, simple as that.

They have all steps on their site, and its very simple.


Sent from my iPad using Tapatalk

I'm using a hdhomerun quad (rather than tbs pcie card) now so should be easier as no mapping all network :)

 

Quick question, is the docker image platform dependant - ie different images for broadwell, bromolow, appollolake etc?

 

Also, I presume I'll be able to map a drive into the container so I can copy my existing tvheadend config files (dvr files etc) and map to //volume1/video/TV_Recording etc?

 

Cheers for the info JMRR :)

Edited by TheBlueVoice

Share this post


Link to post
Share on other sites

Docker platform manages cpu architecture, you dont need to worry about that.

 

here is all you need to configure tvh inside docker on synology.

https://hub.docker.com/r/linuxserver/tvheadend/

 

Just install docker pakage, and my sugestion is to manually run the create comand:

 

adapt this exemple to your needs:

 

docker create \
  --name=tvheadend \
  -e PUID=0 \ #verify on your syno root id mine is 0
  -e PGID=0 \ #verify on your syno root id mine is 0
  -e TZ=Europe/London \ #adapt for your location
  -e RUN_OPTS=--satip_xml http://ip_of_satip_source:port/desc.xml \ #optional for me i used satip from external source, so i need to point in here the start up comand of tvheadend to point for satip server
  -p 9981:9981 \
  -p 9982:9982 \ # i dont use htsp, my is just an iptv server

  -p 9983:9983 \ # i dont use satip as server, just as client, so no need to map this port
  -v <path to data>:/config \ #its beter to save config outside docker , so any upgrade dont delete config. my example(  -v /volume1/docker/tvheadend/config :/config)
  -v <path to recordings>:/recordings \ #same thing for recordings.my example(  -v /volume1/docker/tvheadend/recordings 😕recordings)
  --device /dev/dri:/dev/dri  \ #if you have transcoding capable device map this(this enables vaapi on tvheadend)
  --device /dev/drb:/dev/dvb \ #if no dvb device present remove, i dont have.
  --restart unless-stopped \
  linuxserver/tvheadend

 

and thats it, tvh will be available on port 9981.

ps:uninstall tvh package first to eliminate port conflit.

 

i use 2 instalations of tvh, on on another machine(generic computer) with tbs dvb input device, that servers all tvs on my house by htsp.

the other instalation is on synology just as iptv to when im outside my house, and want to watch television, on computer/ipad/mobile.

this one is vaapi transcoding capable, so doesent use to much network bandwith. this second tvh instalation is conected to first tvh instalation by satip or iptv. i tested both and prefer iptv.

epg works the same way.

 

 

Share this post


Link to post
Share on other sites

That's great info, thanks again JMMR, you helped me sort the tbs dvb open source linux modules a couple of years back :)

 

One final question, what xpenology loader/model are you running? I presume 1.04b/918+ to get the hw transcode?

 

Share this post


Link to post
Share on other sites

yes i was

 

was using asrock j5005 and 1.04b/918+, on a original serial number and mac address. transcoding was activated and working exelent.

but i tried to update dsm verstion to 6.2.2 and fu*ed up my instalation, so had to start over a new instalation on a HPE microserver gen 8, on 3615 loader, and migrated all data.

 

now my main tvh instalation is ubuntu minimal on asrock j5005, and only one instalations to all devices with vaapi enabled.

my dsm instalations is on HPE MS gen8.

 

i few days back i tried to compile tbs drivers to 918+, but didnt had success.

it would be funny to have again all setups combined on same macinhe( dsm+dvb and tvh on docker).maybe some one can help.

 

on a side note, on this docker image its very easy to compile tvh with only modules you use.

i compile mine withou satip server, without hdhomerun, no cas.....and removed a lot of other things a didnt use, its like a light instalation, try this as next step if your initial setups works as you want.

 

Share this post


Link to post
Share on other sites

Ah poop, just got chance to try running tvh in the docker but still same continuity errors :(

 

I'm wondering if it's because I'm running the 918+ image on Haswell cpu (i3 4150) ? 

Share this post


Link to post
Share on other sites

Deffo not signal as running tvheadend on another machine works fine (hdhomerun as source is very useful for this type of trouble shooting!)..

 

Think I've just narrowed it down to something in my synology SYSTEM SOFTWARE setup :(

 

Originally I was running  1.03b 3617.

I created a new boot usb stick with 1.04b 918+ 

booted up and migrated disks using the same pat no (but 918+).

reinstalled tvheadend (as 918 requires apollow not broadwell)

and found continuity problems.

 

Swapping back to original boot usb (1.03b / 3617), migrating again, and reinstalling tvheadend all was well no continuity errors...

 

Swapped back again to  1.04b 918+  this morning and migrated again to try docker tvheadend - same problems with continuity errors...

 

So just tried  1.04b 918+ (same stick) but with a totally fresh install (well, I mean clean) hard disk and native tvh now works fine.

 

So looks like something being left over on the system partion causing problems. Haven't a clue where to start there though lol!

 

 

Edited by TheBlueVoice

Share this post


Link to post
Share on other sites

AH spoke too soon, while no continuity errors, tvh crashed after awhile:

 

 [ 5138.173447] tvh:mtimer[16313]: segfault at 10 ip 0000559fa6e59e44 sp 00007f57d446b9d0 error 4 in tvheadend[559fa6bc4000+cce000]
 

All this just to get plex hw transcode hehe :)

Share this post


Link to post
Share on other sites

I have the following issue with my system: Asrock J3455-ITX with a SSD for docker and Jun's 1.04b 918+ with different extras tested and tvheadend both as a docker image as well as a community package.

 

Tvheadend (iptv) does not work properly: Picture and sound are not transmitted with the necessary speed. Viewing TV is impossible. The iptv stream is OK and works properly with VLC. I tested the setup with different docker installations and finally I installed the community package as an app within DSM. The result is the same with both installations. I also tried a different nic (USB - AX88179) with the same result. I even tested a clean install as well as Jun’s 1.02b with 3615xs.

 

Since the ssd is fast enough I don’t understand where a bottleneck could be. I moved from a Terramaster NAS with DSM 6.1 3615xs to the J3455-ITX system. The same setup with the previous system worked like a charm.

WARNING] TS: ip1/xxx/ HD: H264 @ #101 Continuity counter error (total 30)[0m
WARNING] TS: ip1/xxx/ HD: AC3 @ #301 Continuity counter error (total 27)[0m
WARNING] TS: ip1/xxx/ HD: AAC-LATM @ #302 Continuity counter error (total 14)[0m
WARNING] TS: ip1/xxx/ HD: AAC LATM @ #303 Continuity counter error (total 15)[0m
WARNING] TS: ip1/xxx/ HD: TELETEXT @ #277 Continuity counter error (total 17)[0m
WARNING] TS: ip1/xxx/ HD: AC3 @ #301 Continuity counter error (total 17)[0m
WARNING] TS: ip1/xxx/ HD: H264 @ #101 Continuity counter error (total 19)[0m

Any idea how to fix this problem?

Thank you.

Edited by Polanskiman
Added code tag.

Share this post


Link to post
Share on other sites

Furthermore to my previous post I tried TVHeadend with the same board with Linux Mint and it runs without continuity counter errors. I believe it is related to some driver but I don't know how to fix it. I even tried another NIC (USB3 dongle ax88179 ) with the same result. With the  continuity counter error it is impossible to watch TV.

Share this post


Link to post
Share on other sites

I finally changed the board from J3455 to J4105. Now everything is working as expected. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.