On 3/17/2021 at 4:25 PM, saarg said:

You can't pass through using /dev/bus/usb as the container doesn't have any drivers.

 

Of course you're right. For some reason I thought the container has the drivers. Thanks! I can now see the adapter just fine.

Edited March 22, 20215 yr by doron

Unable to open /dev/dvb/adapter0/frontend1

 

So I have a DVB-T2 adapter with two frontends/chips - one can do DVB-T and the other can do DVB-T2 (and DVB-C, which I'm not using).

 

I can configure it in tvheadend and everything works fine. I'm mapping two networks - one onto each - and they work nicely, one doing DVB-T and the other doing DVB-T2. All channels are discovered and can be played.

So far so good. This is how the config looks like :

 

 

 

Now, I go and restart the container. 

When it comes up, I see these log messages: 

 

2021-03-22 17:43:21.775 [   INFO] linuxdvb: adapter added /dev/dvb/adapter0
2021-03-22 17:45:04.803 [  ERROR] linuxdvb: unable to open /dev/dvb/adapter0/frontend1

(note it waited about 90 secs between them). From that point on, frontend0 (Realtek chip) is functional, but fronend1 (Sony chip) disappears. Obviously the network/mux and other channels / services that are attached to it are not functional. In the configuration, you see this:

 

The second frontend is just gone.

 

Neither further restarts, nor Unraid reboot or adapter removal/insertion fixes this.

 

One way I found to work around this is to go to /config/input/linuxdvb/adapters in the container, remove the adapters config file, and restart the container. At that point the config file is re-created and lo and behold - both frontends are back in business. Obviously they have new uuids so I need to re-tie them to networks etc. - at which point they become functional again.

 

The next container restart loses the second frontend again. Every time.

 

Any help as to how to tackle this would be greatly appreciated.

Would it be possible to update the ffmpeg shipped with 4.2 so it includes libxml2? Then it should be possible to pipe mdp streams.

18 minutes ago, DiscoDuck said:

Would it be possible to update the ffmpeg shipped with 4.2 so it includes libxml2? Then it should be possible to pipe mdp streams.

Ffmpeg is installed from the alpine repo, so we can't update until alpine updates it.

libxml2 is installed in the container, if that is what's needed.

5 minutes ago, saarg said:

Ffmpeg is installed from the alpine repo, so we can't update until alpine updates it.

libxml2 is installed in the container, if that is what's needed.

Ok. When I just do ffmpeg I get below output, and libxml2 isn't enabled. Maybe I've missed something basic in the configuration?

 

ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9.3.0 (Alpine 9.3.0)
  configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-libdav1d --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --enable-libssh --disable-stripping --disable-static --disable-librtmp --enable-vaapi --enable-vdpau --enable-libopus --enable-libaom --disable-debug
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Use -h to get full help or, even better, run 'man ffmpeg'

 

Edited May 15, 20215 yr by DiscoDuck

15 minutes ago, DiscoDuck said:

Ok. When I just do ffmpeg I get below output, and libxml2 isn't enabled. Maybe I've missed something basic in the configuration?

 

ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9.3.0 (Alpine 9.3.0)
  configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-libdav1d --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --enable-libssh --disable-stripping --disable-static --disable-librtmp --enable-vaapi --enable-vdpau --enable-libopus --enable-libaom --disable-debug
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Use -h to get full help or, even better, run 'man ffmpeg'

 

Then you need to ask alpine Linux to enable it in their ffmpeg build.

Hi,

I am quite nooby in unraid.

I have been running tvheadend for 1 month getting it working fine.

I have it installed in appdata share folder whitch is addressed in the cache (NVME ssd disk).

My doubt is, is it (cache) the best place to run it instead of the array (HDD disk)?

When playing, it is continously writting and deleting data so, the ssd TBW life would be reduced quickly.

HD Channels have a maximum of 20 mbps of quality so HDD disks would satisfy this requirement.

Is it better to move it to a new share folder addressed in the Array (as well as oscam and xteve also)?

 

Thank you

After I updated the container today I get an error that the execution of /bin/tar has been denied and the container isn't able to start, the message repeats over and over again.

 

I attached the log:

tvheadend.log

 

Has something changed that I've been missing?

 

 

Also may I ask what is the difference between the version-9476680f vs. 9476680f-ls100?

I've reverted now back to version: 63784405-ls97 which is running fine.

On 6/10/2021 at 9:54 AM, ich777 said:

After I updated the container today I get an error that the execution of /bin/tar has been denied and the container isn't able to start, the message repeats over and over again.

 

I attached the log:

tvheadend.log 4.4 kB · 0 downloads

 

Has something changed that I've been missing?

 

 

Also may I ask what is the difference between the version-9476680f vs. 9476680f-ls100?

I've reverted now back to version: 63784405-ls97 which is running fine.

I would not advice to use latest unless there is a feature you need. New developer started working on it and it breaks now and then.

 

The two versions are identical.

Hello

 

I'm trying to get an IPTV RTSP mux to work.

My Internet provider allows to stream local (French) TV channels from the "router box" (called Freebox). They provide a .m3u from which I extracted one stream for testing purposes:

rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd

This URL works when opening in VLC.

 

I created a IPTV network and a mux with the URL:

 

And scan fails:

2021-07-30 00:00:40.901 epggrab: rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd in Freebox TV - registering mux for OTA EPG
2021-07-30 00:00:40.904 subscription: 0010: "scan" subscribing to mux "rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd", weight: 5, adapter: "IPTV", network: "Freebox TV", service: "Raw PID Subscription"
2021-07-30 00:00:55.900 mpegts: rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd in Freebox TV - scan no data, failed
2021-07-30 00:00:55.900 subscription: 0010: "scan" unsubscribing

 

I tried to use the local IP of the router (192.168.0.1) and I have the same error (works as well with VLC).

 

I tested and the Docker container seems to access the port with no problem:

root@Tower:~# docker exec -it tvheadend bash
root@21234e9f20e5:/# nc -vz 192.168.0.1 554
192.168.0.1 (192.168.0.1:554) open
root@21234e9f20e5:/# nc -vz mafreebox.freebox.fr 554
mafreebox.freebox.fr (212.27.XXX.XXX:554) open

 

Here is what VLC has to say about the stream:

Any idea why this wouldn't work?

 

Using linuxserver/tvheadend:release-4.2

Edited July 29, 20214 yr by Guillaurent
Offuscating IP

6 hours ago, Guillaurent said:

Any idea why this wouldn't work?

 

 

search for pipe input in tvheadend forums, rtsp needs to be piped through ffmpeg (remuxed to .ts)

2 hours ago, alturismo said:

 

search for pipe input in tvheadend forums, rtsp needs to be piped through ffmpeg (remuxed to .ts)

Thanks for the tip.

 

I gave it a go and did some further testing and it seems that the problem is with codec parameters:

root@Tower:~# docker exec tvheadend ffmpeg -i "rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd"
ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9.3.0 (Alpine 9.3.0)
  configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-libdav1d --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --enable-libssh --disable-stripping --disable-static --disable-librtmp --enable-vaapi --enable-vdpau --enable-libopus --enable-libaom --disable-debug
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
[rtsp @ 0x154c3d28e5c0] UDP timeout, retrying with TCP
[rtsp @ 0x154c3d28e5c0] method PAUSE failed: 551 Option Not Supported
rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd: could not find codec parameters

 

Fixed the UDP timeout, did not change much:

root@Tower:~# docker exec tvheadend ffmpeg -f rtsp -rtsp_transport udp -i "rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd"
ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9.3.0 (Alpine 9.3.0)
  configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-libdav1d --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --enable-libssh --disable-stripping --disable-static --disable-librtmp --enable-vaapi --enable-vdpau --enable-libopus --enable-libaom --disable-debug
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd: could not find codec parameters

 

I tried to specify the input codec (h264) to no avail:

root@Tower:~# docker exec tvheadend ffmpeg -f rtsp -rtsp_transport udp -codec h264 -i "rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd"
ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9.3.0 (Alpine 9.3.0)
  configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-libdav1d --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --enable-libssh --disable-stripping --disable-static --disable-librtmp --enable-vaapi --enable-vdpau --enable-libopus --enable-libaom --disable-debug
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd: could not find codec parameters

 

I'm at lost now...

I've found the issue I was having. The incoming UDP traffic could not get through to the tvheadend container in Network type bridge (or custon bridge).

Switching Network type to Host did the trick but I don't know if there's another way around it.

Hi,

 

I am suffering some periodic cuts (each 7 or 8 minutes).

 

An example of the log is here:

 

2021-08-20 12:23:23.122 capmt: diegonas: normal socket shutdown
2021-08-20 12:23:23.122 capmt: diegonas: Automatic reconnection attempt in 3 seconds
2021-08-20 12:23:26.087 capmt: diegonas: mode 5 connected to 172.18.0.59:9000 (single)
2021-08-20 12:23:26.088 capmt: diegonas: Connected to server 'OSCam v1.20_svn, build r11693 (x86_64-alpine-linux-musl); ' (protocol version 3)
2021-08-20 12:32:24.852 TS: Satelite/10906V/ANTENA 3 HD: H264 @ #163 Continuity counter error (total 1)
2021-08-20 12:32:24.852 TS: Satelite/10906V/ANTENA 3 HD: MPEG2AUDIO @ #98 Continuity counter error (total 1)
2021-08-20 12:32:24.852 TS: Satelite/10906V/ANTENA 3 HD: MPEG2AUDIO @ #99 Continuity counter error (total 1)
2021-08-20 12:32:24.853 descrambler: cannot decode packets for service "ANTENA 3 HD"
2021-08-20 12:40:25.034 TS: Satelite/10906V/ANTENA 3 HD: H264 @ #163 Continuity counter error (total 261)
2021-08-20 12:40:25.034 TS: Satelite/10906V/ANTENA 3 HD: MPEG2AUDIO @ #98 Continuity counter error (total 136)
2021-08-20 12:40:25.034 TS: Satelite/10906V/ANTENA 3 HD: MPEG2AUDIO @ #99 Continuity counter error (total 140)
2021-08-20 12:40:25.034 descrambler: cannot decode packets for service "ANTENA 3 HD"
2021-08-20 12:48:18.379 TS: Satelite/10906V/ANTENA 3 HD: H264 @ #163 Continuity counter error (total 489)
2021-08-20 12:48:18.379 TS: Satelite/10906V/ANTENA 3 HD: MPEG2AUDIO @ #99 Continuity counter error (total 258)
2021-08-20 12:48:18.379 TS: Satelite/10906V/ANTENA 3 HD: MPEG2AUDIO @ #98 Continuity counter error (total 255)
2021-08-20 12:48:18.379 descrambler: cannot decode packets for service "ANTENA 3 HD"
2021-08-20 12:55:25.924 TS: Satelite/10906V/ANTENA 3 HD: H264 @ #163 Continuity counter error (total 872)
2021-08-20 12:55:25.924 TS: Satelite/10906V/ANTENA 3 HD: MPEG2AUDIO @ #99 Continuity counter error (total 414)
2021-08-20 12:55:25.924 TS: Satelite/10906V/ANTENA 3 HD: MPEG2AUDIO @ #98 Continuity counter error (total 408)
2021-08-20 12:55:25.924 descrambler: cannot decode packets for service "ANTENA 3 HD"

 

Someone now where the problem is?

 

Thank you

Others may have other insights, but for me with DVB-T/T2, continuity errors were normally caused by poor signal.

 

Do you ever get dropouts in heavy rain or anything like that?

this is most likely weak signal, bad USB (if its a USB Tuner), ....

I‘m using this Image now about a year. But from ohne day to the other, ist seems EPG stoped working. Am I the only one with this issue?

I am running this docker with the deafult (latest) tag.

Current version: HTS Tvheadend version 4.3-1979~g8fc2dfa7e

 

I am not sure if that is currently recommended or not?

 

 

When recording via autorecs the recordings fail with a file missing error,

the scheduled recording "starts" there is no file outputted: During a "recording":  Status > Subscriptions lists the output as 0kb/s and there is no file created in the unRAID filesystem

 

It is not a permission issue (either filesystem or user permissions) as: If I stop the autorecording and start it manually via either WebUI or Kodi the recording works correctly.

 

The Priority and DVR Configurations for the autorecs are the same as manually triggered recordings but only manully triggered or schedued recordings work.

 

I have tried searching this bug in regular tvheadend forums but got nowhere.

 

Anyone here having the same issue?.

6 hours ago, Capt.Insano said:

Anyone here having the same issue?.

no ... (i love this question )

 

6 hours ago, Capt.Insano said:

Status > Subscriptions lists the output as 0kb/s and there is no file created in the unRAID filesystem

and input ? also 0kb ?

 

6 hours ago, Capt.Insano said:

I have tried searching this bug in regular tvheadend forums but got nowhere.

 

what does your tvheadend logs say ? enabled debug information ?

 

with those infos you prolly should check at tvheadend forums or you may already have further informations ...

3 hours ago, alturismo said:

and input ? also 0kb ?

 

No, input shows a correct kp/s for the stream (usually about 3k).

If I manually trigger/schedule the recording the input and output kb/ps are the same and the recorded file is being created. 

 

I have not seen anything in the TVheadend logs, it is as if TVHeadend thinks it is recording correctly but then after the recording realises that the file is missing. But I must check the logs again.

8 minutes ago, Capt.Insano said:

No, input shows a correct kp/s for the stream (usually about 3k).

 

so, this is usally a write error then

 

there is a debug console in the buttom, take a look there when a schedule is starting

 

Hi,

i installed for the first time a PCIE TV card, a TBS-6902.

I installed the DVB drivers and then this container. Configured as host and privileged mode.

The webui is not loading on port 9981, nothing happens ERR_CONNECTION_REFUSED

I tried to load with different clients, even android devices.

 

I tried with network custom br0 and a free ip, same result

Same for network bridge.

 

*update a day later*

i entered the console and checked with "netstat -lpnt" if the service is running and listening -> it was not.

 

so i entered in the container console tvheadend -C and everything startet up. Will check later if it will start automatically next docker restart.

 

unraid-diagnostics-20211123-2234.zip

Edited November 24, 20214 yr by Grobalt
added diagnostics

On 10/19/2021 at 10:35 PM, Capt.Insano said:

I am running this docker with the deafult (latest) tag.

Current version: HTS Tvheadend version 4.3-1979~g8fc2dfa7e

 

I am not sure if that is currently recommended or not?

 

 

When recording via autorecs the recordings fail with a file missing error,

the scheduled recording "starts" there is no file outputted: During a "recording":  Status > Subscriptions lists the output as 0kb/s and there is no file created in the unRAID filesystem

 

It is not a permission issue (either filesystem or user permissions) as: If I stop the autorecording and start it manually via either WebUI or Kodi the recording works correctly.

 

The Priority and DVR Configurations for the autorecs are the same as manually triggered recordings but only manully triggered or schedued recordings work.

 

I have tried searching this bug in regular tvheadend forums but got nowhere.

 

Anyone here having the same issue?.

 

Update to this issue incase anyone else faces a similar issue:

 

Took me longer than it should have to figure this out.

 

The recording issue was based on EIT (programme runtime) setting in recorder:

 

 

 

This should be set to DISABLED in my case, there is some issue in getting this EPG data. Disabling "Use EPG running state" fixes it in my case.

 

 

Thanks to all devs

 

docker tvheadend container is getting corrupted. The dri/dvb lines from the template is enumerating a dozen times, not sure why.

I deleted the template and re-downloaded from scratch, and then removed the offending lines, as they are optional and not needed. But it keeps coming back.

Never seen anything like this before....

Look at attached screenshot...

 

Edited February 6, 20224 yr by bucky2076
attached screenshot

9 hours ago, bucky2076 said:

docker tvheadend container is getting corrupted. The dri/dvb lines from the template is enumerating a dozen times, not sure why.

I deleted the template and re-downloaded from scratch, and then removed the offending lines, as they are optional and not needed. But it keeps coming back.

Never seen anything like this before....

Look at attached screenshot...

 

I have the exact same issue when I updated the docker this morning.  Deleted the extra lines, but still does not work and unable to start, just get execution error.  This is not the first time either, but I think I just started from scratch last time.  I'm hoping not to have to take that kind of drastic action again. (It's a pain in the arse)