vdr January 2006

vdr@linuxtv.org

153 participants
203 discussions

Vdradmin
by Rene Hertell 26 Jan '06

26 Jan '06

Hi, I'm trying to find some replacement for vdradmin that would be a bit more reliable than the am-versions, and newer than the original vdradmin 1.96. The 1.96 has so far been working best with the auto timers if compared with the am-versions of vdradmin. The biggest problem with the am-versions of vdradmin was that I got recordings that claimed to be e.g. Alias, but what was recorded was completely something else. Other problems with auto timers was that I got a bunch of identical timers, and if I did not clean up my timers on regular basis, I got the many programs recorded multiple times. If someone has any suggestions for a vdradmin-replacement, then they are welcome :-) Regards, René

7 16

[ANNOUNCE] Remote Control Plugin 0.3.5
by Oliver Endriss 25 Jan '06

25 Jan '06

Hi, there is a bug fix release for the Remote Control plugin. History: -------- 2006-01-25: Version 0.3.5 - Fixed segfault due to FileName == NULL in cTtyStatus::Recording() and cTtyStatus::Replaying() (thanks to Ronny Kornexl for reporting this one). Rewrote cTtyStatus::Recording() and cTtyStatus::Replaying(): Do not assume that Name and/or FileName have a particular format. 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 available at http://www.escape-edv.de/endriss/vdr/ --------------------------------------------------------

1 0

Ping Darren Salt: Suspend patch in Debian
by Tony Houghton 25 Jan '06

25 Jan '06

Even if the original authors won't accept the usefulness of the suspend feature, please could you consider adding Marko Makela's suspend patch to your Debian package. I found it applied OK manually to 1.3.39-1 despite some offsets. The suspend patch is useful to the point of being essential for us softdevice users. For use as a recording daemon and because it's difficult to start and stop VDR on demand on a headless box, I tend to have it running all the time, and without suspending it uses about 60% of my CPU cycles. -- TH * http://www.realh.co.uk

2 2

dxr3 plugin and Debian sid vdr package
by Richard Wall 24 Jan '06

24 Jan '06

I just noticed that there is now an uptodate vdr package in Debian sid, but is there an easy "Debian" way of compiling plugins for it. I specifically need the dxr3 plugin, but it doesn't seem to be available as a package. I found the command debianize-vdrplugin, but am not quite sure how to procede after running it. Can anyone give any hints on which files need editing in the ./debian folder? Thanks, -RichardW.

2 2

[PATCH] vdr-1.3.39 & crash bug in schedule
by Rolf Ahrenberg 24 Jan '06

24 Jan '06

Hi, here's a little patch to prevent crashing on Digita network, that uses 'NULL' in some event titles. Otherwise the new EPG search feature is neat. BR, -- rofa

3 8

Vdradmin channels compatibility problem
by Tony Houghton 24 Jan '06

24 Jan '06

I'm now using VDR 1.3.39-1 (Darren Salt's deb) and vdradmin-am-3.4.3rc with DVB-T in the UK (Freeview). I've still got the same annoying problem with vdradmin's channel configuration that I've had for ages. Generally, when I try to add channels to the menus in vdradmin's Configuration page, they won't appear, seemingly at random. Later on some of them do; I think this may be caused by VDR doing an EPG scan. When I raised this complaint once before, one of the authors commented something about, "Perhaps we shouldn't filter out channels [something or other]". So I had a look at the code and saw that it was skipping channels without EPG data. I removed that check, but it didn't help much because it wouldn't show any data for those channels. Now that I've got softdevice running again instead of running VDR as a recording daemon with no output, I just did an experiment. In VDR I viewed the schedule for one of the channels vdradmin refused to display. When I looked again in vdradmin that channel had become available. -- TH * http://www.realh.co.uk

1 0

RE: [vdr] Vdradmin
by christian jacobsen 24 Jan '06

24 Jan '06

Hallo, > I'm trying to find some replacement for vdradmin that would be a bit > more reliable than the am-versions, and newer than the > original vdradmin > 1.96. The 1.96 has so far been working best with the auto timers if > compared with the am-versions of vdradmin. The biggest > problem with the > am-versions of vdradmin was that I got recordings that claimed to be > e.g. Alias, but what was recorded was completely something else. Other > problems with auto timers was that I got a bunch of identical timers, > and if I did not clean up my timers on regular basis, I got the many > programs recorded multiple times. > > If someone has any suggestions for a vdradmin-replacement, > then they are > welcome :-) You could also try the epgsearch plugin. It has the ability to create "searchtimer" which again program Timers. You can configure a lot there - and everything from within VDR :) As far as I can see it has almost everything what Master-Timer has got. It has no blacklist, but that is on the todo list. But if you want a webinterface it is not the right thing for you. Greetings Christian Jacobsen

1 0

vdr-1.3.37+ doesn't start with new runvdr
by Christoph Hermanns 23 Jan '06

23 Jan '06

Hi list, since i've updated to vdr-1.3.37 i hava a problem starting plugins with a command line option in runvdr like this: ... VDRUSR=root DVBDIR="/usr/local/src/DVB/driver" VDRPRG="/usr/local/src/VDR/vdr" VDRCMD="$VDRPRG -u $VDRUSR -w 60 -t /dev/tty8 -L /usr/local/src/VDR/PLUGINS/lib -c /usr/local/vdr/etc $* \ -s /usr/local/bin/vdrshutdown \ -P 'osdteletext -r' \ -P 'osdimage --directory /video/screenshots' " ... while (true) do $VDRCMD ... vdr doesn't start with this runvdr. Plugins without single quotation '' e.g. -P osdteletext work here. Changing the start command in the while-loop from $VDRCMD into the old su $VDRUSR -c "$VDRCMD" like ... while (true) do su $VDRUSR -c "$VDRCMD" ... and all plugins work as before including the command line options in single quota. - Has someone tested a plugin with command line options with the new runvdr from 1.3.37+ ??? - Or is this a rights problem ? Regards, Christoph

2 1

Patch: try to reconnect to lircd
by Ville Skyttä 23 Jan '06

23 Jan '06

Here's a patch that makes VDR try to reconnect to lircd if the connection is lost (eg. due to lircd restart on package upgrade, or whatever). The delay could be longer than the default of 3 seconds in this patch, no strong opinions on that. It would be cool to periodically try it also if the lircd connection is not available when starting VDR, but I think that's less often needed.

1 0

RE: [vdr] [Announce] LNB-sharing patch for VDR 1.3.38
by christian jacobsen 23 Jan '06

23 Jan '06

Hallo Matthias, > A new release of the configurable LNB-sharing patch for VDR 1.3 is > available at: > http://xn--ltzke-jua.de/dvb/VDR_LNB_sharing_patch/configurable > LNBshare-VDR_1.3.38.patch > > Changes: > - adapted to VDR 1.3.38 > > For general information about the LNB-sharing patch have a look at: > http://xn--ltzke-jua.de/dvb/VDR_LNB_sharing_patch/Description.txt > http://www.vdr-wiki.de/wiki/index.php/Lnbsharing-patch (german) Just wanted to say Thanks for this very nice patch :) Works very fine here since mid-december with the folowing cards : DVB-s rev. 1.6 4MB as primary DVB-s rev. 1.3 as secondary Nova-s as third card. The second and third card are sharing the same cable to the switch. Using the sat-out of the rev. 1.3 did not work, but an axis sat-splitter did the trick :) Greetings Christian Jacobsen

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
21
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr January 2006