vdr November 2012

vdr@linuxtv.org

33 participants
25 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-plugin-IPTV not working with vdr-plugin-xvdr and XBMC
by Paulo Louro 27 Oct '13

27 Oct '13

Hello guys/girls, I have been trying to make iptv plugin to work with xvdr and xbmc, but i haven't manage to have any success. Xvdr is a plugin that needs a 100% complete TS to work, including PAT and PMT tables. By searching and "debuging" iptv and xvdr plugins code, I found out that the problem may be related with the filtering of PIDs, but i cant manage to understand how does the filtering system works. Is there any documentation or Howto example on how to program a plugin that implements cDevice interface on the right way? Some extra comments can be found on Pipelka github: https://github.com/pipelka/xbmc-addon-xvdr/issues/64 Regards,Louro

2 1

vdr-prefermenu and vdr 1.7.21
by Arturo Martinez 27 Sep '13

27 Sep '13

Is there a patch for vdr-prefermenu to work with vdr 1.7.21 ?

6 5

HDMI CEC support in VDR with Pulse Eight Adapter
by Morfsta 14 May '13

14 May '13

Hi, Has anyone had any experience of working with the Pulse Eight USB to HDMI CEC adapter [1] with controlling VDR when using a graphics card or other non-CEC device as an output? It seems that support for this has been implemented within Myth TV and XBMC, but I haven't seen anything on VDR. It would be very useful to be able to control VDR from your TV handset and also be able to power on / off VDR with all other HDMI CEC devices. I wondered if anyone has started work on a CEC VDR PLUGIN or whether it should be implemented within the core itself, alongside LIRC and KBD? If not, I might look at trying to hack up a plugin if I get some time. Thanks, Morfsta [1] http://www.pulse-eight.com/store/products/104-usb-hdmi-cec-adapter.aspx

2 1

VDR form packages
by Marx 21 Mar '13

21 Mar '13

Hello I use Debian for years and to keep it clean I'm trying to use all software from packages. It generally works, hovewer I have problem with VDR, XBMC and drivers. Usually to have the newest driver I need to use some unstable version of VDR with the newest possible kernel. VDR in Debian is an option, hovewer it's usually behind the newest VDR, and number of plugins in repository is low. This lead to alternative repositories. I know two valuable: e-tobi and yavdr. I was using e-tobi but it lately isn't updated to the newest VDR. Yavdr is built on top of Ubuntu, and while it generally works on Debian, it's not recommended (some things doesn't work). So there is an option to build packages myself - really no option, because I have to make package manually for every plugin and for every new version of VDR. Any idea? Marx

8 31

[ANNOUNCE] vdr-xine-0.9.4 plugin
by Reinhard Nissl 15 Mar '13

15 Mar '13

Hi, I'm pleased to announce maintenance release 0.9.4. You can find it on my homepage as usual: http://home.vr-web.de/~rnissl Excerpt from HISTORY: 2011-03-16: Version 0.9.4 - The contained xine-lib-1.1 patch is outdated but might still work. The patch will get updated in 0.9.5. - A couple of xine-lib-1.2 patches is still waiting to get commited. vdr-xine-0.9.4 should be able to work without them. - Fixed a couple of things in xine-lib-1.2 and VDPAU. - Fixed compilation for VDR-1.2.x and VDR-1.6.x. - Updated Makefile to VDR-1.7.17. - Added support for VDR-1.7.17s TrueColor OSD. - Added support for VDR-1.7.12s changed PCR handling. - Added support for VDR-1.7.11s semantic of MakePrimaryDevice. - Resolved a segfault regarding VDR-1.7.x and cutting marks in radio recordings (thanks to Joachim Wilke for providing a fix). - Included Lithuanian translation (thanks to Valdemaras Pipiras). - Included Slovak translation (thanks to Milan Hrala). - Included Chinese and Taiwanese translations (thanks to NanFeng). - Fixed MANUAL about centre_cut_out_mode (thanks to Vorg on #xine-vdpau). Enjoy. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

4 6

[ANNOUNCE] vdr-rotorng-0.3
by Morfsta 12 Mar '13

12 Mar '13

Hi, The third version of my plugin rotorng has been released here: - http://projects.vdr-developer.org/projects/plg-rotor-ng/files This plugin allows you to steer a disecq 1.1 rotor, find satellites with a signal meter and to store them at given positions. It also has a rudimentary channel scanner which works with both DVB-S and S2. Much of this code has been merged together from the existing actuator and rotor plugins, so thanks to the developers of those for their work. Please see the README file, there are a number of functions within the user interface that aren't fully implemented or working but the main functions are there. Changes since previous version: - 2012-10-11: Version 0.2 - updated sat card store value in config, always resetting - fixed issue with change implemented in 1.7.23 (thanks to Ihanisch) 2012-10-21: Version 0.3 - Added patch for vdr-1.7.27 onwards, old patch for VDR still exists also. - Fixed problem with cStatusMonitor::ChannelSwitch call introduced in VDR 1.7.26 so dish moves on channel change Good luck!

4 10

Tuning timeouts blocks the other adapter
by Mariusz Bialonczyk 13 Jan '13

13 Jan '13

Hi guys! My system is currently based on two dvb cards: - Prof 7301 PCI - Prof 8000 PCIe Both of them is using stv090x frontend. I am using VDR 1.7.31 and i have the following problem: When one adapter has a problem with tuning in epg-scan mode, (eg: frontend 1/0 timed out while tuning to channel...), then the vdr freeze for a while. I can see this while watching tv on the second one (busy) adapter: the xvdr plugin stops feeding xbmc with stream causing buffering and/or artifacts. Another example is that both adapters are in epg-scan mode and i am watching a recording, then every time when i've got "timed out while tuning" in the log, the replay of the recording stops (resulting in a buffering) for a while. When i start vdr with -D0 or -D1 then i've got no problems (but also no 2nd adapter ;) Is it possible that it is caused by some global lock or mutexes in VDR? regards, -- Mariusz Białończyk jabber/e-mail: manio(a)skyboo.net https://github.com/manio

4 7

polarization character case in channels.conf
by Mike Hay 03 Dec '12

03 Dec '12

Hi list, I recently lost access to all vertically polarised channels and after quite a bit of floundering about I discovered the reason for this is due to the case of the polarisation character in channels.conf. According to the vdr changelog it has been possible to specify this in either upper or lower case since version 0.6 but it seems this is not correct - at least in 1.7.31. I generate my channels.conf with w_scan and it produces lower case "h" and "v" for polarisation. It seemed to work OK for the horizontal channels but not the vertical. Perhaps it works for horizontal because this is the default position... Anyway I have resolved my issue by manually changing the case of these characters in channels.conf but wondered if this is really a bug or just a misunderstanding on my part. Regards, Mike

4 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr November 2012