vdr December 2006

vdr@linuxtv.org

69 participants
55 discussions

pid change, timers and an after-skript
by Janne Liimatainen 07 Dec '06

07 Dec '06

Hey, the problem is this: when recording a program with a tailtime of eg. 5 minutes there is often a pid change when the show actually ends, which causes the recording to stop and then restart again for a few minutes. And when using a script that automatically processes recordings after they are done this causes the post-process script run twice. I could of course check the time the script gets run against the timer's end time, but are there any more elegant solutions? Thanks for your help! -Frozen-minded Janne

2 1

Problem with aspect ratio after update
by Matthias Fechner 07 Dec '06

07 Dec '06

Hi, I updated these days my system from kernel 2.6.15.4 to 2.6.19 and now every movie on every program is now in 16:9 even the movies which had been 4:3 before. Is there something broken in the driver from the kernel or is it a problem with the firmware or VDR? I have VDR 1.4.4 running and 2xFF card (DVB-S). Best regards, Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook

3 3

vdr 1.4.4 / xineliboutput 1.0.0_pre6 causes complete system freeze
by Matthias Dahl 05 Dec '06

05 Dec '06

Hi everyone. I am currently trying to get away from MythTV (which never lived up to my expectations). So far, vdr has been nothing but great. Except for the following which just drives me crazy: Whenever I am using vdr-sfxe or xine-ui to watch tv, switching channels sometimes freezes my system hard... except for the Magic SysRq reboot key, its totally dead. (no remote logging, no emergency umounting, ...) So far I have been able to come up with a testcase that reproduces the problem or at least some problem... 1) start vdr as demon (with xineliboutput) 2) fire up vdr-sxfe (use a local pipe or rtsp or whatever) or xine xvdr:// 3) send a SIGKILL to the frontend process (so either vdr-sxfe or xine) 4) system freezes hard immediately without any logs or whatsoever I believe this is the same problem I have been expierencing at random. I guess what happened previously was that vdr-sxfe or xine died unexpectedly and which naturally led to the same result. What's interesting though, starting vdr directly (not as demon) with the xineliboutput, I am unable to reproduce the problem. I can kill the process, zap around as much as I want... no problem. Here some more informations: - OS: Gentoo ~amd64 (64 bit -hicks-) - KNC ONE DVB-C Plus with Cineview and Alphacrypt Light CAM - fresh (a few days old) dvb tree from mercurial repository (linuxtv.org) - 2.6.19rc6git10 (almost 100% identical to 2.6.19-final) - xinelib 1.1.3_pre20061129 - vdr 1.4.4 with bigpatch, setup plugin, jumpplay, dvbplayer, cmdsubmenu dolby-record-switch, submenu and femon - xineliboutput 1.0.0_pre6 - gcc 4.1.1 (gentoo rev 2, meaning there are a lot of fixes included and thus not vanilla) - glibc 2.5 Naturally I also tried older kernels and older dvb checkouts but that didn't change anything. I do believe now that the problem is somewhere either in vdr or in xineliboutput because my system is normally rock solid and I cannot force a total freeze with just some dvb apps even if I want to. (believe me, I tried) Being an "computer scientist" myself, I know there is nothing more important than debugging the whole thing. Unfortunately that's hard to do when the whole system just takes a break. ;-) I tried getting getting some infos out of this with gdb but so far nothing turned up. There is also no kernel oops or anything like it reported. The strangest thing about this: vdr runs as vdr:vdr and vdr-sxfe is also just a regular user. Actually user processes shouldn't be able to freeze the system hard. ;-( By the way, I also opened up a post over at vdr-portal.de which turned up that I am not the only one seeing this problem. (german) http://www.vdr-portal.de/board/thread.php?postid=548719 I also email Petri (author of xineliboutput) a few days ago with roughly the same msg here but I haven't yet received an answer. Thanks for any help or advice in advance! If there is anything I can do to help to get to the bottom of this, I'd be more than glad. Have a nice weekend, matthew.

3 3

Segfault if cSkinDisplayMessage is replaced by another display object
by Udo Richter 05 Dec '06

05 Dec '06

Hi Klaus, I've isolated an null pointer dereferencing bug in cSkins::Message(): In the very rare case that a message is displayed using a cSkinDisplayMessage object, and the message is not removed before another cSkinDisplay object takes control, the next attempt to display a message while no cSkinDisplay::Current() object is available causes a segfault. The reason is that the cSkins::displayMessage pointer is not cleared if another cSkinDisplay object takes over. cSkins::Message() sees an existing displayMessage object, but accesses the non-existing cSkinDisplay::Current(), assuming they're both the same. The only way I know how to trigger this is to use mtStatus messages and allow user activity while the message is shown. I don't think that plain VDR can trigger this on its own. The attached patch changes cSkins::Message() by only checking the existence of cSkinDisplay::Current(). If no current cSkinDisplay exists, any old displayMessage object is deleted and a new one is created. Cheers, Udo --- skins.c.orig 2006-11-30 02:19:41.705523304 +0100 +++ skins.c 2006-11-30 02:33:28.269230960 +0100 @@ -226,8 +226,11 @@ } if (!Current()) return kNone; - if (!cSkinDisplay::Current() && !displayMessage) + if (!cSkinDisplay::Current()) { + if (displayMessage) + delete displayMessage; displayMessage = Current()->DisplayMessage(); + } cSkinDisplay::Current()->SetMessage(Type, s); cSkinDisplay::Current()->Flush(); cStatus::MsgOsdStatusMessage(s);

1 1

vdradmin: can't "watch tv"
by Suur Karu 05 Dec '06

05 Dec '06

Installed vdradmin-am-3.5.1 give me strange TV picture on "Watch TV" menu: http://kodu.neti.ee/~pa000t/files/vdradmin.gif make.sh check said that all Perl modules presents. Using Slackware 11.0 (2.6.18 kernel) with 2 budget cards. Regards, SK

5 4

Record a channel without displaying?
by Michael McQuillan 05 Dec '06

05 Dec '06

I've been using VDR for quite a while now, I'm a bit behind on the versions, but having limited linux knowledge I'm sticking to the adage if it ain't broke don't fix it! Anyway, I'd now like to record an HD channel which is available to me (MPEG2). I have a single FF card which obviously can display it directly, running in softmode is not really an option as the machine isn't upto decoding the HD stream via software so I've written off the hope of viewing HD for now. I am still interested in recording the HD streams for play back on a standalone. The problem I run into is that if I just setup a normal timed recording vdr restarts several times as the FF attempts to display, so the recording is unwatchable. I then had an idea to playback a previous recording whilst recording HD which stops the display of HD but as the recordings suffer a little bit when (I guess) the card is doing to much at once. Finally I came up with the working solution of starting a playback, pausing it and then letting the timer do the rest, this works for the most part and I have been able to get decent recordings. I don't know if pause has a time out on it either so this may not work for long recordings (I've only done 1 hour at a time so far) and sometimes when a recording starts it stops my playback (I think this may be an issue with my set up) I was wondering if there was a better way to do this, say to tell VDR that although the HD channel is available I do not wish to "watch" it when a timer starts. There are no other channels on that transponder so I can't tune to a different channel at the same time (And I suspect this would have the same problem as with playback a recording) I hope I've explained this well! Any suggestions? Michael

2 1

xineliboutput brightness
by Simon Baxter 03 Dec '06

03 Dec '06

Hi. I've tried adjusting the picture by adding: gui.vo_brightness:35616 gui.vo_contrast:33900 gui.vo_saturation:42940 ...to ~/.xine/config_xineliboutput but it has no affect. Any ideas?

1 0

[ANNOUNCE] VDR maintenance patch 1.4.4-1
by Klaus Schmidinger 03 Dec '06

03 Dec '06

VDR maintenance patch 1.4.4-1 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.4-1.diff This is a 'diff' against version 1.4.4. Small fixes to the officially released VDR versions will be first made available as "maintenance patches" in the Developer directory, so that they can be reviewed and tested before a new official release is published. So please apply the above patch and report whether it works (or if it causes any new problems). The changes since version 1.4.4: - Some improvements to the man pages (thanks to Ville Skyttä). - Fixed a possible segfault in cSkins::Message() (thanks to Udo Richter). - Made the getskyepg.pl script of the 'sky' plugin send a user agent message to the server, according to the rules at http://bleb.org/tv/data/listings. If your version of 'wget' doesn't support the -U option to set the user agent, use the new option -U of getskyepg.pl to have the information added to the URL as a query string. - The getskyepg.pl script now replaces "&" with "&". - Fixed a possible crash in remux.c on 64-bit machines (thanks to Reinhard Nissl). - Fixed a typo in the change to the "Use small font" setup option in version 1.3.47 in the HISTORY and CONTRIBUTORS file (reported by Andreas Brugger). - Added a missing 'const' to cRecordingInfo::ChannelID() (reported by Andreas Brugger). This required the APIVERSION to be increased, so plugins will have to be recompiled. - Now calling cPluginManager::Active() only if VDR is really trying to shut down, and waiting for 5 minutes before calling it again (thanks to Jörg Wendel for reporting that cPlugin::Active() was called too often, and to Udo Richter for some hints on how to improve this). - Replaced 'unsigned long long' with 'uint32_t' and 'uint64' with 'uint64_t' to avoid problems on 64-bit machines. Have fun! Klaus

4 8

[ANNOUNCE] VDR maintenance patch 1.4.4-2
by Klaus Schmidinger 03 Dec '06

03 Dec '06

VDR maintenance patch 1.4.4-2 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.4-2.diff This is a 'diff' against version 1.4.4-1 (which is the official version 1.4.4, patched with ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.4-1.diff). Small fixes to the officially released VDR versions will be first made available as "maintenance patches" in the Developer directory, so that they can be reviewed and tested before a new official release is published. So please apply the above patch and report whether it works (or if it causes any new problems). Since the removal of the 'uint64' typedef has caused some turmoil amoung the plugin users/authors, this quick patch introduces a define that makes 'uint64' available again This patch also uses the previous naming scheme again, which I had messed up in the 1.4.4-1 patch. The changes since version 1.4.4-1: - Added '#include <stdint.h>' to font.h (reported by Peter Pinnau). - Added a compatibility define for 'uint64' to tools.h, so that existing plugins don't need to be modified immediately (reported by Suur Karu). This will be removed in version 1.5. Have fun! Klaus

1 1

[ANNOUNCE] Remote Control Plugin 0.3.9
by Oliver Endriss 03 Dec '06

03 Dec '06

Hi, there is an update for the remote control plugin. History: -------- 2006-12-03: Version 0.3.9 - Added Russian language texts (thanks to Waldemar Nikel). - Replaced uint64 by uint64_t for APIVERSION >= 1.4.5. 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 av711x-based DVB cards (aka full-featured cards), e.g. DVB-S Nexus [1] - remote control port of some budget cards, e.g. Nova-CI [2] - other input devices (not tested, please report success!) 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 Notes: [1] supported by DVB and dvb-kernel [2] supported by dvb-kernel only Summary of command line options: -------------------------------- -i dev, --input=dev select device which supports the /dev/input protocol -l dev, --lirc=dev select LIRC device -t dev, --tty=dev select terminal device -T dev, --TTY=dev select terminal device with 'OSD' -p tcp:n, --port=tcp:n select connection on tcp port <n> Examples: --------- vdr -Premote vdr -P"remote -i autodetect" Try to autodetect device '/dev/input/eventX' (X = 0,1,2,...). If no device can be identified, '-i /dev/input/event0' is used. vdr -P"remote -i /dev/input/event2" use specified input device '/dev/input/event2' vdr -P"remote -l /dev/lircd" select LIRC remote control vdr -P"remote -p tcp:3333" wait for a telnet connection on tcp port 3333 (use 'telnet vdr 3333' to access this port) vdr -P"remote -t /dev/tty10" use terminal device without 'OSD' vdr -P"remote -T /dev/tty10" use terminal device with 'OSD' vdr -P"remote -i autodetect -p tcp:3333 -t /dev/tty10" use multiple devices Have fun, Oliver -- -------------------------------------------------------- VDR Remote Plugin 0.3.9 available at http://www.escape-edv.de/endriss/vdr/ --------------------------------------------------------

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr December 2006