vdr December 2012

vdr@linuxtv.org

40 participants
44 discussions

[DISCUSSION REQUEST] reintroduce a common make configuration file in VDR-1.7.35
by Reinhard Nissl 03 Jan '13

03 Jan '13

Hi, as mentioned in the VDR-1.7.34 announcement, Make.config is now gone for plugins. Make.config gave me the opportunity to control features or behavior of plugins and VDR at a central location without having the need to adjust each plugin's Makefile. For example, while developing vdr-xine, I could keep vdr-xine's Makefile in a distributable state and still control to enable some features I'd like to use in my local configuration. And when upgrading some other plugins at bugfix level (i. e. there are usually no new features and hence the config variables can stay the same), there was no need to adjust the Makefile due to the config entries in Make.config. Here is an excerpt of my Make.config for an example of the above mentioned configuration settings: > #xine > #VDR_XINE_VDR_HAS_TRUECOLOR_OSD = 1 > VDR_XINE_SET_VIDEO_WINDOW = 1 > VDR_XINE_VERIFY_BITMAP_DIRTY = 0 > > #burn > DVDDEV=/dev/hdd > ISODIR=/video > > #vdr > BIDI=1 > VFAT=1 > REMOTE=LIRC > LIRC_PUSHFREQ=64 # 1/s > LIRC_REPEATDELAY=250 # ms > LIRC_REPEATFREQ=32 # 1/s > #LIRC_REPEATTIMEOUT=500 # ms > #LIRC_RECONNECTDELAY=3000 # ms > LIRC_PRIORITYBOOST=1 > > #muggle > HAVE_ONLY_SERVER=1 As you can see, there is nothing like changing compiler or linker settings -- for that stuff, I really appreciate the way it is done now. In a private discussion with kls, he asked me to talk to other plugin developers too (so here we are) about that issue, so that any solution in that regard will be of broad agreement by all developers. To conclude: 1.) there is a need for a common make configuration file for both VDR and plugins. 2.) the file should be included in VDR's Makefile after including Make.config (maybe that idea should be dropped in favor of 5.a) as any VDR related option can be put into Make.config anyway). 3.) the file should be included into plugin Makefiles after having set PLUGIN and VERSION to be able to have some plugin-/version-dependent configuration. 4.) the file is optional -- maybe a template file like Make.config.template could indicate that there is something available for tuning. 5.) how do we name the file? 5.a) plugins.conf (doesn't fit perfectly for 2., to be a common file for VDR too) 5.b) Make.common 5.c) local.conf 5.d) Make.config.local 6.) where do we put the file? 6.a) kls suggested /etc/vdr at a random shot 6.b) I would like to put it next to Make.config 6.c) use pkg-config to determine path (defaults to VDRDIR) Please start sharing your ideas now ;-) Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

22 89

[ANNOUNCE] VDR developer version 1.7.35
by Klaus Schmidinger 31 Dec '12

31 Dec '12

VDR developer version 1.7.35 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.35.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.34-1.7.35.diff MD5 checksums: 3b9d0376325370afb464b6c5843591c7 vdr-1.7.35.tar.bz2 4b6fb681359325ad33a466503503e772 vdr-1.7.34-1.7.35.diff WARNING: ======== This is a *developer* version. Even though *I* use it in my productive environment. I strongly recommend that you only use it under controlled conditions and for testing and debugging. The changes since version 1.7.34: - Making sure that plugins include the VDR header files from the actual VDR source directory when doing "make plugins" (suggested by Christoper Reimer). - Increased the version numbers of all plugins to reflect the recent Makefile changes. - Removed the lines ifdef DVBDIR INCLUDES += -I$(DVBDIR)/include endif from the file Make.config.template. If set, DVBDIR is now conveyed to plugins via the CFLAGS. - Removed some redundancy from Make.config.template. - Changed "==" to "=" in the Makefile to make it POSIX style. - Added MANDIR to the vdr.pc file, so that plugins that need it can retrieve it via MANDIR = $(DESTDIR)$(call PKGCFG,mandir). - Using relative paths again when building plugins locally (by request of Udo Richter). - Plugin Makefiles can now include a configuration file for compile time parameters (requested by Reinhard Nissl). The actual name of this file can be defined in Make.config (see "PLGCFG" in Make.config.template), and existing plugin Makefiles that have compile time parameters should add the lines PLGCFG = $(call PKGCFG,plgcfg) -include $(PLGCFG) accordingly (see the "newplugin" script for details). - Re-enabled building plugins that still use pre-version-1.7.34 Makefiles. The file Make.global is present again to satisfy the "include" these Makefiles do, but the file itself contains no settings. The VDR Makefile's "plugins" target determines whether a particular plugin uses an old style Makefile and calls it accordingly. Note that this only works when building plugins from within the VDR source tree, using "make plugins" in the VDR source directory. - Removed "include" from the DVBDIR setting in the VDR Makefile (reported by Oliver Endriss). You may need to adjust your DVBDIR setting in Make.config, in case you use it. - Added maximum SNR value for PCTV Systems PCTV 73ESE (thanks to Cedric Dewijs). Have fun! Klaus

2 1

Standardized DVB signal info up for review!
by VDR User 30 Dec '12

30 Dec '12

As many know, getting standardized dvb signal info in linux has been a want for a very long time for a lot of users (and developers). There has been several talks/threads about it but nothing was ever merged. The subject has come up once again and Mauro has posted a patch for review. I know that there are at least a handful of coders here who have interest in this, including Klaus. I strongly urge anyone who would like to see this finally happen to take a few minutes and read the links below. Further, it would be great if people actively participated in the discussion so please post anything you may like to contribute to the discussion! The patch and discussion is available at: "[PATCH RFCv3] dvb: Add DVBv5 properties for quality parameters" http://www.mail-archive.com/linux-media@vger.kernel.org/msg56557.html

2 2

adjust range of snr bar at bottom of vdr screen?
by cedric.dewijs＠telfort.nl 30 Dec '12

30 Dec '12

Hi All, I use an USB DVB-T receiver. This works ok, but the snr meter at the bottom of the screen is never filled more than a few pixels, no matter how good the signal is. The problem with this receiver is that the snr figure never goes above 0x00d0. Is there a way to adjust the scaling of the signal and snr bars? I would like the snr bar to be fully filled when the figure is 0x00ff Best regards, Cedric $ lsusb Bus 001 Device 004: ID 2013:0245 PCTV Systems PCTV 73ESE $ tzap -a 0 -r 'Nederland 1' using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' reading channels from file '/home/cedric/.tzap/channels.conf' tuning to 474000000 Hz video pid 0x1b63, audio pid 0x1b64 status 1b | signal 0dbd | snr 00a2 | ber 001fffff | unc 00000000 | FE_HAS_LOCK $ dmesg [ 3.519233] dvb-usb: found a 'Pinnacle PCTV 73e SE' in cold state, will try to load a firmware [ 3.529962] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' [ 3.871202] dib0700: firmware started successfully. [ 4.373456] dvb-usb: found a 'Pinnacle PCTV 73e SE' in warm state. [ 4.373567] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 4.373732] DVB: registering new adapter (Pinnacle PCTV 73e SE) [ 4.568680] DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)... [ 4.766795] DiB0070: successfully identified [ 4.830021] Registered IR keymap rc-dib0700-rc5 [ 4.831325] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:10.4/usb1/1-6/rc/rc0/input6 [ 4.831485] rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:10.4/usb1/1-6/rc/rc0 [ 4.831681] dvb-usb: schedule remote query interval to 50 msecs. [ 4.831688] dvb-usb: Pinnacle PCTV 73e SE successfully initialized and connected.

4 6

road-map
by Peter Münster 29 Dec '12

29 Dec '12

Hi, Is there some kind of road-map for VDR? Things like: - What is expected to happen before next stable release? - Approximate time-line. - What features are to be integrated? -- Peter

2 1

[ANNOUNCE] VDR developer version 1.7.34
by Klaus Schmidinger 27 Dec '12

27 Dec '12

VDR developer version 1.7.34 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.34.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.33-1.7.34.diff and a helper patch for plugin Makefiles can be found at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.33-pluginmakefile.diff MD5 checksums: 55d9aba62563efe39ee040e987f7023c vdr-1.7.34.tar.bz2 019ba806b263f7054dbd0da8956ea73b vdr-1.7.33-1.7.34.diff 6c2b8efe5eead6822f006bc867ccb324 vdr-1.7.33-pluginmakefile.diff WARNING: ======== This is a *developer* version. Even though *I* use it in my productive environment. I strongly recommend that you only use it under controlled conditions and for testing and debugging. IMPORTANT: ========== This version comes with revised versions of the Makefiles for VDR itself and all of its standard plugins. As a result of this, existing plugins will no longer build with this version of VDR, unless their Makefiles are properly adapted. To do so, please follow the instructions given below. There is also a generic patch (see below) that might help you update your plugin's Makefile. If you do want to build this version of VDR with plugins that don't have their Makefiles adapted yet, you can simply copy the Makefile, Make.global and Make.config (if applicable) files from a previous version of VDR into this source and use them. Note, though, that you cannot mix old and new Makefiles. All Makefiles for VDR and all plugins must be either old or new! PLEASE GIVE THE PLUGIN DEVELOPERS SOME TIME TO ADAPT THEIR MAKEFILES ACCORDINGLY. AFTER ALL, IT'S CHRISTMAS, SO THEY PROBABLY HAVE BETTER THINGS TO DO THAN SIT AT THEIR COMPUTERS ;-). The changes since version 1.7.33: - Changed the type of the TimerMatch parameter in cSkinDisplayMenu::SetItemEvent() from 'int' to 'eTimerEvent' (reported by Christoph Haubrich). - Updated the Estonian OSD texts (thanks to Arthur Konovalov). - Fixed cOsd::GetBitmap() to always return NULL if a non-exising area is requested. - Added several missing "`ls $^`" in the calls to xgettext in plugin Makefiles and the "newplugin" script. - Fixed setting the --package-name and --package-version options in the calls to xgettext in several plugin Makefiles. - Added "-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE" to the DEFINES in the Makefile (somehow got lost from Make.config.template in version 1.7.13). - Removed some redundancy in the Makefile/Make.global/Make.config mechanism (suggested by Christopher Reimer). The file Make.global is no longer used, and plugin Makefiles don't include the file Make.config any more. Instead they now retrieve all necessary information through calls to pkg-config. - The plugin Makefiles now have a separate 'install' target (suggested by Christopher Reimer). In order to still allow the normal building of VDR (with all plugins in its ./PLUGINS/src subdirectory, the plugin libraries in ./PLUGINS/lib and the i18n files in ./locale) the VDR Makefile checks the settings of LIBDIR and LOCDIR when building the plugins from within the VDR source directory. If these macros have their default values, then the 'install' targets of the plugins' Makefiles are called. Otherwise the 'all' targets are called and the plugins are merely built, and will have to be installed by a call to 'make install-plugins'. This now also allows a user to copy a plugin source to any directory, change into that directory and do 'make' and 'make install' to have the plugin installed to wherever the local installation of VDR expects them. - Plugin Makefiles now use DESTDIR and the 'install' program (thanks to Christopher Reimer). - Due to the changes to the plugin Makefiles, existing plugins will not build with this version of VDR any more. You can either use the new 'newplugin' script to generate a dummy plugin directory and use the Makefile from there (adapting it to your particular plugin), or apply the patch from ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.33-pluginmakefile.diff to your Makefile to make the necessary changes (see comments in that file for details). - Added the new menu categories mcChannelEdit, mcTimerEdit, mcScheduleNow, mcScheduleNext, mcRecordingInfo, mcPluginSetup, mcSetupOsd, mcSetupEpg, mcSetupDvb, mcSetupLnb, mcSetupCam, mcSetupRecord, mcSetupReplay, mcSetupMisc and mcSetupPlugins. - Updated the Italian OSD texts (thanks to Diego Pierotto). - Fixed replay stuttering close to the end of an ongoing recording (reported by Andreas Regel). - Fixed cIndexFile::GetNextIFrame() to properly handle the case where the very last frame is an I-frame (which normally shouldn't occur). - Fixed replaying ongoing recordings from other VDR instances. Merry Christmas! Have fun! Klaus

3 5

Positioner and multi-tuner setup?
by Antti Hartikainen 27 Dec '12

27 Dec '12

Hi. I would want to somehow configure VDR to use positioner (H-H motor) and dual tuner setup, to receive two transponders from same source at one time. My current hardware setup is: TechnoTrend S2-6400 dual tuner DVB-S2 with H/W decoder, H-H motor and a quad LNB. I'm using diseqc commands in diseqc.conf to control the motor, as GOTOXX patch and rotorng plugin are both too buggy to be used. Rotorng I used to store the positions. Currently I only have one tuner in use, and it is connected to the motor. I was wondering if it would be somehow possible to get second tuner in use also. It would be connected directly to LNB, and that tuner would be limited to the same satellite source as the other tuner is tuned to, and have independent frequency/polarization. Thanks. PS. What is the current recomended way for using positioner with VDR? Preferred would be a USALS capable setup.

1 0

Debugging facility in VDR Makefile(s)?
by Eike 26 Dec '12

26 Dec '12

Hello! When I had a deeper look into VDR, I wondered why there seems to be no debugging facility. I added the following to VDR's Makefile: debug: CFLAGS += -DDEBUG -ggdb3 -O0 debug: CXXFLAGS += -DDEBUG -ggdb3 -O0 debug: all ... so "make debug" creates an executable where no variables are optimized out and and no statements are reordered. I guess this could be useful for other people as well. Or did I miss something and this is already included somewhere? Ciao, Eike PS: Sorry, I misdirected this mail to vdr-owner(a)linuxtv.org first.

1 0

[ANNOUNCE] Remote Control Plugin 0.5.0
by Oliver Endriss 26 Dec '12

26 Dec '12

Hi, there is an update for the remote control plugin. Compilation has been tested with VDR 1.4.7, 1.6.0, 1.7.31 and 1.7.34. Other releases should work as well. History: -------- 2012-12-26: Version 0.5.0 - gettext detection modified to use $(VDRDIR)/i18n.h (thanks to Tobias Grimm). - Updated Italian language texts. - Fixed some compiler warnings. - Telnet section added to FAQ. - GPL text added to all source files. - Fixed crash with TTY and/or Telnet remotes when VDR terminated. - Access /proc/av7110_ir in write-only mode (required by kernel 2.6.34+). - Adopt Makefile for vdr 1.7.34+. It can be downloaded from http://www.escape-edv.de/endriss/vdr/ See README for details. Short description: ------------------ This plugin extends the remote control capabilities of vdr. The following remote control devices are supported: (a) linux input device driver ('/dev/input/eventX', X=0,1,2,...) - Built-in remote control port of the TT DVB-S2 6400 (HD full-featured card). - Built-in remote control port of the av711x-based DVB cards (SD full-featured cards), e.g. DVB-S Nexus. - Remote control port of some budget cards, e.g. Nova-CI. - Other input devices. See file FAQ for a list of cards which have been reported to work. (b) keyboard (tty driver): /dev/console, /dev/ttyX (c) TCP connection (telnet) (d) LIRC Have fun, Oliver -- ---------------------------------------------------------------- VDR Remote Plugin 0.5.0: http://www.escape-edv.de/endriss/vdr/ 4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/ Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/ ----------------------------------------------------------------

1 0

Reserve device for Live-Tv
by Ingo Prochaska 21 Dec '12

21 Dec '12

Hello, I would like to have one dvb-device dedicated for live tv. Or in other words: I want vdr to record on all-dvb-devices - 1, so that one device is still available for viewing via the output-front-end or streamdev. Perhaps its possible to configure vdr to behave like this - but I have no clue how to accomblish this... Regards, Ingo

8 18

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr December 2012