[Support] Linuxserver.io - TVHeadend


1209 posts in this topic Last Reply

Recommended Posts

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 by doron
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

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 :

 

tvh1.PNG.937cf1b54a5da54e62af6ff8541f8cd2.PNG

 

 

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:

 

tvh2.PNG.96263ccccf877f58b21d33ef079b4d5d.PNG

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.

Link to post
  • 1 month later...
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.

Link to post
Posted (edited)
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 by DiscoDuck
Link to post
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.

Link to post

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

Link to post
  • 4 weeks later...

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.

Link to post
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.

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.