vdr January 2016

vdr@linuxtv.org

13 participants
9 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 github: https://github.com/chrodriguez/vdr/commit/dadbca57c2dc55c1c53b4fa8f68b56728… That's the only change I've made. Now I can enjoy my fresh upgraded VDR installation!! I think a better refactor should be made, but for now it's working perfectly deployed as a docker container: https://registry.hub.docker.com/u/chrodriguez/vdr Thanks for this wonderfull project! -- Lic. Christian A. Rodriguez @car_unlp

4 7

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-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?

4 8

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 ?) The second way seems to be more complicated to configure, and I'm not sure it suits my project, but the rpihddevice is well maintained though. The first solution is perhaps much straightforward and includes a media player (?) Could you tell me more please ? Damien

6 6

Re: [vdr] buffer overruns and sync probs after change of receivers
by Harald Milz 30 Jan '16

30 Jan '16

On Sat, Jan 30, 2016 at 12:35:49PM +0100, Thomas Netousek wrote: > Try disabling MSI interrupts in the ddbridge driver. Thank you for the hint... 17: 0 0 2317734 690 IO-APIC 17-fasteoi ddbridge but sadly: Jan 30 17:38:36 seneca vdr: [26112] buffer usage: 70% (tid=26111) Jan 30 17:38:36 seneca vdr: [26112] buffer usage: 80% (tid=26111) Jan 30 17:38:37 seneca vdr: [26112] buffer usage: 90% (tid=26111) Jan 30 17:38:37 seneca vdr: [26112] buffer usage: 100% (tid=26111) Jan 30 17:38:38 seneca vdr: [26111] ERROR: skipped 123 bytes to sync on TS packet on device 1 Jan 30 17:38:44 seneca vdr: [26112] ERROR: driver buffer overflow on device 1 Jan 30 17:38:46 seneca vdr: [26111] ERROR: skipped 123 bytes to sync on TS packet on device 1 Jan 30 17:38:46 seneca vdr: [26112] buffer usage: 60% (tid=26111) Jan 30 17:38:46 seneca vdr: [26112] i/o throttle released, count = 0 (tid=26112) tid=26111 is the vnsiserver. Am I out of options? -- Learn to pause -- or nothing worthwhile can catch up to you.

1 0

determine within plugin, whether radio or tv station
by Joerg Riechardt 30 Jan '16

30 Jan '16

Hi, what is a safe way to determine within a plugin, whether the stream it is receiving from VDR is a radio or a tv stream? There are tv streams with slowly changing still pictures, there are radio plugins which insert grafical information, so I am not sure if this could be achived by analysing the stream. Of cause there is the video pid. Is there a standard way to get that to the plugin? Do I think to complicated or am I missing something? The plugin needs to know within less than 100ms after start of stream. Joerg

3 5

How setup VDR to import external EPG data (XMLTV file)
by Chris R. 16 Jan '16

16 Jan '16

Hello i have got a rpi2 + dvb-t tuner that run under openelec 6 and VDR for the TV. This system work well and i would now import external EPG data... i read several thread about xmltv2vdr and it isn't so clear for me : - i was thinking of download xmltv file from internet (kazer.org for france) with a cron task - and use xmltv2vdr to import the downloaded file into VDR Is it possible to do like this ? Thanks

3 4

playing VDR-recordings on Samsung Smart TV with subtitles
by Peter Münster 15 Jan '16

15 Jan '16

Hi, Is is possible to play VDR-recordings on Samsung Smart TV with subtitles, and if yes, how please? It seems, that the Samsung Smart needs 2 files: an mp4 and an srt file. I've tried: "ffmpeg -i 00001.ts -vn -an -codec:s:0 srt 00001.srt" But no 00001.srt is created... TIA for any hints, -- Peter

2 2

[ANNOUNCE] vdrcm-0.0.2 - interactive console dialogs script for managing VDR configuration files
by Lucian Muresan 09 Jan '16

09 Jan '16

Hi all, vdrcm-0.0.2 - the VDR Config Manager for managing VDR configuration files is now available at [1]. What is this all about? You may remember the ARGSDIR feature introduced in VDR last year, which allows to store all the CLI parameters supplied to VDR and its plugins spread over several files with the extension *.conf in INI style, located for example in the /etc/vdr/conf.d directory. They only need to contain INI sections named like [vdr] or [plugin-name], followed by one option per line, then vdr launched with no CLI-parameters at all will read these files in their file name order. Just like other implementations (for example vdrctl used by yaVDR), vdrcm will actually symlink config files from a pool directory /etc/vdr/conf.avail to ARGSDIR, when it enables a plugin, or delete the symlink only, when disabling it. It also lets you define the explicit order of the plugins, by prefixing the symlinks with a number, or fires up the text editor defined in the EDITOR environment variable, and all this interactivlely in a CLI console, by using whiptail or dialog, see sreenshots at [2]. Note that the screenshots are from version 0.0.1, running with dialog, now I noticed that whiptail looks a lot better and is now preferred if both are present on the system. There is also a non-interactive pure CLI-mode supporting enabling or disabling a plugin by its name, and promoting the order of a plugin before another one, by the index before re-ordering. These CLI-options should be suitable for writing a true vdr Plugin for managing plugins, which should need to call these commands with setuid in order to be able to execute them, and scan the directories for refreshing the list of available/active/inactive plugins in the OSD. There were such type of plugins in the past, but they were too distribution-specific. The ARGSDIR-feature would allow any distribution to use this type of VDR/plugins configuration, therefore also the usage of the same management tools for them. I'm planning to write such a plugin in the near future, as spare time will permit it. The runtime dependencies of vdrcm are quite basic: - which - coreutils - util-linux - grep - pkg-config (optional, see README for a workaround when missing) - whiptail or dialog (optional if only the CLI-mode is used). For more information and a short visual usage summary, check the README.md at the homepage. Have fun, Lucian [1](Homepage) https://github.com/lucianm/vdrcm [2](Screenshots) https://github.com/lucianm/vdrcm/wiki/Short-visual-usage-summary [3](Releases) https://github.com/lucianm/vdrcm/releases

2 1

VDR + SatIP + Octopus Net - no more data on SD channels
by Patrick Boettcher 06 Jan '16

06 Jan '16

Hi list, I'm facing a problem with the following configuration: - VDR on a Raspi2 (raspian with packages from e-tobi) - Digital Devices' Octopus Net with 2 DVB-S2 receivers I'm using vdr-plugin-satip with the following arguments: -s <host>|DVBS2-2|Octo -d 2 Everything works fine. Except that after some time streaming on SD-channels seems to stop. Zapping to a HD-channels works. When trying to receive a non-working SD-stream I can see, via the satip-config-menu, that no PIDs seem to be delivered. Restarting the vdr-process (via the menu) works. While trying to understand the problem I have the feeling that zapping to non-existent services makes it appear faster. Not sure though. Is this a known issue? What can I do to better analyse the problem? Thanks in advance for any help. -- Patrick.

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr January 2016