vdr

vdr@linuxtv.org

2 participants
6731 discussions

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

noepg
by Marx 09 May '13

09 May '13

I'm trying to configure noepg headless. Some time ago I had GUI and configured noepeg, but now it's headless and after channels update I need to configure it again. While there is no documentation, I've found thread describing it: http://www.vdr-portal.de/board16-video-disk-recorder/board55-vdr-plugins/p9… Hovewer I use DVB-T and so channels have format like V-0-3588-1 V-0-2916-1 V-0-2917-1 V-0-3589-1 V-0-2805-1 V-0-3700-1 My channels list doesn't contain anything like 3588, 2916 etc so I don't know how to manually build this list. I'm attaching at the end my channels.conf. Marx :DVB-T TVP1 HD;EmiTel:191500:I999B7C999D999M999T999G999Y999:T:27500:102=27:103=pol@3;104=qaa@122,108=aux@122:105;106=pol,109=eng:0:1:8808:1:0 TVP1;EmiTel:184500:I999B7C78D0M64T4G16Y0:T:27500:102=27:104=pol@4;103=qaa@122,108=aux@122:105;106=pol,109=eng:0:44:8808:3:0 TVP2 HD;EmiTel:184500:I999B7C78D0M64T4G16Y0:T:27500:202=27:204=pol@4;203=qaa@122,208=aux@122:205;206=pol,209=eng:0:2:8808:3:0 TVP2;EmiTel:191500:I999B7C999D999M999T999G999Y999:T:27500:202=27:203=pol@3;204=qaa@122:205;206=pol,209=eng:0:45:8808:1:0 Polsat;EmiTel:177500:I999B7C78D0M64T4G16Y0:T:27500:102=27:103=pol@4;104=mul@122:105;106=pol:0:3:8808:2:0 TVN;EmiTel:177500:I999B7C78D0M64T4G16Y0:T:27500:202=27:203=pol@4;204=mul@106:205;206=pol:0:4:8808:2:0 TVN Siedem;EmiTel:177500:I999B7C78D0M64T4G16Y0:T:27500:502=27:503=pol@4;504=mul@106:505;506=pol:0:23:8808:2:0 TV4;EmiTel:177500:I999B7C78D0M64T4G16Y0:T:27500:302=27:303=pol@4,308=aux@4:305:0:5:8808:2:0 TV Puls;EmiTel:177500:I999B7C78D0M64T4G16Y0:T:27500:402=27:403=pol@4:0:0:6:8808:2:0 PULS 2;EmiTel:177500:I999B7C78D0M64T4G16Y0:T:27500:602=27:603=pol@4:0:0:24:8808:2:0 TV6;EmiTel:177500:I999B7C78D0M64T4G16Y0:T:27500:702=27:703=pol@4,708=aux@4:0:0:25:8808:2:0 Polsat Sport News;EmiTel:177500:I999B7C78D0M64T4G16Y0:T:27500:802=27:803=pol@4:0:0:26:8808:2:0 TVP Kultura;EmiTel:184500:I999B7C78D0M64T4G16Y0:T:27500:402=27:404=pol@4;403=qaa@106:405;406=pol:0:31:8808:3:0 TVP Historia;EmiTel:184500:I999B7C78D0M64T4G16Y0:T:27500:502=27:504=pol@4;503=aux@106:505:0:32:8808:3:0 TVP Polonia;EmiTel:184500:I999B7C78D0M64T4G16Y0:T:27500:602=27:603=pol@4:605:0:33:8808:3:0 TVP Rozrywka;EmiTel:184500:I999B7C78D0M64T4G16Y0:T:27500:3402=27:3403=pol@4;3408=aux@122:0:0:34:8808:3:0 TVP INFO Katowice;EmiTel:191500:I999B7C999D999M999T999G999Y999:T:27500:1102=27:1104=pol@4:1105:0:11:8808:1:0 ESKA TV;EmiTel:191500:I999B7C999D999M999T999G999Y999:T:27500:302=27:303=pol@3:0:0:27:8808:1:0 TTV;EmiTel:191500:I999B7C999D999M999T999G999Y999:T:27500:402=27:403=pol@3;404=mul@106:405:0:28:8808:1:0 POLO TV;EmiTel:191500:I999B7C999D999M999T999G999Y999:T:27500:502=27:503=pol@3:0:0:29:8808:1:0 ATM Rozrywka;EmiTel:191500:I999B7C999D999M999T999G999Y999:T:27500:602=27:603=pol@3,608=aux@3:0:0:30:8808:1:0

3 3

Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1
by René 06 May '13

06 May '13

I do the following in the vdr source-dir (vdr-2.0.1): make install-plugins With this my plugins end up in the plugin-dir. René On 04.05.2013 18:03 , Karim wrote: > Hi Salim, > > I was looking for "libvdr-xineliboutput.so.2.0.0.lib" file, instead of > "libvdr-xineliboutput.so.2.0.0". After I copied it in vdr/PLUGINS/lib, > problem solved. > > Thanks a lot ! > Karim > > -----Message d'origine----- > De : vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] De la part de > Karim > Envoyé : jeudi 2 mai 2013 19:24 > À : 'VDR Mailing List' > Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 > > Hi Halim, > > I have double checked : there is no "libvdr-xineliboutput.so.2.0.0" in > vdr/PLUGINS/lib (or anywhere). > I am afraid that compilation fails. > > Thanks > Karim > > > -----Message d'origine----- > De : vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] De la part de > Halim Sahin Envoyé : jeudi 2 mai 2013 05:39 À : vdr(a)linuxtv.org Objet : Re: > [vdr] Xineliboutput doesn't compil under vdr-2.0.1 > > Hi, > In the output you posted here are no error message (only warnings). > The build was successfull but xineliboutput didn't copy the binaries to > PLUGINS/lib because of the old Makefiles. > You can do it yourself :-). > cd PLUGINS/src/xineliboutput > cp libvdr-xineliboutput* ../../lib > cp libxineliboutput* ../../lib > To install the frontends: > sudo make install > Thats it. > HTH. > Halim > > > _______________________________________________ > 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 > > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >

2 1

Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1
by Karim 04 May '13

04 May '13

Hi Salim, I was looking for "libvdr-xineliboutput.so.2.0.0.lib" file, instead of "libvdr-xineliboutput.so.2.0.0". After I copied it in vdr/PLUGINS/lib, problem solved. Thanks a lot ! Karim -----Message d'origine----- De : vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] De la part de Karim Envoyé : jeudi 2 mai 2013 19:24 À : 'VDR Mailing List' Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 Hi Halim, I have double checked : there is no "libvdr-xineliboutput.so.2.0.0" in vdr/PLUGINS/lib (or anywhere). I am afraid that compilation fails. Thanks Karim -----Message d'origine----- De : vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] De la part de Halim Sahin Envoyé : jeudi 2 mai 2013 05:39 À : vdr(a)linuxtv.org Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 Hi, In the output you posted here are no error message (only warnings). The build was successfull but xineliboutput didn't copy the binaries to PLUGINS/lib because of the old Makefiles. You can do it yourself :-). cd PLUGINS/src/xineliboutput cp libvdr-xineliboutput* ../../lib cp libxineliboutput* ../../lib To install the frontends: sudo make install Thats it. HTH. Halim _______________________________________________ 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

1 0

Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1
by Karim 02 May '13

02 May '13

PS : I tried to run "make install" from vdr but xineliboutput doesn't "see" vdr. Please see below : root@pctest:/usr/local/src/vdr/PLUGINS/src/xineliboutput# make install sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type Makefile:97: ******************************************************** Makefile:98: VDR not detected ! VDR plugins will not be compiled. Makefile:99: ******************************************************** sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type Installing //usr/local/lib/xine/plugins/2.2/xineplug_inp_xvdr.so Installing //usr/local/lib/xine/plugins/2.2/post/xineplug_post_autocrop.so Installing //usr/local/lib/xine/plugins/2.2/post/xineplug_post_swscale.so Installing //usr/local/lib/xine/plugins/2.2/post/xineplug_post_audiochannel.so Installing ../../lib/libvdr-xineliboutput.so. Installing //usr/bin/vdr-fbfe Installing ../../lib/libxineliboutput-fbfe.so.1.0.90-cvs Installing //usr/bin/vdr-sxfe Installing ../../lib/libxineliboutput-sxfe.so.1.0.90-cvs If this log could help to point on the problem... Regards. Karim -----Message d'origine----- De : vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] De la part de Karim Envoyé : jeudi 2 mai 2013 19:24 À : 'VDR Mailing List' Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 Hi Halim, I have double checked : there is no "libvdr-xineliboutput.so.2.0.0" in vdr/PLUGINS/lib (or anywhere). I am afraid that compilation fails. Thanks Karim -----Message d'origine----- De : vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] De la part de Halim Sahin Envoyé : jeudi 2 mai 2013 05:39 À : vdr(a)linuxtv.org Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 Hi, In the output you posted here are no error message (only warnings). The build was successfull but xineliboutput didn't copy the binaries to PLUGINS/lib because of the old Makefiles. You can do it yourself :-). cd PLUGINS/src/xineliboutput cp libvdr-xineliboutput* ../../lib cp libxineliboutput* ../../lib To install the frontends: sudo make install Thats it. HTH. Halim _______________________________________________ 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

1 0

Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1
by Halim Sahin 02 May '13

02 May '13

Hi, In the output you posted here are no error message (only warnings). The build was successfull but xineliboutput didn't copy the binaries to PLUGINS/lib because of the old Makefiles. You can do it yourself :-). cd PLUGINS/src/xineliboutput cp libvdr-xineliboutput* ../../lib cp libxineliboutput* ../../lib To install the frontends: sudo make install Thats it. HTH. Halim

2 1

Xineliboutput doesn't compil under vdr-2.0.1
by Karim 01 May '13

01 May '13

Hi, I am trying new vdr-2.0.1 with 2 plugins : - femon (v2.0.0) - Xineliboutput (cvs from today). => Xineliboutput doesn't compil (no problem with Femon). I compile VDR with theses options : make REMOTE=LIRC VFAT=1 LCLBLD=1 Here is the error message I always get : ---------------------------------------------------------------------------- *** Plugin xineliboutput: WARNING: plugin xineliboutput is using an old Makefile! Makefile:112: ******************************************************** Makefile:113: VDR source tree not detected ! Makefile:114: VDR plugins will not be installed. Makefile:115: ******************************************************** make[1]: Rien à faire pour « all ». *** plugins with old Makefile: xineliboutput ********************************************************************** *** While this currently still works, it is strongly recommended *** that you convert old Makefiles to the new style used since *** VDR version 1.7.36. Support for old style Makefiles may be dropped *** in future versions of VDR. ********************************************************************** ---------------------------------------------------------------------------- Here is my paths : ---------------------------------------------------------------------------- /DATA/video /DATA/configVDR /usr/local/src/vdr ---------------------------------------------------------------------------- Here is my VDR Make.config ---------------------------------------------------------------------------- # # User defined Makefile options for the Video Disk Recorder # # Copy this file to 'Make.config' and change the parameters as necessary. # # See the main source file 'vdr.c' for copyright information and # how to reach the author. # # $Id: Make.config.template 2.19 2013/02/18 10:55:39 kls Exp $ ### The C compiler and options: CC = gcc CFLAGS = -g -O3 -Wall CXX = g++ CXXFLAGS = -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses # Use 'make M32=1 ...' to build a 32-bit version of VDR on a 64-bit machine: ifdef M32 CFLAGS += -m32 CXXFLAGS += -m32 endif ### The directory environment: # Default directories (adjust as necessary or desired): #PREFIX = /usr/local #BINDIR = $(PREFIX)/bin #INCDIR = $(PREFIX)/include #LIBDIR = $(PREFIX)/lib/vdr ############################ Update perso #LOCDIR = $(PREFIX)/share/locale LOCDIR = /usr/local/src/vdr/locale #MANDIR = $(PREFIX)/share/man #PCDIR = $(PREFIX)/lib/pkgconfig #RESDIR = $(PREFIX)/share/vdr ############################ Update perso #DVBDIR = /usr/src/v4l-dvb/linux/include/uapi DVBDIR = /usr/include/linux/dvb ############################ Update perso #VIDEODIR = /srv/vdr/video VIDEODIR = /DATA/video0 ############################ Update perso #CONFDIR = /var/lib/vdr CONFDIR = /DATA/configVDR #CACHEDIR = /var/cache/vdr # Overrides for preset/legacy configurations: # Use 'make LCLBLD=1' to build locale and plugin files under the source directory: ifdef LCLBLD LOCDIR = $(CWD)/locale PLUGINDIR = $(CWD)/PLUGINS ifndef PLUGIN # don't overwrite for plugins with old makefiles LIBDIR = $(PLUGINDIR)/lib endif HDRDIR = $(CWD)/include endif # Use 'make ONEDIR=1' to have all data in one single directory: ifdef ONEDIR ############################ Update perso #VIDEODIR = /video VIDEODIR = /DATA/video0 CACHEDIR = $(VIDEODIR) ############################ Update perso #CONFDIR = $(VIDEODIR) CONFDIR = /DATA/configVDR RESDIR = $(VIDEODIR) endif # Use this if you want to have a central place where you configure compile time # parameters for plugins: #PLGCFG = $(CONFDIR)/plugins.mk ### The remote control: LIRC_DEVICE = /var/run/lirc/lircd ### Define if you want vdr to not run as root: #VDR_USER = vdr ### Fallback for plugins with old makefiles: ifdef PLUGIN CFLAGS += -fPIC CXXFLAGS += -fPIC endif ---------------------------------------------------------------------------- Is there any patch I missed for Xineliboutput ? Perhaps I have to customize Xineliboutput's Makefile ? Could you help me to find the problem ? Regards. Karim

1 0

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr