Re: [vdr] ERROR: video data stream broken on second dvb card , but szap works (new findings!)

Hi, Dieter Bloms wrote: my primary dvb card works fine on both of my Twin-LNB connectors. I can switch the second card via szap and get a video stream via cat /dev/dvb/adapter1/dvr0 /tmp/bla on H and V channels. VDR doesn't get data any data from H channels, but gets data from V channels.

[vdr] Strange delay in recordings with vdr-xine

I recently (more on that below) started experiencing a strange problem with vdr 1.4.5-1 and vdr-xine 0.7.6+network patches: while replaying a recording (either against a local copy of vdr or over the network) the only command that acts immediately is pause, every other one (skip one minute,

Re: [vdr] Strange delay in recordings with vdr-xine

I have the same problem with xineliboutput (xvdr:tcp://). I don't remember when it all started but I don't think is related to xine. This is just a guess, but it may be related to the problem with recordings. When xine.. plugins worked OK I could record up to 5 channels in the same time. Now

[vdr] Capabilities

Hello, I've problems with my statusleds plugin. If vdr is not running as root all capabilities are dropped - except the one for setting the system time. My plugin wants to set the keyboard leds with the ioctl KDSETLED on /dev/console. Unfortunately this ioctl requires one more capability. Is

[vdr] RS-232 relay plugin adapted for the shutdown rewrite

On Sun, Jan 28, 2007 at 05:50:46PM +0100, Udo Richter wrote: Hi list, I've finished a third version of the shutdown rewrite. Again there are two patches available, one for VDR 1.5.0, and one with slight changes for 1.4.x. http://www.udo-richter.de/vdr/patches.html#shutdown

Re: [vdr] Capabilities

Bernd Juraschek wrote: Hello, I've problems with my statusleds plugin. If vdr is not running as root all capabilities are dropped - except the one for setting the system time. My plugin wants to set the keyboard leds with the ioctl KDSETLED on /dev/console. Unfortunately this ioctl

Re: [vdr] Capabilities

Why not simply document this fact in the installation guide: The plugin must have write access to /dev/console. This is similar to the dvd or vcd plugin which need read/write access to /dev/dvd resp. /dev/cdrom. Hmm - this sounds like a good idea ... On my machine, I added the vdr user to

Re: [vdr] Capabilities

Bernd Juraschek wrote: I don't know much about linux capabilities, but my feeling is, that they are meant for things not represented by devices (which use the simpler file-permissions model). On my system /dev/console has r/w access for anyone but this is not sufficient. Damn. so much

Re: [vdr] [RFC] Shutdown rewrite for 1.5.x, version 0.4

Hi list, I've finished a fourth version of the shutdown rewrite. Again there are two patches available, one for VDR 1.5.0, and one with slight changes for 1.4.x. http://www.udo-richter.de/vdr/patches.html#shutdown http://www.udo-richter.de/vdr/patches.en.html#shutdown Changes: - Renamed

[vdr] [ANNOUNCE] runvdr extreme 0.2

Hi list, I've updated the runvdr extreme script to version 0.2. runvdr extreme is a runvdr script, just like the runvdr script included in the VDR distribution. Additionally, it supports configuration files, lots of command line options and more features. -

Re: [vdr] FF card AV sync problems, possible fix to VDR (fwd)

Hi, Kartsa wrote: So I would like to raise this one up again. After applying the two changes (dsyslog(TS continuity error (%d), ccCounter) and { *FrameSize = 0; dsyslog(cAudioRepacker: FrameSize == 0); } in remux.c) I still get these lines in log (and -l 3 in vdr startup) vdr: [3600]