vdr March 2013

vdr@linuxtv.org

67 participants
64 discussions

Markad
by Marx 31 Mar '13

31 Mar '13

I would like to enable ad marking in markad plugin. Does it work only for HD channels? Does it need to have defined channel logos somewhere? Can you recommend some guide/blog entry/description about markad? Marx

3 2

Absolutely last chance for translations for VDR version 2.0.0!
by Klaus Schmidinger 29 Mar '13

29 Mar '13

VDR version 2.0.0 is going to be released this Sunday, March 31. This is the absolutely last chance to have all OSD texts translated into your local language. After tomorrow, March 30, 15:00 (3pm) CET I won't adopt any more patches to *.po files. The languages not yet translated completely are da_DK.po: 134 el_GR.po: 197 hr_HR.po: 134 nn_NO.po: 262 pt_PT.po: 28 sl_SI.po: 1 tr_TR.po: 134 Klaus

1 0

[ANNOUNCE] VDR Power Button Daemon 0.0.1
by Manuel Reimer 29 Mar '13

29 Mar '13

Hello List, I have written a small daemon, which can replace acpid on VDR systems and was written with dedicated VDR systems in mind. Core Features: - Faster than acpid with all the required external scripts. - Emergency reboot feature. You don't loose the power button as safe emergency exit button. Just press it four times within three seconds and a clean reboot is triggered. - Very easy to set up. If you want, you can just copy the "vdrpbd" file to your VDR system and execute it. VDR should react to the power button immediately! - Systemd integration. If systemd is detected, then vdrpbd tries to register itself as "power button inhibitor". The module "Net::DBus" is required for this to work. Note that it requires an up-to-date kernel, as the only supported way, to access the power button, is the input layer. There is no "netlink" support and I also won't add it. Download from here: http://projects.vdr-developer.org/attachments/download/1331/vdrpbd-0.0.1.ta… To post bug reports and feature requests, you may use the ticket system here: http://projects.vdr-developer.org/projects/vdrpbd/issues/new Or just answer to this mail and tell me about your opinion and/or give feature requests. Yours Manuel Reimer

4 7

[PATCH] MaxThemeName and MaxSkinName limit
by Lucian Muresan 27 Mar '13

27 Mar '13

Hi, thank you Klaus for holding up your release plan for 2.0! However, I hope this minor patch won't be too much trouble for you, as it only increases the limit of 16 to theme and skin names, letting them be NAME_MAX as almost any files, since these names can also be involved in file names. Was there a good reason to limit them at 16 only, perhaps the fear that the name won't fit on the OSD? I don't really think someone would really make use of as many as 255 characters for this. On the other hand, users just encountered crashes with plugins which (unfortunately, yet) have themes of their own, when just adding a new theme with a name longer than 16 and at the same time the original plugin author relied on MaxThemeName when allocating the string length. So, what do you think, easy to adopt? Regards, Lucian

11 29

Problem with vdr and a Hauppage WinTV-Duet
by Marc 27 Mar '13

27 Mar '13

Hi, I try to use a new receiver (Hauppage WinTV-Duet, a dual dvb-t usb receiver) but it doesn't work. When I start vdr, I can see them in vdr : vdr: [16411] new device number 3 vdr: [16436] section handler thread started (pid=16411, tid=16436, prio=low) vdr: [16411] frontend 2/0 provides DVB-T with QPSK,QAM16,QAM64 ("DiBcom 7000PC") vdr: [16411] probing /dev/dvb/adapter3/frontend0 vdr: [16411] creating cDvbDevice vdr: [16411] new device number 4 vdr: [16439] section handler thread started (pid=16411, tid=16439, prio=low) vdr: [16438] tuner on frontend 2/0 thread started (pid=16411, tid=16438, prio=high) vdr: [16411] frontend 3/0 provides DVB-T with QPSK,QAM16,QAM64 ("DiBcom 7000PC") but when I try to use one of them, vdr complains with the following message : vdr: [16438] frontend 2/0 timed out while tuning to channel 7, tp 562 (same message for the second adapter) I can see the green led switching on (witch means vdr access the adapter) but only for a few seconds before the above message. vdr tries again without success. There is no more log with loglevel 3. I tried manually and everything works : tzap -a 2 -r -c ~/tzap.chan "France 2" using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' reading channels from file '/root/tzap.chan' tuning to 586000000 Hz video pid 0x0078, audio pid 0x0082 status 1f | signal ac22 | snr 00d5 | ber 001fffff | unc 0000007d | FE_HAS_LOCK status 1f | signal abe6 | snr 00dd | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal abdb | snr 00d8 | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal abaa | snr 00e6 | ber 00000000 | unc 00000000 | FE_HAS_LOCK ... then, I can see the channel with mplayer in /dev/dvb/adapter2/dvr0. Are there some parameters in vdr to get my adapter working ? Thanks, Marc.

1 0

[PATCH] VDR 1.7.42: fix pending timers
by Klaus Schmidinger 26 Mar '13

26 Mar '13

There has been a bug report regarding overlapping "pending" timers. The original posting can be found here: http://www.vdr-portal.de/board17-developer/board97-vdr-core/p1134445-proble… The diagram "version 2" shows 3 timers with different priorities, where timers 1 and 3 can record simultaneously, while timer 2 can only record by itself. This is due to limitations imposed by "device bonding", but similar situations may also occur in other environments. The problem here is that at time 'C', timer 3 starts and forces timer 2 to stop due to its higher priority. Now timer 1 would also be able to record, but it doesn't do so until timer 2 expires. This is caused by timers 1 and 2 being in the "pending" state, but timer 2 always being chosen in cTimers::GetMatch(time_t t) due to its higher priority. The attached patch fixes this. Please apply and test it. I'm considering to include this in the final version 2.0.0 which shall be released on sunday, so I need to know whether it causes any negative side effects. Klaus

1 0

Re: [vdr] Like VDR on facebook!
by master.of.brainless.things＠gmx.net 26 Mar '13

26 Mar '13

facebook hat doofe ohren... -- "The significant problems we face cannot be solved at the same level of thinking we were at when we created them." -Albert Einstein

1 0

Like VDR on facebook!
by Klaus Schmidinger 25 Mar '13

25 Mar '13

https://www.facebook.com/VideoDiskRecorder Klaus

3 3

[ANNOUNCE] skin nOpacity 0.1.0
by Stefan Braun 25 Mar '13

25 Mar '13

Hi list, version 0.1.0 of the true color skin nOpacity is now available. Direct download: http://projects.vdr-developer.org/attachments/download/1287/vdr-skinnopacit… nOpacity needs at least VDR 1.7.34 and runs with every true color capable output device (softhddevice, xine, xineliboutput, FF S2-6400). For more information see the Wiki at vdr-developer.org: http://projects.vdr-developer.org/projects/skin-nopacity/wiki Feature requests or bug reports can be posted at http://projects.vdr-developer.org/projects/skin-nopacity/issues/new You're welcome to to provide a translation for your language. Just provide an appropriate po file in the ticket system. Cheers Louis

6 16

[ANNOUNCE] VDR developer version 1.7.42
by Klaus Schmidinger 24 Mar '13

24 Mar '13

VDR developer version 1.7.42 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.42.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.41-1.7.42.diff MD5 checksums: 5a9ec132781045061325162fe03c2763 vdr-1.7.42.tar.bz2 011f2838026f849f031c40b2f06d9181 vdr-1.7.41-1.7.42.diff Approaching version 2.0.0: ========================== If there are no more serious bug reports, the final version 2.0.0 of VDR shall be released on March 31, 2013. So please test this developer version intensely and report any problems you might encounter as soon as possible. The following language files still have the given number of untranslated texts: da_DK.po: 134 el_GR.po: 197 hr_HR.po: 134 lt_LT.po: 1 nn_NO.po: 262 pt_PT.po: 28 sl_SI.po: 1 tr_TR.po: 134 If nobody takes care of these, they will remain untranslated in version 2.0.0. DEADLINE FOR SUBMITTING TRANSLATIONS IS SATURDAY, MARCH 30! The changes since version 1.7.41: - Updated the Serbian OSD texts (thanks to Zoran Turalija). - Added maximum SNR and signal strength value for TechniSat SkyStar HD2 (thanks to Zoran Turalija). - Renamed the language file sr_SR.po to sr_RS.po (pointed out by Zoran Turalija). - Fixed loading the setup.conf file in case a parameter contains the '#' character (thanks to Johann Friedrichs). - The "Resume" button in the main menu is now only active if the respective recording actually exists (reported by Johann Friedrichs). - The cutter now allocates its buffers on the heap to avoid problems on systems with limited stack space (suggested by Juergen Lock). - Fixed formatting the channel definition example in the vdr(5) man page (thanks to Dominic Evans). - Updated the default channels.conf file. Have fun! Klaus

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr March 2013