vdr February 2016

vdr@linuxtv.org

18 participants
10 discussions

VDR ISDB-T support
by Christian Rodriguez 14 Sep '18

14 Sep '18

Hello everyone! I'm from Argentina, and up to last month I've been using VDR 1.7.262 with an ISDB-T USB adapter. It works really good, but the last week I've been trying to upgrade to VDR 2.2 and I've found a problem with ISDB-T cards: they are not supported. As I'm really interested in using VDR, I was digging inside the code and found a partial solution for this problem: as ISDBT is the same as DVBT, I've changed the way delivery system is queried. My changes are applied in a cloned repo at … [View More]

4 7

Media (.mkv) player on Raspberry Pi2 VDR client
by Nicolas Huillard 12 Mar '16

12 Mar '16

Hi all, My new Raspberry Pi2 install lacks a media player, which begins to be a bit annoying. The current setup : * NFS server * DigitalDevices Octopus Net DVB network server * VDR + rpihddevice + satip on the Pi2 : live TV, timers, recordings, etc. * an old VDR instance on the NFS server plays MKV media (using xinelibouput), but lacks satip (no timers, no live TV anymore) I will upgrade the old VDR to act as a headless epg/timer/recording server. I will thus be unable to play the MKV media … [View More]

6 21

priority -1 too low to trigger deleting an old recording
by Peter Münster 24 Feb '16

24 Feb '16

Hi, On my system, disk usage is always about 99%, because VDR cares about deleting old recordings, when needed. But when editing a recording, the automatic deletion fails: --8<---------------cut here---------------start------------->8--- 17:36:28 vdr[28116]: [28116] info: Editing process started 17:36:50 vdr[28116]: [28834] low disk space while recording, trying to remove a deleted recording... 17:36:50 vdr[28116]: [28834] ...no deleted recording found, priority -1 too low to trigger … [View More]

2 2

buffer overruns and sync probs after change of receivers
by Harald Milz 18 Feb '16

18 Feb '16

Hi all, I recently changed the receivers of my VDR from two TeVii S660's to a Digital Devices Cine S2 + Duoflex card. Everything else remained unchanged on the VDR side of things. Since then, I encounter frequent (as in, once per day approx.) buffer overruns and resync probs. As it seems from the thread IDs, the TS or VNSI buffer threads seem to cause the problem. But I may be wrong. Software versions: - Ubuntu 14.04.3 LTS with Wily kernel (4.2.0-latest) - vdr-2.0.3 (ubuntu) - vnsiserver-… [View More]latest from git (from a couple of days ago) - Kodi 6.0 as in Openelec-current on RPi2 - dddvb driver 0.9.21 or 0.9.22 from Digital Devices git (current). As shown by the kernel log, the DD card is initialized just fine: [ 14.704506] dvb_core: module verification failed: signature and/or required key missing - tainting kernel [ 14.744728] Digital Devices PCIE bridge driver 0.9.21, Copyright (C) 2010-15 Digital Devices GmbH [ 14.744921] DDBridge driver detected: Digital Devices Cine S2 V6.5 DVB adapter [ 14.744938] DDBridge: HW 0001000d REGMAP 00010004 [ 14.744972] DDBridge: using 1 MSI interrupt(s) [ 14.746272] Port 0: Link 0, Link Port 0 (TAB 1): DUAL DVB-S2 [ 14.858090] Port 1: Link 0, Link Port 1 (TAB 2): DUAL DVB-S2 [ 14.859048] Port 2: Link 0, Link Port 2 (TAB 3): NO MODULE [ 14.860003] Port 3: Link 0, Link Port 3 (TAB 4): NO MODULE [ 14.861739] 0 netstream channels [ 14.861742] DVB: registering new adapter (DDBridge) [ 14.861744] DVB: registering new adapter (DDBridge) [ 14.861745] DVB: registering new adapter (DDBridge) [ 14.861746] DVB: registering new adapter (DDBridge) ... [ 15.407636] LNBx2x attached on addr=a [ 15.436794] stv6110x_attach: Attaching STV6110x [ 15.436799] attach tuner input 0 adr 60 [ 15.436871] ddbridge 0000:05:00.0: DVB: registering adapter 0 frontend 0 (STV090x Multistandard)... ... [ 15.472168] LNBx2x attached on addr=8 [ 15.472174] stv6110x_attach: Attaching STV6110x [ 15.472176] attach tuner input 1 adr 63 [ 15.472256] ddbridge 0000:05:00.0: DVB: registering adapter 1 frontend 0 (STV090x Multistandard)... ... [ 15.491106] LNB25 on 0c [ 15.640527] ddbridge 0000:05:00.0: DVB: registering adapter 2 frontend 0 (STV0910)... [ 15.642001] LNB25 on 0d [ 15.645682] ddbridge 0000:05:00.0: DVB: registering adapter 3 frontend 0 (STV0910)... When running, after a while these error messages can be seen: Jan 23 11:15:46 seneca vdr: [7888] VNSI: Successfully switched to channel 14 - KiKA HD Jan 23 11:15:46 seneca vdr: [7888] VNSI: Started streaming of channel KiKA HD (timeout 10 seconds) Jan 23 11:15:46 seneca vdr: [7891] cLiveStreamer stream processor thread started (pid=2593, tid=7891, prio=high) Jan 23 11:15:46 seneca vdr: [7892] TS buffer on device 2 thread started (pid=2593, tid=7892, prio=high) Jan 23 11:15:46 seneca vdr: [7890] VNSI: VideoInput: no pat/pmt within timeout, falling back to channel pids Jan 23 11:15:46 seneca vdr: [7890] VNSI: Video Input - new pmt, attaching receiver Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6610 and type=8 Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6622 and type=1 Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6620 and type=2 Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6621 and type=2 Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6631 and type=9 Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6630 and type=11 Jan 23 11:15:49 seneca vdr: [7892] i/o throttle activated, count = 1 (tid=7892) Jan 23 11:15:50 seneca vdr: [7892] buffer usage: 70% (tid=7889) Jan 23 11:15:50 seneca vdr: [7892] buffer usage: 80% (tid=7889) Jan 23 11:15:50 seneca vdr: [7892] buffer usage: 60% (tid=7889) Jan 23 11:15:50 seneca vdr: [2746] VNSI: Timers state changed (13) Jan 23 11:15:50 seneca vdr: [2746] VNSI: Requesting clients to reload timers Jan 23 11:15:52 seneca vdr: [7892] buffer usage: 70% (tid=7889) Jan 23 11:15:52 seneca vdr: [7892] buffer usage: 80% (tid=7889) Jan 23 11:15:52 seneca vdr: [7892] buffer usage: 90% (tid=7889) Jan 23 11:15:53 seneca vdr: [7892] buffer usage: 100% (tid=7889) Jan 23 11:15:54 seneca vdr: [2746] VNSI: Timers state changed (14) Jan 23 11:15:54 seneca vdr: [2746] VNSI: Requesting clients to reload timers Jan 23 11:15:54 seneca vdr: [7892] ERROR: driver buffer overflow on device 2 Jan 23 11:15:58 seneca vdr: message repeated 2 times: [ [7892] ERROR: driver buffer overflow on device 2] Jan 23 11:16:00 seneca vdr: [7889] ERROR: skipped 123 bytes to sync on TS packet on device 2 Jan 23 11:16:03 seneca vdr: [7892] ERROR: driver buffer overflow on device 2 Jan 23 11:16:04 seneca vdr: [7892] buffer usage: 60% (tid=7889) Jan 23 11:16:04 seneca vdr: [7889] ERROR: skipped 123 bytes to sync on TS packet on device 2 Jan 23 11:16:04 seneca vdr: [7892] i/o throttle released, count = 0 (tid=7892) Jan 23 11:16:05 seneca vdr: [7892] i/o throttle activated, count = 1 (tid=7892) Jan 23 11:16:06 seneca vdr: [7892] buffer usage: 70% (tid=7889) Jan 23 11:16:06 seneca vdr: [7892] buffer usage: 60% (tid=7889) Jan 23 11:16:06 seneca vdr: [7892] buffer usage: 70% (tid=7889) Jan 23 11:16:06 seneca vdr: [7892] buffer usage: 60% (tid=7889) Jan 23 11:16:06 seneca vdr: [7892] buffer usage: 70% (tid=7889) Jan 23 11:16:06 seneca vdr: [7892] buffer usage: 60% (tid=7889) Jan 23 11:16:06 seneca vdr: [7892] buffer usage: 70% (tid=7889) Jan 23 11:16:06 seneca vdr: [7892] buffer usage: 60% (tid=7889) Jan 23 11:16:06 seneca vdr: [7892] buffer usage: 70% (tid=7889) Jan 23 11:16:06 seneca vdr: [7892] buffer usage: 60% (tid=7889) Jan 23 11:16:07 seneca vdr: [7892] buffer usage: 70% (tid=7889) Jan 23 11:16:07 seneca vdr: [7892] buffer usage: 80% (tid=7889) Jan 23 11:16:08 seneca vdr: [7892] buffer usage: 60% (tid=7889) Jan 23 11:16:08 seneca vdr: [7892] buffer usage: 70% (tid=7889) Jan 23 11:16:08 seneca vdr: [7892] buffer usage: 60% (tid=7889) Jan 23 11:16:09 seneca vdr: [7892] buffer usage: 70% (tid=7889) and voilà, decoding errors, blocks, resyncs. The fun part is, it is not enough to restart VDR (and hence, vnsiserver) or unload and reload the kernel modules, but I actually need to restart the _machine_ in order to get away with this. Both device 1 and device 2 are attached to Astra, these are two independent LNBs with no multiswitch or anything inbetween. It makes no difference if the current channel is on 1 or 2, so it should not be the LNBs (how?) or the receiver modules on the DD card. This does not happen when watching live streams with xineliboutput / vdr-sxfe, and also not if I watch recordings using vnsiserver / kodi. Only when it's live streams and vnsiserver / kodi. Happens with HD or SD channels. Does not go away when switching channels. Recording works just fine without any problems. I opened a ticket with Digital Devices but for now I haven't got a clue from them, and also no answer in the VNSI / Kodi forum, so I hope that somebody here might have a clue where to look. And sorry for using an old VDR version but this is where I am. Going to upgrade to 2.2.0 with Ubuntu 16.04 as soon as it's available. This is a "production" (as in "high WAF required") machine. ;-) TIA! -- FORTUNE PROVIDES QUESTIONS FOR THE GREAT ANSWERS: #13 A: Doc, Happy, Bashful, Dopey, Sneezy, Sleepy, & Grumpy Q: Who were the Democratic presidential candidates? [View Less]

4 8

VDR deleting non-.del-dirs in video-path
by Patrick Boettcher 17 Feb '16

17 Feb '16

Hi list, I'm using a Raspi2 for vdr and attached a HDD over USB for storage. I'm also backuping the rootfs (SD-card) onto the HDD on a regular basis. Checking the logs for another problem it turns out the it enters my backup-dir and tries to delete empty-directories. I read in the ML-archive that this is normal behavior. Is there anything I can do to prevent this? Telling vdr to ignore it. best regards, -- Patrick.

2 2

Fwd: Fwd: Re: vdr 2.1.2 segfaults in libc using vdr --genindex
by g.bruno 14 Feb '16

14 Feb '16

Hello, I am sorry to have sent you this mail today at 16:47:58 +0100 with wrong informations because did not work in the right directory. Please ignore it. Greetings G. Bruno -------- Weitergeleitete Nachricht -------- Betreff: Re: [vdr] vdr 2.1.2 segfaults in libc using vdr --genindex Datum: Sun, 14 Feb 2016 16:47:58 +0100 Von: g.bruno <g.bruno(a)t-online.de> Antwort an: VDR Mailing List <vdr(a)linuxtv.org> An: VDR Mailing List <vdr(a)linuxtv.org> I tried the attached … [View More]patches. Most of them ended with errors, see below. ----------------------------------------------------- root@amd8:/usr/local/src/vdr-2.2.0/PLUGINS/src/xineliboutput# patch -N ./Makefile debian.patch patching file ./Makefile Hunk #1 FAILED at 343. 1 out of 1 hunk FAILED -- saving rejects to file ./Makefile.rej root@amd8:/usr/local/src/vdr-2.2.0/PLUGINS/src/xineliboutput# root@amd8:/usr/local/src/vdr-2.2.0/PLUGINS/src/xineliboutput# ls -l xine_frontend.c -rw-r--r-- 1 vdr users 59823 Aug 20 2013 xine_frontend.c --------------------------------------------------- root@amd8:/usr/local/src/vdr-2.2.0/PLUGINS/src/xineliboutput# patch -N ./xine_frontend.c ./xineliboutput-dfatmo-switch patching file ./xine_frontend.c Hunk #1 succeeded at 1439 (offset 2 lines). patching file ./xine_frontend.c Hunk #1 FAILED at 455. 1 out of 1 hunk FAILED -- saving rejects to file ./xine_frontend.c.rej patching file ./xine_frontend.c Hunk #1 succeeded at 401 with fuzz 2 (offset 178 lines). Hunk #2 succeeded at 1107 with fuzz 2 (offset 807 lines). patching file ./xine_frontend.c Hunk #1 FAILED at 218. 1 out of 1 hunk FAILED -- saving rejects to file ./xine_frontend.c.rej --------------------------------------------- root@amd8:/usr/local/src/vdr-2.2.0/PLUGINS/src/xineliboutput# patch ./config.c ./truecolor.diff patching file ./config.c Hunk #1 succeeded at 737 (offset -4 lines). Hunk #2 succeeded at 760 (offset -4 lines). Hunk #3 succeeded at 778 (offset -4 lines). Hunk #4 succeeded at 898 (offset -4 lines). patching file ./config.c Hunk #1 FAILED at 294. 1 out of 1 hunk FAILED -- saving rejects to file ./config.c.rej patching file ./config.c Hunk #1 FAILED at 783. 1 out of 1 hunk FAILED -- saving rejects to file ./config.c.rej patching file ./config.c Hunk #1 FAILED at 160. 1 out of 1 hunk FAILED -- saving rejects to file ./config.c.rej ------------------------------------ root@amd8:/usr/local/src/vdr-2.2.0/PLUGINS/src/xineliboutput/xine# patch ./xvdr_metronom.c ./fix-segfault.patch patching file ./xvdr_metronom.c ----------------------------------- xine_frontend_cec.c does not exist (twice), at least I could not find it ------------------------------ compiling with make failed: root@amd8:/usr/local/src/vdr-2.2.0/PLUGINS/src/xineliboutput# make Makefile:109: Building inside VDR source tree g++ -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DXINELIBOUTPUT_VERSION='"1.1.0"' -Wall -I../../../include -o xineliboutput.o xineliboutput.c xineliboutput.c: In member function ‘virtual bool cPluginXinelibOutput::Service(const char*, void*)’: xineliboutput.c:295:22: error: ‘str’ was not declared in this scope if (!strncasecmp(str, "DFATMOENABLED", 13)) { ^ xineliboutput.c:296:7: error: ‘fe’ was not declared in this scope fe->send_event(fe, str); ^ xineliboutput.c:297:7: error: continue statement not within a loop continue; ^ xineliboutput.c:299:22: error: ‘str’ was not declared in this scope if (!strncasecmp(str, "DFATMOENABLED", 13)) { ^ xineliboutput.c:300:7: error: ‘fe’ was not declared in this scope fe->send_event(fe, str); ^ xineliboutput.c:301:7: error: continue statement not within a loop continue; ^ make: *** [xineliboutput.o] Fehler 1 ---------------------------------------------- Did I make any mistakes? The version of the plugin is xineliboutput-1.1.0. Are the patches for an other version of VDR? What do I do now? Any ideas? G.Bruno Am 14.02.2016 um 12:56 schrieb Lars Hanisch: > Hi, > > Am 14.02.2016 um 11:18 schrieb g.bruno: >> Hallo Klaus, >> >> I already tried VDR version 2.2.0, but it does not run, because the VDR-plugin-xineliboutput is missing for this >> Version. The Version I used with VDR 2.1.2 does not compile. > > Have you tried the latest commits from: > git clone git://projects.vdr-developer.org/xineliboutput.git > > It's better to fix xineliboutput as to work with old vdr versions. :) > If you have problems with compiling xineliboutput, please ask. > > At yavdr we use some patches to compile it with recent libcec versions. They are attached, look at the series files for > the order of the patches. > > Lars. > > > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > _______________________________________________ vdr mailing list vdr(a)linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr [View Less]

1 0

vdr 2.1.2 segfaults in libc using vdr --genindex
by g.bruno 14 Feb '16

14 Feb '16

Dear Sirs, the patch to the subject above, published on http://www.linuxtv.org/pipermail/vdr/2013-December/028137.html has several mistakes and is incomplete. Here the results from the "patch" command): root@amd8:/usr/local/src/vdr-2.1.2# patch -b --verbose ./vdr.c < vdr_c.patch Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- vdr.c 2013/12/25 11:01:28 3.6 |+++ vdr.c 2013/12/25 11:24:26 -------------------------- … [View More]

4 8

HEVC Support
by Jürgen Schneider 05 Feb '16

05 Feb '16

Hi, what is about HEVC support, it will come soon with DVB-T2 in german metropolitan areas. Regards, J. Schneider

2 1

Re: [vdr] NTSC closed captions
by Newsy Paper 01 Feb '16

01 Feb '16

Hi Klaus! Hi Alex! Actually I know one channel receivable in Europe that uses CC directly included into the V-PID. VLC can decode those CC subtitles. It's MSNBC on Telstar 12 15°West 12509 V 3198 7/8 kind regards Newsy -------------------------------------------- Klaus Schmidinger <Klaus.Schmidinger(a)tvdr.de> schrieb am So, 14.6.2015: Betreff: Re: [vdr] NTSC closed captions An: vdr(a)linuxtv.org Datum: Sonntag, 14. Juni, 2015 09:05 Uhr On 14.06.2015 03:20, Alex wrote: > … [View More]

1 0

Using a rasberry pi as vdr client
by Damien Bally 01 Feb '16

01 Feb '16

Hi I want to use raspberry pi as if it were a graphic card : I mean the dvb devices on a PC style server, IR receiver preferably on the server too (rpi and server in the same room) I don't know how to configure it, there is apparently 2 ways of doing it (from what I understood) + xineliboutput with vdr-fbfe (rpi plugin is closed source ? the one here : http://www.vdr-portal.de/board18-vdr-hardware/board98-arm-co/118588-rasperr…) + streamdev and rpihddevice (which additional plugins ?) … [View More]

6 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr February 2016