Posts by elonesna

Geniatech HD Star DVB-S2 USB2.0 works fine for me but I don't recommend anyone to use USB tuners with LibreELEC, because with any update the drivers can stop working.

I leave you this information so you can study my case:

##############################################
#                 LibreELEC                  #
#            https://libreelec.tv            #
##############################################
LibreELEC (official): 9.2.6 (Generic.x86_64)

LibreELEC:~ # uname -r
5.1.16

LibreELEC:~ # cat /etc/os-release
NAME="LibreELEC"
VERSION="9.2.6"
ID="libreelec"
VERSION_ID="9.2"
PRETTY_NAME="LibreELEC (official): 9.2.6"
HOME_URL="https://libreelec.tv"
BUG_REPORT_URL="https://github.com/LibreELEC/LibreELEC.tv"
BUILD_ID="6bd7e983a6c4b748eff6f537077ee156bb800e48"
OPENELEC_ARCH="Generic.x86_64"
LIBREELEC_ARCH="Generic.x86_64"
LIBREELEC_BUILD="official"
LIBREELEC_PROJECT="Generic"

LibreELEC:~ # lsusb
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 004: ID 0bc2:ab62 Seagate RSS LLC
Bus 003 Device 003: ID 2109:0813 VIA Labs, Inc.
Bus 003 Device 002: ID 2109:0813 VIA Labs, Inc.
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 8087:0a2a Intel Corp.
Bus 002 Device 005: ID 18b4:1689 e3C Technologies DUTV009
Bus 002 Device 007: ID 1f4d:3000 G-Tek Electronics Group
Bus 002 Device 006: ID 045e:02d5 Microsoft Corp. Xbox One Digital TV Tuner
Bus 002 Device 004: ID 2109:2813 VIA Labs, Inc.
Bus 002 Device 002: ID 2109:2813 VIA Labs, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

LibreELEC:~ # lsmod
Module                  Size  Used by
8021q                  24576  0
veth                   28672  0
xt_nat                 16384  13
xt_tcpudp              20480  39
ipt_MASQUERADE         20480  16
nf_conntrack_netlink    36864  0
nfnetlink              16384  2 nf_conntrack_netlink
iptable_nat            16384  1
xt_addrtype            16384  2
iptable_filter         16384  1
ip_tables              28672  2 iptable_filter,iptable_nat
xt_conntrack           16384  1
x_tables               28672  7 xt_conntrack,iptable_filter,xt_tcpudp,ipt_MASQUERADE,xt_addrtype,xt_nat,ip_tables
nf_nat                 36864  3 ipt_MASQUERADE,xt_nat,iptable_nat
nf_conntrack           81920  5 xt_conntrack,nf_nat,ipt_MASQUERADE,xt_nat,nf_conntrack_netlink
nf_defrag_ipv6         24576  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
br_netfilter           28672  0
bridge                131072  1 br_netfilter
stp                    16384  1 bridge
llc                    16384  2 bridge,stp
overlay               106496  15
rc_su3000              16384  0
ds3k                   49152  1
iwlmvm                299008  0
mac80211              585728  1 iwlmvm
dvb_usb_dw2102         73728  1
iwlwifi               278528  1 iwlmvm
tda18250               24576  1
wl                   6381568  0
mn88472                24576  1
intel_powerclamp       20480  0
intel_rapl             24576  0
snd_hda_codec_realtek    94208  1
snd_hda_codec_generic    73728  1 snd_hda_codec_realtek
snd_hda_codec_hdmi     53248  1
cfg80211              577536  4 wl,iwlmvm,iwlwifi,mac80211
snd_hda_intel          36864  0
snd_hda_codec         106496  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hwdep              16384  1 snd_hda_codec
snd_hda_core           69632  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
dvb_usb_dib0700       163840  0
dib3000mc              20480  1 dvb_usb_dib0700
dib9000                36864  1 dvb_usb_dib0700
dib0070                20480  1 dvb_usb_dib0700
dib7000m               24576  1 dvb_usb_dib0700
dibx000_common         16384  4 dib9000,dib7000m,dib3000mc,dvb_usb_dib0700
dib0090                36864  1 dvb_usb_dib0700
dvb_usb                32768  2 dvb_usb_dw2102,dvb_usb_dib0700
pcc_cpufreq            20480  0
mxl5005s               49152  1
ec100                  20480  1
btusb                  49152  0
btrtl                  20480  1 btusb
btbcm                  16384  1 btusb
btintel                24576  1 btusb
bluetooth             462848  5 btrtl,btintel,btbcm,btusb
dvb_usb_ec168          20480  0
dvb_usb_v2             40960  1 dvb_usb_ec168
rc_core                40960  6 dvb_usb_v2,rc_su3000,dvb_usb,dvb_usb_dw2102,dvb_usb_dib0700
dvb_core              131072  5 dib9000,dvb_usb_v2,dvb_usb,mn88472,dvb_usb_dw2102
videobuf2_vmalloc      20480  1 dvb_core
videobuf2_memops       20480  1 videobuf2_vmalloc
videobuf2_common       53248  1 dvb_core
videodev              180224  1 videobuf2_common
media                  45056  5 videodev,dvb_usb_v2,dvb_usb,dvb_core,videobuf2_common
ecdh_generic           28672  1 bluetooth
rfkill                 20480  3 bluetooth,cfg80211
wireguard             200704  0
ip6_udp_tunnel         16384  1 wireguard
udp_tunnel             16384  1 wireguard

Forget a USB tuner, you're going to have a lot of problems! Buy a separate tuner: enigma2, SAT>IP, vboxcomm, ... and connect it to your LibreELEC tvheadend via SAT>IP protocol or m3u playlists

I wish I was wrong but I think LibreELEC arm devices cannot easily use a WireGuard server, in fact the LibreELEC.wiki doesn't even mention it. Conversely x86_64 devices running LibreELEC can run the excellent WireGuard server service with docker linuxserver/wireguard.

If you cannot change your VPN server device then I recommend that you use ZeroTier through the docker zyclonite/zerotier service because it works very well both on x86_64 devices and on arm devices, there is no server here but a private VPN network where you can connect devices and establish simple rules of routing and egress to the internet.

Use any storage mount you want. For many years I have used a hard drive connected to my router with VPN server functions because it allowed me to access it day and night at any time. Since I decided to launch a LibreELEC server with 24/7 functions of NAS server, backup server, surveillance storage server, TV server, VPN server, ... my storage mount is managed by LibreELEC.

I'm surprised no one answered you. LibreELEC includes a samba test connection service "/storage/.config/system.d/cifs.mount.sample" and another nfs "/storage/.config/system.d/nfs.mount.sample". Please, in your case this is what you should use.

In docker there are three basic concepts: (1) image (2) container (3) service configuration and data. Storage of images and containers are managed by docker, storage of configuration and service data is managed by the user during the container creation process.

I may be speaking Chinese so keep studying here https://docs.docker.com/

Quote from VLouis

Nov 09 04:26:20.700309 LE tvheadend[360]: TS: PRG-U/642MHz/Nova: AAC-LATM @ #274 Continuity counter error

....

Nov 09 04:26:27.350300 LE tvheadend[360]: tsfix: transport stream AAC-LATM, DTS discontinuity. DTS = 22256813, last = 22068651

....

You have a lot of transport stream AAC-LATM, DTS discontinuity and Continuity counter error, so trying with another version of TVH, another tuner, checking the antenna cable and connections... could be a good idea...

I have seen your log and it reminds me of the logs that occur during the IPTV broadcast of the free Pluto TV channels in tvheadend (I use version 4.3 of docker linuxserver/tvheadend for LE x86_64). Within this service I have installed, and absolutely updated, the ffmpeg, cvlc and streamlink players that I encapsulate through pipe for tvheadend. Well, with these players, the sound is often lost when discontinuities appear, that is, when ads are inserted or a new video clip starts in the stream (this does not happen when the stream is played from the VLC application on a PC ). Sound can be recovered by enabling and disabling the passthrough option within Kodi in LE, until the next discontinuity.

The only solution I've found is to use the docker proxy dnsforge/xteve processing the output to tvheadend with xteve's internal ffmpeg, and pipe this output with cvlc, only then does everything work fine except the loss of a few seconds of image and sound frames in the discontinuities. This solution has a problem: it cannot be applied to the case of live television from a tuner.

My suspicion is that it is a problem with tvheadend or Kodi's native player. The logs do not provide any clues.

I said what I said because I assume Hauppauge HD PVR 2 is capable of writing to a hard drive. If you need a LibreELEC driver then you're screwed!

If your Hauppauge HD PVR 2 is capable of recording to (1) a local network drive or (2) a USB hard drive that is also accessible from the local network, then yes, you could share that you're recording, with any device, it doesn't have to be LibreELEC, that can also access the same hard drive without using ffmpeg or programming anything.

What you cannot do is connect your Hauppauge HD PVR 2 to your LibreELEC device via USB and use the LibreELEC hard drive.

I use VPN connections a lot and I have not detected any major problems. Check your device's routing table with the SSH command 'route', and also check that your DNS are also routed.

Note: I have also seen that sometimes small internet providers do strange things that prevent the proper functioning of VPN connections, in this case try another internet provider.

Read here: Supported wireless devices list

Look inside the /etc/iptables directory, there you can learn how LE builds the firewall. For testing, build your own firewall in /storage/.config/iptables/rules.v4 or rules.v6, and enable it in Settings:System:Network.

Although in the period 1990-2000 I dedicated ten years of my life developing applications for factories and industrial manufacturing processes, in 2019 I knew very little about Linux and since I was interested in satellite television I started with a TV Box S912 and the CoreELEC operating system. That was a discovery for me, I had finally found a very stable operating system, safe from the errors of desktop Linux operating systems, and also the discovery of docker virtual services, which allow services to be transferred from one machine or operating system, to another, without changing anything.

When in 2020 I decided to install a home server I had no doubts: it would be a cheap mini PC with the LibreELEC operating system. I am very grateful to CoreELEC and LibreELEC for being the tool that has allowed me to learn Linux.

I would not change LibreELEC for any other Linux x86 operating system. It is true that LE has many limitations but in return it offers you stability, my LE server has been on for 22 months, restarting automatically every day, without any problem, keeping backup copies of PCs and smartphones, managing our VPN remote access and cameras security, local and remote, saving our documents and our multimedia library and giving us impressive television services even when we are traveling.

As the development times for stable LibreELEC updates are long, I am preparing the alternative of replacing my LE server with an Ubuntu* server with updated media drivers, ssh and samba services, and docker services exported unchanged from LE; all this works now. Since this will be a server I'm thinking of replacing Kodi with a Windows remote desktop service. Obviously, I would never install a NAS server.

* An Ubuntu server also has bugs and errors, I have seen them in the docker service of the snap library, to solve this I always follow the installation recommendations of the software creator, and not the recommendations of third parties.

In short, stick with LibreELEC or create your own server.

Perhaps I am wrong in thinking that audio loss in live TV is associated with streaming errors, and not with the type of hardware. I have observed this on PlutoTV live IPTV TV streams where continuity errors are absolutely normal and predictable when inserting ads. I've tried to fix it by processing the stream inside tvheadend with ffmpeg, cvlc and streamlink (the best) pipes and while some work better than others I haven't totally solved this problem.

Checking the logs does not solve the problem, only video and audio discontinuity errors are observed, and sometimes the audio is lost or the video works stutters. When this happens, the solution that always works is to stop the playback of the TV channel and start it again, for the audio there is also the alternative of changing and resetting the passthrough switch, it seems as if the driver had been damaged, but I do not have the knowledge necessary to restart the drivers using linux commands.

I don't know of any player that knows how to handle discontinuity errors.

Thank you! It doesn't seem right to me that the existence of any file inside the internal /config/custom-cont-init.d directory, even the README.txt file created by the docker linuxserver/tvheadend service itself, prevents the container from working

WireGuard connman for LE is not at all flexible, on VPN connections it requires static IP addresses and tunnels all communications to the VPN server.

How do I solve the problem when I want to do split routing?

With LE I think there is only one solution: use ZeroTier VPN networks (through docker services) instead of WireGuard, because they allow flexible routing.

On my CoreELEC devices I tend to use Entware WireGuard to not route all traffic to the VPN server, but this is not easy to do on LibreELEC.

Complain in a Kodi forum but I think that no one will pay attention to you there either. Free stuff has the problem that they support few variations, take it or leave it

I thought it was solved but no, after a reboot wireguard and tvheadend still don't work.

SOLVED!

The problem seems to be some kind of incompatibility in the contents of the 'custom-cont-init.d' and 'custom-services.d' directories in the new versions of the services released by 'linuxserver'. I use these directories to launch scripts before the tvheadend service starts: install 'streamlink', install 'cvlc' and set epg collectors, all of which are lost with each update of the docker image. My workaround is to do these operations manually on every update.

FINALLY:

I have automated the process by creating a directory 'autostart.d' added to the docker install command as

docker run -d \

...

-v /storage/.config/dockers/tvheadend/autostart.d:/custom-cont-init.d \

...

linuxserver/tvheadend

all scripts inside 'autostart.d' will be executed before starting the 'tvheadend' service. Now everything is compatible with the 'linuxserver' requirements.