vdr April 2013

vdr@linuxtv.org

38 participants
30 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

Livebuffer for VDR 2.0
by René 13 Jul '13

13 Jul '13

Hi all! Now that VDR 2.0 is just around the corner i would like to check if there is any progress to the great livebuffer that was back in the 1.6 days? I tested a 1.7.x version some long time ago, but that did not work as well as the "original" version.. René

6 8

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

Problems with VDSB, how to automate in SYSLOG
by Brian-Imap 12 May '13

12 May '13

Hi, on some channels I get Video Data Stream Broken messages, not sure quite what triggers them yet. They continue till the recording has finished. I have switched off the emergency exit when VDSB occurs, two reasons why: 1. It never cures the problem 2. Occasionally I get a single VDSB written when tuning to certain channels, the emergency exit would happen, but after the restart I would get a single VDSB again when the channel was tuned, ending up in a loop, as the VDR restart is not curing the problem. So, I wanted to know if anyone has any code or rules for rsyslog to identify multiple VDSB messages so I could trigger other actions. For example a reboot of the PC or maybe a driver load/unload. I know I could extend the VDR start script to unload/load the DVB drivers after a VDR exit too. Anyone have other suggestions maybe? Cheers Brian

3 7

Re: [vdr] Viaccess CAM support in VDR
by hederic 01 May '13

01 May '13

Karim <karim.afifi <at> laposte.net> writes: > > Hello, > > I bought the same hardware a few weeks ago. It doesn't work with VDR at this > time. > 1/ I can reset the CAM from VDR but I can't access to the CAM menu. > 2/ As soon as I plug the SMIT module in the CI slot a red led lights. (I > dont' know what it's mean). > > Is it same with you ? > I have to contact TBS support about this problem this week-end. > > To all vdr users, please give us your feedback about good CAM products. > > Regards. > Karim > Hi, I don't know if it's the same problem but i'm having errors in logfile : "CAM tried to send a buffer larger than the ecount size!" End all channels stop working even plain unencrypted channels. Bye. Hederic

2 1

RFC: one or many positioners?
by Klaus Schmidinger 28 Apr '13

28 Apr '13

I'm currently implementing support for steerable dishes, loosely based on https://linuxtv.org/patch/12911. In doing so, I'm defining a virtual base class cPositioner, which defines all the functions necessary to control the positioner. An implementation of cDiseqcPositioner will allow control of "DiSEqC 1.2" and "USALS" motors. A plugin can derive from cPositioner and implement its very own way of controlling a positioner (like through a serial or USB port or whatever). The question I have now is: will it be enough to have *one* single positioner in any given setup, or are there actually users who have more than one positioner? Supporting only a single positioner (as is done in the aforementioned patch) of course simplifies things quite a bit. So I wouldn't want to add this level of complexity unless there is a real need for it. Any opinions? Klaus

10 27

Re: [vdr] RFC: one or many positioners?
by Mike Booth 27 Apr '13

27 Apr '13

I have two positioners one for a ku dish and a second for a C Band dish. Would it be possibles to cater for the southern hemispere by a switch. Your East is my West. Mike

4 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr April 2013