[Support] Linuxserver.io - TVHeadend


1209 posts in this topic Last Reply

Recommended Posts

Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='tvheadend' --net='host' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -e 'PGID'='100' -e 'PUID'='99' -e 'TCP_PORT_9981'='9981' -e 'TCP_PORT_9982'='9982' -e 'TCP_PORT_9983'='9983' -e 'RUN_OPTS'='--satip_xml http://192.168.1.1:49000/satipdesc.xml' -v '/mnt/user/appdata/tvheadend':'/config':'rw' -v '/mnt/user/Media/RECORD/':'/recordings':'rw' -v '/mnt/user/appdata/tvheadend/logos/':'/logos':'rw' --device=/dev/dri 'linuxserver/tvheadend' 

63927e362b58a0124191be5cfc29cd5ef57436a0bb8eea72798bb12d368baa36

The command finished successfully!

Link to post
  • Replies 1.2k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Application Name: TVHeadend Application Site: https://tvheadend.org/ Docker Hub: https://hub.docker.com/r/linuxserver/tvheadend/ Github: https://github.com/linuxserver/docker-tvheadend

You need to install the driver to use your adapter. Then use /dev/dvb as the path for the device pass through. If you are using 6.9.x I don't know if the permissions are set correctly, so make sure no

You need to configure the grabber you want to use, then run it, then map epg source to the channel. There is a link in the first post to the readme on github which has information about configuring yo

Posted Images

1 minute ago, alturismo said:

Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='tvheadend' --net='host' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -e 'PGID'='100' -e 'PUID'='99' -e 'TCP_PORT_9981'='9981' -e 'TCP_PORT_9982'='9982' -e 'TCP_PORT_9983'='9983' -e 'RUN_OPTS'='--satip_xml http://192.168.1.1:49000/satipdesc.xml' -v '/mnt/user/appdata/tvheadend':'/config':'rw' -v '/mnt/user/Media/RECORD/':'/recordings':'rw' -v '/mnt/user/appdata/tvheadend/logos/':'/logos':'rw' --device=/dev/dri 'linuxserver/tvheadend' 

63927e362b58a0124191be5cfc29cd5ef57436a0bb8eea72798bb12d368baa36

The command finished successfully!

 

Try a fresh appdata folder. 

Link to post
8 minutes ago, alturismo said:

no change, fresh setup started, went fast through network settings, stream settings are similar ...

 

What does the version say? 

I have the codec profiles tab on multiple tvheadend servers here. 

Link to post

still doesnt work, but 1 step further at least ;)

 

i check with the settings where there is an error

 

2018-08-05 19:07:30.103 transcode: 0002: 01:H264: ==> Using profile h264_vaapi
2018-08-05 19:07:30.103 transcode: 0002: 02:AC3: ==> Using profile webtv-aac
2018-08-05 19:07:30.103 transcode: 0002: 04:DVBSUB: ==> Filtered out
2018-08-05 19:07:30.570 vaapi: VA-API version 0.40.0
2018-08-05 19:07:30.570 vaapi: va_getDriverName() returns 0
2018-08-05 19:07:30.570 vaapi: Trying to open /usr/lib/dri/i965_drv_video.so
2018-08-05 19:07:30.570 vaapi: Found init function __vaDriverInit_0_40
2018-08-05 19:07:30.570 vaapi: /usr/lib/dri/i965_drv_video.so init failed
2018-08-05 19:07:30.570 vaapi: va_openDriver() returns -1
2018-08-05 19:07:30.570 libav: AVHWDeviceContext: Failed to initialise VAAPI connection: -1 (unknown libva error).
2018-08-05 19:07:30.570 vaapi: failed to create a context for device: /dev/dri/renderD128
2018-08-05 19:07:35.672 mkv: WEBM format supports only VP8+VORBIS streams (detected AAC)
Link to post
2 minutes ago, alturismo said:

still doesnt work, but 1 step further at least ;)

 

i check with the settings where there is an error

 


2018-08-05 19:07:30.103 transcode: 0002: 01:H264: ==> Using profile h264_vaapi

2018-08-05 19:07:30.103 transcode: 0002: 02:AC3: ==> Using profile webtv-aac

2018-08-05 19:07:30.103 transcode: 0002: 04:DVBSUB: ==> Filtered out

2018-08-05 19:07:30.570 vaapi: VA-API version 0.40.0

2018-08-05 19:07:30.570 vaapi: va_getDriverName() returns 0

2018-08-05 19:07:30.570 vaapi: Trying to open /usr/lib/dri/i965_drv_video.so

2018-08-05 19:07:30.570 vaapi: Found init function __vaDriverInit_0_40

2018-08-05 19:07:30.570 vaapi: /usr/lib/dri/i965_drv_video.so init failed

2018-08-05 19:07:30.570 vaapi: va_openDriver() returns -1

2018-08-05 19:07:30.570 libav: AVHWDeviceContext: Failed to initialise VAAPI connection: -1 (unknown libva error).

2018-08-05 19:07:30.570 vaapi: failed to create a context for device: /dev/dri/renderD128

2018-08-05 19:07:35.672 mkv: WEBM format supports only VP8+VORBIS streams (detected AAC)

 

It says in the error what you have to do. You have to use codecs that the format supports. 

Link to post
2 minutes ago, alturismo said:

i guess here is the point ... 

 


2018-08-05 19:22:51.576 vaapi: /usr/lib/dri/i965_drv_video.so init failed

2018-08-05 19:22:51.576 vaapi: va_openDriver() returns -1

 

Well, since you are using a cpu that doesn't have full support yet, it's probably the reason. 

Link to post
  • 2 weeks later...

Hi,

 

Today two recordings failed to start.

Where can I find log files as to what may be the cause ?

It has been pretty bullet proof in the recording department until today.

The recordings were set in to be done - as I checked this morning, but they did not fire.

 

Thanks,

Link to post
2 hours ago, vw-kombi said:

Hi,

 

Today two recordings failed to start.

Where can I find log files as to what may be the cause ?

It has been pretty bullet proof in the recording department until today.

The recordings were set in to be done - as I checked this morning, but they did not fire.

 

Thanks,

 

Check the container log. It's on the far right in the container list.

You can also check the reason for the recording error in the failed recordings list in the webui.

Link to post
8 hours ago, saarg said:

 

Check the container log. It's on the far right in the container list.

You can also check the reason for the recording error in the failed recordings list in the webui.

 

Thats the thing - there is no failed recordings - so no reason why.

I have restarted the docker in case that would help - so likely have lost those container logs, but I will have a look.

 

Thanks.

Link to post
10 hours ago, vw-kombi said:

 

Thats the thing - there is no failed recordings - so no reason why.

I have restarted the docker in case that would help - so likely have lost those container logs, but I will have a look.

 

Thanks.

 

If there is no failed recording, then the recording wasn't scheduled.

Is this an auto-rec?

Link to post
45 minutes ago, saarg said:

 

If there is no failed recording, then the recording wasn't scheduled.

Is this an auto-rec?

 

Yep - an autorec.  Same one every day for one, and the other was a weekly.

No change on them.

I usually check every few dasy that everything is scheduled right, and im sure that morning they were both there.

No logs tho - so I guess I wont restart it next time, if this happens again - i know where to look.

Link to post
1 hour ago, vw-kombi said:

 

Yep - an autorec.  Same one every day for one, and the other was a weekly.

No change on them.

I usually check every few dasy that everything is scheduled right, and im sure that morning they were both there.

No logs tho - so I guess I wont restart it next time, if this happens again - i know where to look.

 

Then the epg was probably updated and the schedule was changed and the recording removed. 

This can happen if the provider makes a mistake. So I don't think it was tvheadend related. 

Link to post
10 hours ago, saarg said:

 

Then the epg was probably updated and the schedule was changed and the recording removed. 

This can happen if the provider makes a mistake. So I don't think it was tvheadend related. 

 

very strange.  this was two different channels from 2 providers so I doubt they both stuffed up.

And they were both actually on TV.

The one was repeated so ok on that - they other was not and I was saving them to my documentary folder which is a bit of a pain as I have a missed episode now - may have to buy the DVD when it comes out now!

Link to post
  • 2 weeks later...

may another attempt to figure why hardware vaapi aint working here (im still confused cause in plex docker it works and i assume it also uses ffmpeg)

 

could it be the reason that there are still "old" images inside my docker file ?

 

from cADVisor

linuxserver/tvheadend latest sha256:b5ea96f49d5fbeefc 305.60 MiB 25.8.2018, 00:11:53
linuxserver/tvheadend release-4.2 sha256:c7df7005437e02f15 301.42 MiB 11.8.2018, 00:13:49
linuxserver/tvheadend stable-4.2.1 sha256:c95b6d7a9fec50fb6 283.87 MiB

1.7.2017, 00:42:49

 

and when i check the bash inside my TVH docker

 

root@AlsServer:~# docker exec -ti tvheadend bash
root@AlsServer:/$ vainfo
bash: vainfo: command not found
root@AlsServer:/$

 

the build im using is HTS Tvheadend 4.3-1292~g9b9ee6859, my docker run command

Command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='tvheadend' --net='host' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -e 'PGID'='100' -e 'PUID'='99' -e 'TCP_PORT_9981'='9981' -e 'TCP_PORT_9982'='9982' -e 'TCP_PORT_9983'='9983' -e 'RUN_OPTS'='--satip_xml http://192.168.1.1:49000/satipdesc.xml' -v '/mnt/user/appdata/tvheadend':'/config':'rw' -v '/mnt/user/Media/RECORD/':'/recordings':'rw' -v '/mnt/user/appdata/tvheadend/logos/':'/logos':'rw' -v '/mnt/user/Media/Temp/':'/Temp':'rw' --device=/dev/dri 'linuxserver/tvheadend' 
698398efb4d811165dd260fbdccb376fdf0b906b1077d5abd6ccd3cb9367b6aa

The command finished successfully!

Link to post
8 hours ago, alturismo said:

may another attempt to figure why hardware vaapi aint working here (im still confused cause in plex docker it works and i assume it also uses ffmpeg)

 

could it be the reason that there are still "old" images inside my docker file ?

 

from cADVisor

linuxserver/tvheadend latest sha256:b5ea96f49d5fbeefc 305.60 MiB 25.8.2018, 00:11:53
linuxserver/tvheadend release-4.2 sha256:c7df7005437e02f15 301.42 MiB 11.8.2018, 00:13:49
linuxserver/tvheadend stable-4.2.1 sha256:c95b6d7a9fec50fb6 283.87 MiB

1.7.2017, 00:42:49

 

and when i check the bash inside my TVH docker

 

root@AlsServer:~# docker exec -ti tvheadend bash
root@AlsServer:/$ vainfo
bash: vainfo: command not found
root@AlsServer:/$

 

the build im using is HTS Tvheadend 4.3-1292~g9b9ee6859, my docker run command

Command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='tvheadend' --net='host' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -e 'PGID'='100' -e 'PUID'='99' -e 'TCP_PORT_9981'='9981' -e 'TCP_PORT_9982'='9982' -e 'TCP_PORT_9983'='9983' -e 'RUN_OPTS'='--satip_xml http://192.168.1.1:49000/satipdesc.xml' -v '/mnt/user/appdata/tvheadend':'/config':'rw' -v '/mnt/user/Media/RECORD/':'/recordings':'rw' -v '/mnt/user/appdata/tvheadend/logos/':'/logos':'rw' -v '/mnt/user/Media/Temp/':'/Temp':'rw' --device=/dev/dri 'linuxserver/tvheadend' 
698398efb4d811165dd260fbdccb376fdf0b906b1077d5abd6ccd3cb9367b6aa

The command finished successfully!

 

It's most likely a combination of your hardware in alpha state and the implementation in TVheadend. 

I don't know what vainfo is, but I guess it needs to be installed if you want to run it. 

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

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.