vdr November 2020

vdr@linuxtv.org

9 participants
8 discussions

Trouble with DVB-T2 on frontend 1
by Marko Mäkelä 03 Jan '22

03 Jan '22

Hi all, I recently got a USB adapter "Astrometa DVB-T2" that I would like to use with VDR. It comprises two frontends: /dev/dvb/adapter0/frontend0: Realtek RTL2832 (DVB-T) /dev/dvb/adapter0/frontend1: Panasonic MN88473 (DVB-T2 and DVB-C) I guess it is similar to this one; just a slightly different plastic case with some more ventilation holes: http://blog.palosaari.fi/2014/09/naked-hardware-18-astrometa-amdvb-t2-v2.ht… The hardware appears to work fine, once I copied the /lib/firmware/dvb-demod-mn88473-01.fw from somewhere. The firmware upload has failed at least once on the Raspberry Pi 2 (using Linux 4.9.59), but never on another machine that runs a 4.13.0 kernel. I did not yet get the infrared remote control to produce anything in evtest. With dvbv5-zap (after running dvbv5-scan), I can tune into DVB-T2 channels like this: dvbv5-zap -a 0 -f 1 -c dvb_channel.conf 'Yle TV1 HD' -r After this, I can play the video and audio stream on the Raspberry Pi 2: omxplayer /dev/dvb/adapter0/dvr0 Unless I explicitly specify the options -a 0 -f 1, then dvbv5-zap will fail to find any DVB-T2 senders, because it apparently defaults to frontend0, which is DVB-T only. In VDR 2.3.8, I have only been able to view DVB-T from the first frontend. When I did a trick and renamed /dev/dvb/adapter0/frontend1 to frontend0 before starting VDR, VDR no longer complained that the DVB-T2 channels (which I converted from the dvb_channel.conf to channels.conf with dvb-format-convert) not being available, but it did not seem to receive anything from these channels either. Also, after using dvbv5-scan or dvbv5-zap, I sometimes have to invoke w_scan to "reset" the hardware so that VDR can receive DVB-T channels. I would like to receive and record DVB-T and DVB-T2 on this setup. I am willing to try patches or do some programming myself, but I would appreciate some hints to get started. Marko

2 7

vdr not working in Raspbian 10
by Narcis Garcia 04 Jan '21

04 Jan '21

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. -- Narcis Garcia __________ 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.

5 21

Re: [vdr] vdr not working in Raspbian 10
by Narcis Garcia 29 Nov '20

29 Nov '20

El 29/11/20 a les 14:16, André Weidemann ha escrit: > > > On 29.11.2020 11:33, Narcis Garcia wrote: >> de nov. 29 11:29:53 raspberrypi vdr[11391]: [11391] ERROR >> (dvbdevice.c,1650): /dev/dvb/adapter0/frontend1: El dispositiu o recurs >> es troba ocupat > > Looks like the dvb-adapter is already in use. > You can try to figure which process is holding on to it by running: > > sudo lsof |grep /dev/dvb/adap|awk '{print $2}'|uniq|xargs ps -fp > > André $ sudo lsof |grep /dev/dvb/adap|awk '{print $2}'|uniq|xargs ps -fp lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. UID PID PPID C STIME TTY TIME CMD vdr 11391 1 0 11:29 ? 00:01:10 /usr/bin/vdr *Narcís*

1 0

VDR do not show HD channels.
by prelude 22 Nov '20

22 Nov '20

Hello and thx for this great VDR software. Could someone help me at the start as I cannot get dvb-t2 channels visible in VDR? If I add HD channels manually in channels.conf then VDR mark those as OBSOLETE. Yesterday I even clean my channels.conf totally and just left one channel on it and put in setup "add new transponders". In the morning all DVB-T channels were in channels.conf file but not any DVB-T2. tvheadend works fine also in HD channels but i just like so much more VDR user experience that i don't want to change it.

3 6

Subtitle
by Alexander 20 Nov '20

20 Nov '20

Hi, my wife is hard of hearing and that is why we have permanently discontinued the subtitle in the vdr. But if she don't watch, I'll turn off the subtitle with the hotkey. When I switch channels, the subtitle is on again. Is there a possibility that the subtitles will not appear until the next restart of vdr? -- Greets Walter

3 2

option parsing for --log still broken
by Harald Milz 18 Nov '20

18 Nov '20

Hi Klaus and all, it appears that option parsing for the --log option is still broken, as described in this thread: https://www.vdr-portal.de/forum/index.php?thread/108924-gel%C3%B6st-logging… Short version: vdr stops parsing the remainder of the command line at the point of --log=2.6. Long version: The problem is in the getopt code in vdr.c: case 'l': { char *p = strchr(optarg, '.'); if (p) *p = 0; if (isnumber(optarg)) { int l = atoi(optarg); if (0 <= l && l <= 3) { SysLogLevel = l; if (!p) break; if (isnumber(p + 1)) { int l = atoi(p + 1); if (0 <= l && l <= 7) { int targets[] = { LOG_LOCAL0, LOG_LOCAL1, LOG_LOCAL2, LOG_LOCAL3, LOG_LOCAL4, LOG_LOCAL5, LOG_LOCAL6, LOG_LOCAL7 }; SysLogTarget = targets[l]; break; } } } } if (p) *p = '.'; fprintf(stderr, "vdr: invalid log level: %s\n", optarg); return 2; } Initially, the point is replaced by a NULL byte in order to be able to atoi() both numbers (if (p) *p = 0;). This replacing takes place _in place_. In theory, the replace should be reverted at the end of the code snippet (if (p) *p = '.';) BUT if one of the branches involving a break is executed, the revert is never invoked, and the original command line remains broken so that the remaining command line options are not getting evaluated. Consequently, what used to be vdr -w 60 -g -u vdr -l 2.6 -P plugin1 -P plugin2 becomes vdr -w 60 -g -u vdr -l 2 6 -P plugin1 -P plugin2 and the modules will not get loaded. The thread mentioned above speaks of upstart & co but I have the same issue in a docker container with explicit program start in a shell script whithout any upstart or anything. I now helped myself putting the -l at the end of the command line but I still cannot send the vdr log to a different facility because the dangling 6 is not getting evaluated. My suggestion would be to not evaluate the optarg string directly but create a copy of optarg first, and work with the copy. This way, the original command line is unchanged. Sample patch attached, untested but it should do the trick. -- You are as I am with You.

2 2

Re: [vdr] Many "Tuning timeout" messages and signal disruptions
by Richard F 17 Nov '20

17 Nov '20

I'd either use bare metal or maybe a container (LXC, not sure sure about docker) as that's as near as bare metal with few encumbrances. Why ? I've always used bare metal, and it seems VDR is working quite close to the hardware, adding layers adds complexity. But the other thing is that that sever looks quite ancient now and a replacement (somewhat newer, if not new) shouldn't cost much. I had a similar issue with a CCTV card unrecognised by the kernel and gave up fighting the FOXCONN mobo/BIOS, after some discussion and help on the kernel developers forum who tried but ultimately couldn't help in the end, and bought an-off-the shelf HP machine for only around 100 euro / used. There were other benefits, like super-efficient PSU giving power eduction which in the 4 or 5 years since may have paid for it ! The ugly bit is ideally you need a kind soul to let you test your card in whatever machine first, to be sure it works. On 13/11/2020 12:00 pm, vdr-request(a)linuxtv.org wrote: > potential solutions: > - run VDR in a docker container instead of in a VM and pass /dev/dvb to the > container > - replace the KVM host, thus get rid of the RMRR issue and continue to use PCI > passthrough > - run the VDR on bare metal > - others? > > What would you do if you were in my place, and why?

1 0

Many "Tuning timeout" messages and signal disruptions with minisatip and the satip plugin
by Harald Milz 12 Nov '20

12 Nov '20

Hi guys, I migrated my VDR and my KVM host to Ubuntu 20.04-latest lately. The KVM host has the sat card (Digital Devices Cine S2 V6.5 DVB adapter), the driver stack (0.9.33-integrated), plus minisatip-latest from git, and the vdr VM runs the normal Ubuntu stack with vdr-2.4.1 and satip-2.4.0 (plus xineliboutput and vnsiserver). I use two satellites, Astra 19.2E and Hotbird S13E, with 2 receivers each. The stack basically works, but after some time the messages "SATIP-ERROR: Tuning timeout" get more and more and the usual artifacts occur. The WAF factor is not that high as you can tell. Since everything else works nicely, I suspect a problem somewhere between the ddbridge driver, minisatip and the satip plugin. Question: is that the expected behaviour for such a setup? In the old days I used PCI passthrough but this is very inconvenient because the server (HP DL380G6) has a RMRR problem with the sat card, and I had to use custom built kernels all the time... potential solutions: - run VDR in a docker container instead of in a VM and pass /dev/dvb to the container - replace the KVM host, thus get rid of the RMRR issue and continue to use PCI passthrough - run the VDR on bare metal - others? What would you do if you were in my place, and why? TIA! -- Q: Why should you always serve a Southern Carolina football man soup in a plate? A: 'Cause if you give him a bowl, he'll throw it away.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr November 2020