Tvheadend

You could try using "force_pid_filter_usage".

add:

"options dvb_usb force_pid_filter_usage=1" to /etc/modprobe.d/dvb.conf

Thanks, but I don't have this file: /etc/modprobe.d/dvb.conf

Do I need to make this file?

One little thing - if I disable ALL EPG Grabber Modules in Configuration > Channel/EPG > EPG Grabber Modules, quantity of errors is much less, about 25 per hour.

I made dvb.conf file in modprobe.d with "options dvb_usb force_pid_filter_usage=1" but it doesn't change situation

This sounds like data overload on the single USB bus - not much you can do unless you use a separate backend with a separate Ethernet (giga preferred) & USB ports.

Mark Clarkstone wrote:

This sounds like data overload on the single USB bus - not much you can do unless you use a separate backend with a separate Ethernet (giga preferred) & USB ports.

What does it mean? Do I need powered USB hub or something like this?

Jan Kowalski wrote:

Mark Clarkstone wrote:

This sounds like data overload on the single USB bus - not much you can do unless you use a separate backend with a separate Ethernet (giga preferred) & USB ports.

What does it mean? Do I need powered USB hub or something like this?

The Pi shares a single USB bus between it's USB Ports and Ethernet. This explains it better than I could.

Just couple words:

1. Tvh shows bandwidth (in Status tab)
- for HD channels: 3500-6500 kb/s
- for SD channels: 2400-3500 kb/s

2. If I use etc/modprobe.d/dvb.conf with:
"options dvb_usb force_pid_filter_usage=1"
or
"options dvb_usb_v2 force_pid_filter_usage=1"

It won't show anything. check

sudo modinfo {dvb_usb,dvb_usb_v2} | less

Syslog show nothing about pid filtering options. But When I use

"options dvb_usb_dvbsky force_pid_filter_usage=1"

Syslog shows:

dvb_usb_dvbsky: unknown parameter 'force_pid_filter_usage' ignored

That's because that module doesn't support the option. :p

I think about buying other tuner: Hauppauge WinTV-Solo which provide DVB-C. Anyone knows that this tuner can handle "force_pid_filter_usage" ???

Well, is that:

1. My dvb.conf file has:
options dvb_usb_v2 force_pid_filter_usage=1
options dvb_usb_v2 disable_rc_polling=1
options dvb_usb_dvbsky disable_rc=1

After reboot

Module = "dvb_usb_v2" 

  Attributes:
    coresize            = "16424" 
    initsize            = "0" 
    initstate           = "live" 
    refcnt              = "1" 
    srcversion          = "B48D772FD4CD86C536DE815" 
    taint               = "" 
    uevent              = <store method only>
    version             = "2.0" 

  Parameters:
    disable_rc_polling  = "1" 
    force_pid_filter_usage= "1" 

  Sections:
    .ARM.exidx          = "0x7f165ba0" 
    .ARM.extab          = "0x7f165a20" 
    .bss                = "0x7f165ec0" 
    .gnu.linkonce.this_module= "0x7f165cc0" 
    .note.gnu.build-id  = "0x7f16521c" 
    .rodata             = "0x7f1652ac" 
    .rodata.str1.4      = "0x7f1653a0" 
    .strtab             = "0x7f16a020" 
    .symtab             = "0x7f169000" 
    .text               = "0x7f163000" 
    __kcrctab           = "0x7f165288" 
    __ksymtab_strings   = "0x7f1652d8" 
    __ksymtab           = "0x7f165240" 
    __mcount_loc        = "0x7f1659a0" 
    __param             = "0x7f165978"

Module = "dvb_usb_dvbsky" 

  Attributes:
    coresize            = "10092" 
    initsize            = "0" 
    initstate           = "live" 
    refcnt              = "1" 
    srcversion          = "05A35D125162F5B71AA58C1" 
    taint               = "" 
    uevent              = <store method only>

  Parameters:
    adapter_nr          = "-1,-1,-1,-1,-1,-1,-1,-1" 
    disable_rc          = "1" 

  Sections:
    .ARM.exidx          = "0x7f175758" 
    .ARM.exidx.exit.text= "0x7f175388" 
    .ARM.exidx.init.text= "0x7f175374" 
    .ARM.extab.exit.text= "0x7f17537c" 
    .ARM.extab.init.text= "0x7f175368" 
    .ARM.extab          = "0x7f175668" 
    .bss                = "0x7f175d40" 
    .data               = "0x7f1757f8" 
    .exit.text          = "0x7f17516c" 
    .gnu.linkonce.this_module= "0x7f175b40" 
    .init.text          = "0x7f178000" 
    .note.gnu.build-id  = "0x7f175188" 
    .rodata             = "0x7f1751ac" 
    .rodata.str1.4      = "0x7f175390" 
    .strtab             = "0x7f178b0c" 
    .symtab             = "0x7f17802c" 
    .text               = "0x7f174000" 
    __mcount_loc        = "0x7f175618" 
    __param             = "0x7f1755f0"

filename:       /lib/modules/4.9.35-v7+/kernel/drivers/media/usb/dvb-usb/dvb-usb.ko
license:        GPL
description:    A library module containing commonly used USB and DVB function USB DVB devices
author:         Patrick Boettcher <[email protected]>
version:        1.0
srcversion:     5052817F8F74754EDB57F76
depends:        rc-core,dvb-core
intree:         Y
vermagic:       4.9.35-v7+ SMP mod_unload modversions ARMv7 p2v8 
parm:           debug:set debugging level (1=info,xfer=2,pll=4,ts=8,err=16,rc=32,fw=64,mem=128,uxfer=256  (or-able)). (debugging is not enabled) (int)
parm:           disable_rc_polling:disable remote control polling (default: 0). (int)
parm:           force_pid_filter_usage:force all dvb-usb-devices to use a PID filter, if any (default: 0). (int)
filename:       /lib/modules/4.9.35-v7+/kernel/drivers/media/usb/dvb-usb-v2/dvb_usb_v2.ko
license:        GPL
description:    DVB USB common
author:         Antti Palosaari <[email protected]>
author:         Patrick Boettcher <[email protected]>
version:        2.0
srcversion:     B48D772FD4CD86C536DE815
depends:        rc-core,dvb-core
intree:         Y
vermagic:       4.9.35-v7+ SMP mod_unload modversions ARMv7 p2v8 
parm:           disable_rc_polling:disable remote control polling (default: 0) (int)
parm:           force_pid_filter_usage:force all DVB USB devices to use a PID filter, if any (default: 0) (int)

total 0
drwxr-xr-x 2 root root    0 Nov  7 20:54 .
drwxr-xr-x 7 root root    0 Nov  7 20:42 ..
-r--r--r-- 1 root root 4096 Nov  7 20:46 adapter_nr
-rw-r--r-- 1 root root 4096 Nov  7 20:46 disable_rc

I wondering what means this (after command: systool -v -m dvb_usb_dvbsky):

Parameters:
    adapter_nr          = "-1,-1,-1,-1,-1,-1,-1,-1"

Looks weird

adapter_nr allows you to assign a custom adapter number. I believe -1 basically tells the driver to pick the next number available. Nothing to worry about.

So, after disabling RC, and adding options dvb_usb_v2 force_pid_filter_usage=1, is still the same amount of errors, nothing change.

I wondering about two things:
1. Is my signal isn't too.... high. Is about -50 dBm, SNR 34 dB
2. Order RPi3.

Check that the chipset isn't the same as the one you already have (I think they are).

Getting an RPi3 might not solve the problem either. Hell an Orange Pi zero might be worth a shot if you want something cheap that doesn't share usb buses with Ethernet!

If you really want to be sure that tvh is using filtering reduce "Maximum PIDs" (to something like 3) and uncheck "Allow all PIDs" in the tuner frontend options - you may need to change your view-level to expert to see them (in the tv adapters tab).

HTH

I've got no option "Allow all PIDs" (Tvh HTS Tvheadend 4.2.4-6). Is only "Maximum PIDs". Set to 3 doesn't change situation.

That's not very promising

The DVBSky T330 uses the silabs si216* chipset which I've actually used on a Pi 1 & it worked fine for DVB-T. Mainly because the max bit rate for T is a lot lower compared to C.

Only other thing I can suggest now is to change the power governor on the Pi to performance & see if that helps.

Well, power governon is interesing. After few tests looks good.

I'm using this script to change the raspberry pi governor and let this setting persist through restarts:
https://github.com/DavidM42/rpi-cpu.gov

After installing and command: sudo rpi.gov I choose options "performance - locks the CPU at maximum frequency" and so far I noticed just overall 13 data erros in about 1,5 hours of FHD recording material. I will experiment with other options in cpu.gov

In other side probably I will buy OrangePi strictly for Tvh and DVB-C tuner.

Jan Kowalski wrote:

Well, power governon is interesing. After few tests looks good.

I'm using this script to change the raspberry pi governor and let this setting persist through restarts:
https://github.com/DavidM42/rpi-cpu.gov

After installing and command: sudo rpi.gov I choose options "performance - locks the CPU at maximum frequency" and so far I noticed just overall 13 data erros in about 1,5 hours of FHD recording material. I will experiment with other options in cpu.gov

In other side probably I will buy OrangePi strictly for Tvh and DVB-C tuner.

Get one of the OPis with a H3, avoid the lite as it uses shared usb I believe. H2 CPUs tend to run a little hotter compared to H3 (I have an OPi PC H3 & a OPi zero H2+).

Look here to find the right board for you

Thanks. I think about OP PC Plus to replace RPi2. Before I though about OP zero just for Tvh but like you said, H2 can be to hotter for tuner. Do you think OP PC Plus is good choice to replace RPi2?

Jan Kowalski wrote:

Thanks. I think about OP PC Plus to replace RPi2. Before I though about OP zero just for Tvh but like you said, H2 can be to hotter for tuner. Do you think OP PC Plus is good choice to replace RPi2?

Pick one that has at least stable Armbian (mainline if no desktop, or legacy otherwise). Don't forget about the USB bus issues.

Avoid any that use the XR819 wireless chip, if you plan to use wifi! See here for a list of issues!

Well, after some research about OP, I will stay with RPi2.

I take risk and buy OP Zero strict for Tvh

Today I tested OrangePi Zero.

Probably this would be good solution but.... kernel is now just 4.13 and is unable to have DVB-C drivers with this kernel version. Minimum for this 4.4.1 kernel is required.

But is also good news. I installed OSMC on RPi - version OSMC from january 2017 and is working GREAT! Is much quicker than Raspbian with Kodi and better than OpenELEC because I can install all software I want through apt-get install.

But the most important is that quantity of continuity errors is VERY SMALL even if I watching 720p movie from internet via Kodi and have Tvh recording (full HD stream) at the same time! I noticed about 4 errors per 1 hour. This is very promising because I think about upgrade to RPi3.

Jan Kowalski wrote:

Today I tested OrangePi Zero.

Probably this would be good solution but.... kernel is now just 4.13 and is unable to have DVB-C drivers with this kernel version. Minimum for this 4.4.1 kernel is required.

4.13 is newer than 4.4.1. It should work out of the box on the Zero. You should NOT need to install/make any drivers, perhaps firmware, but nothing else.

Drivers are included in kernel 3.17 (for version 1) and 3.19 (for version 2). They can be built with media_build for older kernels.

What does dmesg say on the zero with the device plugged in (without any drivers installed)?

Well, if I put T330 to OrangePi Zero it looks promising. Stick is recognize (dmesg) and has firmware loaded. But.... DVB-C is not supported. TVHeadend show only DVB-T from this stick. I was trying compile drivers from dvbsky website: http://www.dvbsky.net/Support_linux.html but no succsess (errors after make command).

Strange.

Can you post the dmesg, lsmod and what kernel are you running?

Sure, so:
lsusb:

Bus 003 Device 002: ID 0572:0320 Conexant Systems (Rockwell), Inc. DVBSky T330 DVB-T2/C tuner

dmesg | grep dvb

root@orangepizero:~# dmesg | grep dvb
[   10.461217] usb 3-1: dvb_usb_v2: found a 'DVBSky T330' in warm state
[   10.503596] usb 3-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[   10.503678] dvbdev: DVB: registering new adapter (DVBSky T330)
[   10.505153] usb 3-1: dvb_usb_v2: MAC address: 00:cc:10:a5:33:0c
[   10.639306] Registered IR keymap rc-dvbsky
[   10.640015] usb 3-1: dvb_usb_v2: schedule remote query interval to 300 msecs
[   10.640034] usb 3-1: dvb_usb_v2: 'DVBSky T330' successfully initialized and connected
[   10.640173] usbcore: registered new interface driver dvb_usb_dvbsky

lsmod

root@orangepizero:~# lsmod
Module                  Size  Used by
zram                   20480  4
evdev                  20480  0
rc_dvbsky              16384  0
si2157                 16384  1
si2168                 16384  1
sun8i_codec_analog     24576  0
snd_soc_core          118784  1 sun8i_codec_analog
snd_pcm_dmaengine      16384  1 snd_soc_core
snd_pcm                69632  2 snd_pcm_dmaengine,snd_soc_core
snd_timer              24576  1 snd_pcm
dvb_usb_dvbsky         16384  0
snd                    45056  3 snd_timer,snd_soc_core,snd_pcm
soundcore              16384  1 snd
m88ds3103              20480  1 dvb_usb_dvbsky
xradio_wlan            94208  1
sun4i_gpadc_iio        16384  0
mac80211              446464  1 xradio_wlan
cfg80211              376832  2 mac80211,xradio_wlan
rfkill                 20480  3 cfg80211
uio_pdrv_genirq        16384  0
uio                    16384  1 uio_pdrv_genirq
usb_f_acm              16384  1
u_serial               20480  3 usb_f_acm
g_serial               16384  0
libcomposite           40960  2 g_serial,usb_f_acm
pwrseq_simple          16384  1

Now do sudo modinfo dvb_usb_dvbsky

root@orangepizero:~# sudo modinfo dvb_usb_dvbsky
filename:       /lib/modules/4.13.12-sunxi/kernel/drivers/media/usb/dvb-usb-v2/dvb-usb-dvbsky.ko
license:        GPL
description:    Driver for DVBSky USB
author:         Max nibble <[email protected]>
alias:          usb:v0CCDp0105d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0CCDp10A5d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0B48p3017d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0B48p3015d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0B48p3012d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0B48p3014d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0572p0320d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0572p680Cd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0572p960Cd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0572p6831d*dc*dsc*dp*ic*isc*ip*in*
depends:        m88ds3103
intree:         Y
name:           dvb_usb_dvbsky
vermagic:       4.13.12-sunxi SMP mod_unload ARMv7 thumb2 p2v8 
parm:           disable_rc:Disable inbuilt IR receiver. (int)
parm:           adapter_nr:DVB adapter numbers (array of short)

Little edit: After reboot (after first plug DVB Stick) dmesg looks that:

root@orangepizero:~# dmesg | grep dvb
[   10.489050] usb 3-1: dvb_usb_v2: found a 'DVBSky T330' in warm state
[   10.489756] usb 3-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[   10.489834] dvbdev: DVB: registering new adapter (DVBSky T330)
[   10.491239] usb 3-1: dvb_usb_v2: MAC address: 00:cc:10:a5:33:0c
[   10.649097] Registered IR keymap rc-dvbsky
[   10.649704] usb 3-1: dvb_usb_v2: schedule remote query interval to 300 msecs
[   10.649722] usb 3-1: dvb_usb_v2: 'DVBSky T330' successfully initialized and connected
[   10.649844] usbcore: registered new interface driver dvb_usb_dvbsky
[   14.234467] si2168 0-0064: Direct firmware load for dvb-demod-si2168-b40-01.fw failed with error -2
[   14.238739] si2168 0-0064: Direct firmware load for dvb-demod-si2168-02.fw failed with error -2
[   14.243320] si2168 0-0064: firmware file 'dvb-demod-si2168-02.fw' not found

If I install firmware from DVBSky website:

wget http://www.dvbsky.net/download/linux/dvbsky-firmware.tar.gz
tar -zxvf dvbsky-firmware.tar.gz
cd dvbsky-firmware
sudo ./copy-firmware.sh

After reboot dmesg looks:

root@orangepizero:~# dmesg | grep dvb
[   10.369196] usb 3-1: dvb_usb_v2: found a 'DVBSky T330' in warm state
[   10.370093] usb 3-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[   10.370184] dvbdev: DVB: registering new adapter (DVBSky T330)
[   10.371577] usb 3-1: dvb_usb_v2: MAC address: 00:cc:10:a5:33:0c
[   10.589278] Registered IR keymap rc-dvbsky
[   10.589884] usb 3-1: dvb_usb_v2: schedule remote query interval to 300 msecs
[   10.589912] usb 3-1: dvb_usb_v2: 'DVBSky T330' successfully initialized and connected
[   10.590068] usbcore: registered new interface driver dvb_usb_dvbsky
[   13.352236] si2168 0-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'

But DVB-C is still unrecognized in Tvh.