Hello,
I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found.
But I try to watch some channel and I get no data. Tried with two clients Kodi software with its VDR plugin (screen interface) and with vdradmin-am (web interface).
What can I check to find the problem?
Notes: - TV dongle works; if I stop vdr service and use GUI applicacion Kaffeine, I can watch all TV channels. - I see VDR service attending TCP ports 34890 (VNSI), 6419 and 2010
Thank you.
_________ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 140 de nov. 28 15:57 . drwxr-xr-x 3 root root 60 de nov. 28 15:57 .. crw-rw----+ 1 root video 212, 4 de nov. 28 15:57 demux0 crw-rw----+ 1 root video 212, 5 de nov. 28 15:57 dvr0 crw-rw----+ 1 root video 212, 3 de nov. 28 15:57 frontend0 crw-rw----+ 1 root video 212, 19 de nov. 28 15:57 frontend1 crw-rw----+ 1 root video 212, 7 de nov. 28 15:57 net0
$ ps -A -o user,group,cmd | grep -ie vdr vdradmi+ vdradmi+ vdradmind pi pi grep --color=auto -ie vdr vdr vdr /usr/bin/vdr
$ groups vdr vdr : vdr video
I'm trying now with vdr-plugin-live : Same unsuccess result.
El 28/11/20 a les 17:44, Narcis Garcia ha escrit:
WHEN I JUST START SERVICE:
$ sudo systemctl status vdr ● vdr.service - Video Disk Recorder Loaded: loaded (/lib/systemd/system/vdr.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-11-28 17:31:10 CET; 13s ago Process: 30488 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh commands (code=exited, status=0/SUCCESS) Process: 30498 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh reccmds (code=exited, status=0/SUCCESS) Main PID: 30508 (vdr) Status: "Ready" Tasks: 9 (limit: 3748) CGroup: /system.slice/vdr.service └─30508 /usr/bin/vdr
de nov. 28 17:31:10 raspberrypi vdr[30508]: [30508] ERROR: no OSD provider available - using dummy OSD! de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] loading /var/cache/vdr/cam.data de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] switching to channel 1 T-0-17-155 (mega) de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] setting watchdog timer to 60 seconds de nov. 28 17:31:20 raspberrypi vdr[30508]: [32663] SVDRP server handler thread started (pid=30508, tid=32663, prio=low) de nov. 28 17:31:20 raspberrypi vdr[30508]: [32663] SVDRP raspberrypi opening port 6419/tcp de nov. 28 17:31:20 raspberrypi vdr[30508]: [32663] SVDRP raspberrypi listening on port 6419/tcp de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] OSD size changed to 720x480 @ 1 de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] ERROR: no OSD provider available - using dummy OSD! de nov. 28 17:31:21 raspberrypi vdr[30508]: [30508] max. latency time 1 seconds
AFTER A MINUTE OF RUNNING SERVICE (I was trying to switch TV channel from a client):
$ sudo systemctl status vdr ● vdr.service - Video Disk Recorder Loaded: loaded (/lib/systemd/system/vdr.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-11-28 17:31:10 CET; 2min 21s ago Process: 30488 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh commands (code=exited, status=0/SUCCESS) Process: 30498 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh reccmds (code=exited, status=0/SUCCESS) Main PID: 30508 (vdr) Status: "Ready" Tasks: 9 (limit: 3748) CGroup: /system.slice/vdr.service └─30508 /usr/bin/vdr
de nov. 28 17:33:12 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:13 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:16 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:18 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:21 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:21 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:24 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:25 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:28 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:28 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586
El 29/11/20 a les 9:42, Narcis Garcia ha escrit:
I've used "VDR Live" to restart service while tracking log with "journalctl -xef -u vdr"
*LOG:*
de nov. 29 11:29:47 raspberrypi systemd[1]: Starting Video Disk Recorder... -- Subject: A start job for unit vdr.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support
On Sat, 28 Nov 2020 17:44:32 +0100 Narcis Garcia debianlists@actiu.net wrote:
This is a multi-frontend device. You need VDR-2.4.1 or newer - or at least this patch from here: https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi...
Helmut
Helmut Binder kirjoitti 29.11.2020 klo 15.11:
You need to select correct frontend like this:
#!/bin/bash
var=$(dvb-fe-tool -a0 -f1 | grep 'Device' | awk '{print $3}')
echo 'A0 Second frontend is ' $var
if [ $var == 'MN88473' ]; then
echo 'A0 frontend is ' $var
mv /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/frontend2 mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0 mv /dev/dvb/adapter0/frontend2 /dev/dvb/adapter0/frontend1
fi
var=$(dvb-fe-tool -a0 -f0 | grep 'Device' | awk '{print $3}')
if [ $var == 'MN88473' ]; then
dvb-fe-tool -a0 -f0 -d DVBT2
dvb-fe-tool -a0 -f0 -g |grep DELIVERY
fi
************************ Second frontend with this adapter can handle DVBC/ANNEX_A too.
Vdr should know both frontends and use correct one and setup delivery system either by setup parameter or trying which one is working and prefer DVBT2. With satelite channnels it knows when to use S2. W_scan can handle this too.
Other version of this device can have CXD2837ER as second frontend name.
Timo
Timo Helkiö kirjoitti 29.11.2020 klo 16.09:
More info:
http://blog.palosaari.fi/2014/09/naked-hardware-18-astrometa-amdvb-t2-v2.htm...
Timo
The project sources repository (sadly in a proprietary platform):
https://github.com/stefantalpalaru/w_scan2
Narcis Garcia
El 30/11/20 a les 19:47, Richard F ha escrit:
A simplified alternative to w_scan2:
https://github.com/mighty-p/t2scan/
Narcis Garcia
El 1/12/20 a les 8:50, Narcis Garcia ha escrit:
El 29/11/20 a les 15:09, Timo Helkiö ha escrit:
Not matching cases: Once I've installed dvb-tools to have dvb-fe-tool program: $ sudo systemctl stop vdr $ dvb-fe-tool -a0 -f1 | grep 'Device' | awk '{print $3}' CXD2837ER $ dvb-fe-tool -a0 -f0 | grep 'Device' | awk '{print $3}' RTL2832 $ sudo systemctl start vdr
This is the assembled device: https://osmc.tv/store/product/tv-dongle/
El 29/11/20 a les 15:09, Timo Helkiö ha escrit:
I've done this like a backport from next Raspbian version:
$ sudo apt -t bullseye install vdr
/[installing new] gcc-10-base libcbor0 libcrypt-dev libcrypt1 libffi7 libfido2-1 libgcc-s1 libnsl-dev libnsl2 libnss-nis libnss-nisplus libreadline8 libtirpc-dev runit-helper/
/[upgrading] libc-bin libc-dev-bin libc-l10n libc6 libc6-dbg libc6-dev libpython3.7 libpython3.7-dev libpython3.7-minimal libpython3.7-stdlib libselinux1 libstdc++6 libtirpc-common libtirpc3 locales manpages manpages-dev openssh-client openssh-server openssh-sftp-server python3.7 python3.7-dev python3.7-minimal python3.7-venv vdr vdr-plugin-femon vdr-plugin-live vdr-plugin-osdserver vdr-plugin-vnsiserver/
(...) Bai:43 http://ftp.cica.es/mirrors/Linux/raspbian/raspbian bullseye/main armhf vdr armhf 2.4.1-4.1 [1043 kB] S'està preparant per a desempaquetar …/vdr_2.4.1-4.1_armhf.deb… S'està desempaquetant vdr (2.4.1-4.1) sobre (2.4.0-1+b1)… (...)
$ sudo systemctl stop vdr
$ sudo systemctl start vdr
$ sudo journalctl -xef -u vdr
de nov. 29 17:41:31 raspberrypi systemd[1]: Starting Video Disk Recorder... -- Subject: A start job for unit vdr.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support
On Sun, 29 Nov 2020 17:53:27 +0100 Narcis Garcia debianlists@actiu.net wrote:
Can you receive any DVB-T2 Channels ? These would use frontend 0/1 with the CXD2837ER demodulator and you could compare the tuning. If not, rename frontend1 to frontend0, similar as in Timo's proposal:
- stop vdr
mv /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/Xfrontend0" mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0"
- start vdr
Helmut
El 29/11/20 a les 22:13, Helmut Binder ha escrit:
Tried this workaround several times, and last one resulted but in this order:
1. Tuned channels with devices/frontends "as is" 2. moved frontend1 to frontend0
I'm pending to do more testing and be sure this is the point for my case.
__________ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 29/11/20 a les 14:11, Helmut Binder ha escrit:
I've just tried same device with Ubuntu 20.10 (it has VDR 2.4.1 on repositories) This is not fixed in this version. I had to do the frontend0 <-> frontend1 workaround to have it working (channels scan must be done without frontends swap). And no EPG. Same results as with Raspbian 10
-
Helmut Binder -
Klaus Schmidinger -
Narcis Garcia -
Richard F -
Timo Helkiö