August 5, 20187 yr 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' 63927e362b58a0124191be5cfc29cd5ef57436a0bb8eea72798bb12d368baa36The command finished successfully!
August 5, 20187 yr 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' 63927e362b58a0124191be5cfc29cd5ef57436a0bb8eea72798bb12d368baa36The command finished successfully! Try a fresh appdata folder.
August 5, 20187 yr no change, fresh setup started, went fast through network settings, stream settings are similar ...
August 5, 20187 yr 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.
August 5, 20187 yr Just now, alturismo said: HTS Tvheadend 4.3-334~g7db25fab0 Latest version has 4.3-1292, so you have an old version. Update it, and it should appear.
August 5, 20187 yr omg ... yes its there now thanks alot ... i changed the tag so 4.3 installed didnt checked for an update after that ...
August 5, 20187 yr 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)
August 5, 20187 yr 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.
August 5, 20187 yr 2018-08-05 19:07:35.672 mkv: WEBM format supports only VP8+VORBIS streams (detected AAC) thats audio only ... i guess its something else ...
August 5, 20187 yr may also cause i use coffee lake ... no idea yet, will try l8 with some settings thanks for your help
August 5, 20187 yr 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
August 5, 20187 yr 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.
August 15, 20187 yr 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,
August 15, 20187 yr 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.
August 15, 20187 yr 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.
August 16, 20187 yr 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?
August 16, 20187 yr 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.
August 16, 20187 yr 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.
August 16, 20187 yr 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!
August 29, 20187 yr 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!
August 29, 20187 yr 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.
August 29, 20187 yr you probably right, as mine is 965 ... and all here is 915, just wondered me why plex can use it and TVH not, nvm and yes, vainfo shows VAAPI Infos and needs to be installed.
August 30, 20187 yr I might have had this problem for a while as it occurs on rarely watched channels thankfully, but I can't switch between muxes i.e. if I want to watch a channel on a new mux it says no free adapter available. Is anyone else having this problem? Also, posted on TVH forums - https://tvheadend.org/boards/14/topics/33990 Thanks
August 30, 20187 yr How many tuners are active in TVH ? DVB Inputs, Adapters ... all mapped to DVB-C ?
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.