No /dev/dvb devices

[Marx]

Hi
I have dual TV tuner which makes two device: /dev/dvb/adapter0 and /dev/dvb/adapter1
Should they be automatically visible in Docker and recognized by NextPVR?
I suppose no. Then, how can I make them visible in Docker?

Edit: I've found that I probably I need
--device /dev/dvb:/dev/dvb
I need just to find out how to use it in Portainer

[mvallevand]

Unless you are using minimum OS like LibreElec using Docker doesn't really have any advantage over running NextPVR on the bare metal once you get into installing firmware and drivers, it's probably harder and definitely wasting memory.

Martin

[Marx]

It's working now, Portainer has devices setting in resources tab. I've passed my device and NextPVR see it. It would be good to add this to docker image description (see https://hub.docker.com/r/linuxserver/tvheadend/)
The problem is now, that my DVB-T device is using local cable provider frequencies, which doesn't exists in default configurations. It's hit & miss trying different countries to scan frequencies i need. I wish NextPVR would allow me to put frequencies configuration, or provide ability to make full scan of all possible frequencies.
Edit: auto-default did the trick and discovered all channels

Is Docker installation supposed to deliver live tv? On channel selection browser popups, but streaming is not happening. Should I pass different port for streaming? Looking at Chrome console I don't see request to different port.


According to Docker choice there's one big advantage - it's very easy to have multiple versions of software and switch between them. I was using VDR for years on Debian, and Debian upgrade was always a headache - is there eTobi repository with correct versions? Debian stable repo usually is much too old, exactly like for Kodi.

[Marx]

I have strange problems when I try to watch live:

Code:

ffmpeg version 4.1.4-1~deb10u1 Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 8 (Debian 8.3.0-6)
  configuration: --prefix=/usr --extra-version='1~deb10u1' --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --a
rch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --
enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libf
reetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt
--enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-l
ibssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --e
nable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --
enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
  libavutil      56. 22.100 / 56. 22.100
  libavcodec    58. 35.100 / 58. 35.100
  libavformat    58. 20.100 / 58. 20.100
  libavdevice    58.  5.100 / 58.  5.100
  libavfilter    7. 40.101 /  7. 40.101
  libavresample  4.  0.  0 /  4.  0.  0
  libswscale      5.  3.100 /  5.  3.100
  libswresample  3.  3.100 /  3.  3.100
  libpostproc    55.  3.100 / 55.  3.100
[http @ 0x557ac8b18d00] HTTP error 404 Not Found
http://127.0.0.1:8866/live?channeloid=7309&transcoder=ad12b7ad-b81b-4412-ad53-bce99029881f&client=6a334e4f-a0f2-4ab8-b0b4-10740f5f243f: Server returned 404 Not Found

I cannot view any channel.

[mvallevand]

If your restart the docker without rebooting does the problem go away? It appears the tuner are disabled, full logs are recommended over snippets.

Martin

[Marx]

I've put logs here
https://pastebin.com/u9ZFfedg
as they're too big to be embedded, and I cannot add attachments here

I see that there's missing file /config/adapter0-DVB-T-channels.conf, and it's true. config folder doesn't have it:

Code:

root@wuwek:/srv/dev-disk-by-label-wd4/dockerconfig# ls -al
total 168
drwxr-xr-x  7 root root  4096 Jan  6 11:50 .
drwxr-xr-x 10 root root  4096 Jan  5 22:41 ..
-rw-r--r--  1 root root 18320 Jan  6 00:54 config.xml
-rw-r--r--  1 root root 18319 Jan  6 00:35 config.xml.old
drwxr-xr-x  2 root root  4096 Jan  6 11:52 logs
drwxr-xr-x  4 root root  4096 Jan  5 22:43 media
-rw-r--r--  1 root root 80896 Jan  6 11:50 npvr.db3
-rw-r--r--  1 root root    65 Jan  6 03:45 recording-backup.xml
-rw-r--r--  1 root root    65 Jan  6 00:10 recording-backup.xml.1
-rw-r--r--  1 root root    65 Jan  6 03:45 recurring-backup.xml
-rw-r--r--  1 root root    65 Jan  6 00:10 recurring-backup.xml.1
drwxr-xr-x  2 root root  4096 Jan  5 22:43 scripts
drwxr-xr-x  2 root root  4096 Jan  5 22:43 thumbs
drwxr-xr-x  3 root root  4096 Jan  5 22:43 web
root@wuwek:/srv/dev-disk-by-label-wd4/dockerconfig#

UI shows I have 57 channels on each adapter, and they're visible in "Channels" and "TV Guide" section

[mvallevand]

If you copy adapter1-DVB-T-channels.conf to adapter0-DVB-T-channels.conf does that change anything? I'm guessing that you copied channels and possibly NextPVR didn't copy the conf file.

Martin

[Marx]

I don't have file adapter1-DVB-T-channels.conf. Isn't NextPVR supposed to make it ourself?

[mvallevand]

Yes but I was thinking there might have been an issue if you copied channels from one tuner to another. If you delete the tuner and scan again does it work? It might be a NextPVR issue saving to the wrong folder on docker.

Martin

[Marx]

I didn't copied anything, it's fresh install.
How can I delete tuner? I see no such option in WebGUI