vdr March 2015

vdr@linuxtv.org

15 participants
10 discussions

xmltv2vdr.pl
by Dominic Evans 14 Aug '15

14 Aug '15

I don't know if anyone else still uses the xmltv2vdr.pl perl script for piping XMLTV data into VDR's epg, but I've been keeping a version of it updated with some additional function here: https://github.com/oldmanuk/xmltv2vdr These are the changes since the last version (1.0.9) was released on the mailing list - Add support for XMLTV episode-num. Currently gets added as EPG entry 'sub-title', if no existing subtitle has been found, in the form sXXeXX (e.g., Bones~s01e01). - Change default SVDRP port number to 6419. - Better support for ATSC/PVRINPUT EPG sources. - Allow multiple channels to have the same XMLTV channel id, useful for multi input (e.g., DVB-T, DVB-S) systems where you want to feed VDR the same info. Previously only a 1:1 mapping was permitted. I've also received a pull request from someone who rewrote the whole script to be a lot more readable and to use full XML parsing (rather than just line-by-line scraping), but I still need to investigate what the performance penalty is before accepting that in.

6 10

VDR & Multiple frontends
by Eddi 25 Jul '15

25 Jul '15

Hi, I wrote a patch to Steve Toth hvr3000 repository, so my FlyDVB Trio can use multiple frontend. So I get: /dev/dvb/adapter0/demux0 /dev/dvb/adapter0/demux1 /dev/dvb/adapter0/dvr0 /dev/dvb/adapter0/dvr1 /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/net0 /dev/dvb/adapter0/net1 The bus of the two frontend is shared, isn't possible to get access to both frontend simultaneously, so I get an -EBUSY error by trying accessing frontend1 if frontend0 is in use. VDR doesn't support yet the second frontend, and it try to get exclusive access on both frontend on start, so the second frontend is inusabile. Vdr should probe for multiple frontend at start, and access frontend only on channel change. Please can someone give me an help to wrote a patch for this issue? Best Regards, Eddi

4 21

vdr + rpihddevice + skinnopacity
by Jouni Karvo 02 Apr '15

02 Apr '15

hi, I have the following problem: when pressing "menu" with my Raspberry pi Lirc, VDR crashes: Mar 31 13:51:09 vdrfe vdr: [2456] rpihddevice: [OpenVG] cannot allocate pixmap of 2804px x 781px, clipped to 2048px x 781px! Mar 31 13:51:09 vdrfe vdr: [2469] rpihddevice: [EGL] failed to create pixel buffer surface: bad alloc! Mar 31 13:51:09 vdrfe vdr: [2456] rpihddevice: [OpenVG] failed to create pixmap! (allocation failed) setup: - vdr 2.2.0 - raspberry pi current git - skinnopacity 1.1.3 + the second version of skinnopacity remotetimers patch - remotetimers v 1.0.1 I have set gpu_mem to 256M With rpihddevice from git Mar 8th, no crashes, but I could not use accelerated OSD (the subtitles did not work). I pulled the repository again about a week ago, and got accelerated osd working. Yesterday the problem I described started, and I re-pulled the git, because it seemed there was a fix. Not working. When not using accelerated OSD, it works fine, but rendering subtitles takes so long that there is hardly time to read them. Any suggestions? Should I insert more debug info? (what and how?) yours, Jouni

2 2

raspbian apt repo with up to date vdr packages?
by Torgeir Veimo 27 Mar '15

27 Mar '15

I've been testing out VDR on a raspberry pi 2 with excellent result using rpihddevice and am wondering if anyone know of any good APT repository with up to date packages for VDR and plugins? Am currently using raspbian which has VDR 1.7.28, so it's a bit behind. -- -Tor

4 3

select() problem seen with vdr-plugin-streamdev 0.6.1
by Hans Petter Selasky 26 Mar '15

26 Mar '15

Hi, I'm seeing this strange problem that a select statement in the streamdev server is returning EBADF and then the streamdev server exits and refuse to accept more connections. This typically happens when trying to stream a specific channel. Trying to stream other channels does not exhibit this problem. I can recompile code and try patches. I've made simple and crude patch to make the streamdev server plugin a bit more fault tolerant. See attachment. OS: FreeBSD-11-current Driver: Wecamd (Same as what is in Linux 3.18) BTW: Thank you for keeping VDR up to date! --HPS

1 0

raspberry pi media player with VDR
by Damien Bally 23 Mar '15

23 Mar '15

Hi It doesn't seem that the rpihddevice plugin integrates a media player (as the xine plugin does). Is there a simple way to play video files using omxplayer or other within VDR ? Thanks Damien

2 1

Fwd: Re: raspbian apt repo with up to date vdr packages?
by Jouni Karvo 10 Mar '15

10 Mar '15

On 09.03.2015 16:31, VDR User wrote: > Have you tried compiling the sources yourself? It'll probably take a > while but as long as no voodoo/magic is required, I don't see why not. I am in the process. Using the instructions from http://www.vdr-wiki.de/wiki/index.php/Kategorie:Raspbian_VDR_Streaming_Clie… It seems that concerning streamdev patches: not needed for streamdev. And one hunk needs to be manually applied for remotetimers for 2.2.0 For some reason; skinnopacity + remotetimers seems to cause the menus flash in and out. Tried the latest tarball. Now trying the git. I hope it works; I prefer the default skinnopacity over lcars. yours, Jouni

1 0

Improved privacy on the VDR User Counter!
by Klaus Schmidinger 09 Mar '15

09 Mar '15

The VDR User Counter no longer requires you to enter an actual name, so you can register totally anonymously now. Go to http://www.tvdr.de/counter.htm if you're using VDR and help us in finding out how popular VDR really is. Klaus

1 0

Dummy Device PLugin
by Brian 05 Mar '15

05 Mar '15

Hi, I am attempting to get rid of my last functioning FF Card. I dont need it any more as I have clients that connect via XVDR. I tried to install the dummy device plugin but hit some problems: Dummy device plugin is not available as a package for my ubuntu setup, therefore I need to compile it myself Make was OK. But starting the plugin did not work: Source code 1 2 3 4 5 6 Mar 1 13:05:58 localhost vdr: [8766] VDR version 2.0.2 started Mar 1 13:05:58 localhost vdr: [8766] switched to user 'vdr' Mar 1 13:05:58 localhost vdr: [8766] codeset is 'UTF-8' - known Mar 1 13:05:58 localhost vdr: [8766] loading plugin: /usr/lib/vdr/plugins/libvdr-dummydevice.so.2.0.0 Mar 1 13:05:58 localhost vdr: [8766] ERROR: /usr/lib/vdr/plugins/libvdr-dummydevice.so.2.0.0: undefined symbol: _ZN7cDeviceC2Ev Mar 1 13:05:58 localhost vdr: [8766] exiting, exit code 2 Make Source code 1 2 3 4 VDR-test-cellar (SDB1): make g++ -c -DPLUGIN_NAME_I18N='"dummydevice"' -o dummydevice.o dummydevice.c g++ -shared dummydevice.o -o libvdr-dummydevice.so xgettext -C -cTRANSLATORS --no-wrap --no-location -k -ktr -ktrNOOP --package-name=vdr-dummydevice --package-version=2.0.0 --msgid-bugs-address='<see README>' -o po/dummydevice.pot `ls dummydevice.c` Here the files: Source code 1 2 3 4 5 6 7 8 9 10 11 12 13 VDR-test-cellar (SDB1): ls -la total 112 drwxr-xr-x 2 vdr users 4096 Mar 1 13:41 . drwxr-xr-x 5 root root 4096 Mar 1 13:04 .. -rw-r--r-- 1 vdr users 17990 Apr 30 2006 COPYING -rw-r--r-- 1 root root 29 Mar 1 13:41 .dependencies -rw-r--r-- 1 vdr users 4364 Aug 20 2013 dummydevice.c -rw-r--r-- 1 root root 26436 Mar 1 13:41 dummydevice.o -rw-r--r-- 1 vdr users 485 Aug 20 2013 HISTORY -rwxr-xr-x 1 root root 26384 Mar 1 13:41 libvdr-dummydevice.so -rw-r--r-- 1 vdr users 3150 Aug 20 2013 Makefile -rw-r--r-- 1 vdr users 2032 Sep 2 2007 Makefile.vdr-1.7.37 -rw-r--r-- 1 vdr users 585 Aug 20 2013 README Moved the .so to the correct directory changed permissions to 644. I have the dummydevice version for VDR > V2. Anyone any ideas? Cheers Brian --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com

2 3

VDR User Counter: now with map!
by Klaus Schmidinger 04 Mar '15

04 Mar '15

I have refurbished the VDR User Counter (see http://www.tvdr.de/counter.htm) and added a map of all registered VDR users. You can now also enter the number of VDRs you are using (default is '1' for existing entries). I'm asking all registered users to please access their entries and verify the "Location" (and adjust it as desired). By default the location is determined from the IP number and may be way off. Please make sure you press the "Change" button in the editing dialog to verify your location, even if you don't adjust it! Registered users have received an email upon registration, containing a link to the page where they can edit their entry. If that link got lost, a new one can be requested via the "Forgot your password?" function (see http://www.tvdr.de/cgi-bin/vdr-counter.pl?action=forgot). I would appreciate if many VDR users update their counter entries, or newly register their VDRs. Klaus

5 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr March 2015