Re: [vdr] Problems with VDSB, how to automate in SYSLOG
Am 27.04.2013 14:06, schrieb Brian-Imap: > The single one at the start is what stops me activating the emergency > exit in VDR. Do you have an in-accurate system clock and/or clock syncing enabled? VDR will falsely trigger an VDSB if the clock is set more than 30 seconds ahead while a recording is running. If you set the clock by DVB time, I'd suggest restricting it to one channel only. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] RFC: one or many positioners?
On 22.04.2013 20:56, Lars Hanisch wrote:
Am 22.04.2013 14:28, schrieb Klaus Schmidinger:
...
or even
virtual void Drive(bool Left) {}// true = left, false = right
virtual void Step(int Steps) {} // <0 = left, >0 = right
virtual void SetLimit(bool Left) {} // true = left, false = right
?
If you would go this way, I would prefer an enum as parameter, because it's
easier to use and the code is easier to
understand. You don't have to remember if true is left or right. :)
"Step" would than have two parameters, the enum and an uint.
Well, I guess especially with the Step() function it could have been nice
to have the sign indicate the direction. But then again VDR itself probably
isn't going to use Step() with anything else but '1', so
enum ePositionerDirection { pdLeft, pdRight };
virtual void Step(ePositionerDirection Direction, uint NumSteps = 1);
should do just fine...
Klaus
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] RFC: one or many positioners?
On 23.04.2013 13:34, Ales Jurik wrote: On 04/23/2013 01:08 PM, Klaus Schmidinger wrote: ... I'm also thinking of allowing something in the form of * 11700 V 9750 t V W15 [E0 10 38 F0] W15 P * 9 V 10600 t V W15 [E0 10 38 F1] W15 P * 11700 H 9750 t V W15 [E0 10 38 F2] W15 P * 9 H 10600 t V W15 [E0 10 38 F3] W15 P (note the '*' instead of, e.g., 'S19.2E'), which could be a shortcut for a (USALS) positioner that could receive any satellite (as long as it's above the horizon). Klaus Hi Klaus, please could it be possible to have functionality of diseqc.conf which allows simple combining of fixed LNB's and motorized dish, so the will it be possible to have in diseqc.conf standard entries like S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W15 A W15 t S19.2E 9 V 10600 t v W15 [E0 10 38 F1] W15 A W15 T S19.2E 11700 H 9750 t V W15 [E0 10 38 F2] W15 A W15 t S19.2E 9 H 10600 t V W15 [E0 10 38 F3] W15 A W15 T followed with the new syntax one * 11700 V 9750 t V W15 [E0 10 38 FC] W15 P * 9 V 10600 t V W15 [E0 10 38 FD] W15 P * 11700 H 9750 t V W15 [E0 10 38 FE] W15 P * 9 H 10600 t V W15 [E0 10 38 FF] W15 P and the standard entries will be prioritized? This will allow to use fixed LNB's as preferable ones in combined diseqc installation. I'm planning to do it that way. Of course with chance of source choosing (if more than one tuner is used). I don't understand what you mean here. My second wish is to have possibility to use the new syntax on all tuners available, so only gotoxx command will be send to the/all tuner, to allow simple cooperation with intelligent vtuner devices like NessieDVB. I'm afraid I don't understand this, either. Can you be more specific? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problems with VDSB, how to automate in SYSLOG
On 27.04.2013 12:36, Udo Richter wrote: Am 27.04.2013 10:50, schrieb Brian-Imap: Hi, on some channels I get Video Data Stream Broken messages, not sure quite what triggers them yet. VDSB is triggered if a recording doesn't receive any video data within 30 seconds. Usually this is because either the channel doesn't exist / doesn't broadcast, or because the DVB hardware failed and stopped working. If you disable emergency exit, VDR will likely continue to see no data, so forget about that recording. I know I could extend the VDR start script to unload/load the DVB drivers after a VDR exit too. This is the only thing that might cure a VDSB, and the only reason to do an emergency exit at all. Its quite unlikely that restarting VDR without reloading drivers will make any difference. (though not impossible, I've seen strange crosstalk effects in the past, and VDR doing something completely different after restart sometimes helped.) Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Moin, strange, here are some example messages that I send myself per email: VDR-Test-Cellar(SDA2): 01:43 VDSB VDR-Test-Cellar(SDA2): 01:43 VDSB VDR-Test-Cellar(SDA2): 01:42 VDSB VDR-Test-Cellar(SDA2): 01:41 VDSB VDR-Test-Cellar(SDA2): 01:41 Start 2013-04-27 01.41 Friday Night Dinner VDR-Test-Cellar(SDA2): 01:30 Stop 2013-04-27 00.01 Later... with Jools Holland VDR-Test-Cellar(SDA2): 01:26 Start 2013-04-27 01.26 Bluestone 42 VDR-Test-Cellar(SDA2): 00:01 Start 2013-04-27 00.01 Later... with Jools Holland VDR-Test-Cellar(SDA2): 23:50 Stop 2013-04-26 22.59 QI VDR-Test-Cellar(SDA2): 23:20 Stop 2013-04-26 21.56 Ben Earl VDR-Test-Cellar(SDA2): 23:20 Stop 2013-04-26 22.26 Have I Got News for You VDR-Test-Cellar(SDA2): 23:10 Stop 2013-04-26 21.58 The Genius of Turner#3A Painting the Ind VDR-Test-Cellar(SDA2): 22:59 Start 2013-04-26 22.59 QI VDR-Test-Cellar(SDA2): 22:26 Start 2013-04-26 22.26 Have I Got News for You VDR-Test-Cellar(SDA2): 21:58 Start 2013-04-26 21.58 The Genius of Turner#3A Painting the Ind VDR-Test-Cellar(SDA2): 21:56 Start 2013-04-26 21.56 Ben Earl VDR-Test-Cellar(SDA2): 21:55 VDSB VDR-Test-Cellar(SDA2): 18:38 Up VDR-Test-Cellar(SDA2): 07:40 Going down At 21:55 there is a single VDSB depsite the fact that no recording is running. Then all is OK till 01:41 that recording triggers the VDSB and they continue until the recording end time is reached. So its this continual repeated VDSB that I want to catch if possible. The single one at the start is what stops me activating the emergency exit in VDR. Cheers Brian ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problems with VDSB, how to automate in SYSLOG
Am 27.04.2013 10:50, schrieb Brian-Imap: > Hi, > on some channels I get Video Data Stream Broken messages, not sure quite > what triggers them yet. VDSB is triggered if a recording doesn't receive any video data within 30 seconds. Usually this is because either the channel doesn't exist / doesn't broadcast, or because the DVB hardware failed and stopped working. If you disable emergency exit, VDR will likely continue to see no data, so forget about that recording. > I know I could extend the VDR start script to unload/load the DVB > drivers after a VDR exit too. This is the only thing that might cure a VDSB, and the only reason to do an emergency exit at all. Its quite unlikely that restarting VDR without reloading drivers will make any difference. (though not impossible, I've seen strange crosstalk effects in the past, and VDR doing something completely different after restart sometimes helped.) Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] VDR Power Button Daemon 0.1.0
Hello, I tried to add all the suggestions, I got for vdrpbd 0.0.1 and created a new release. This one comes with a template for vdrpbd.conf and even has a man page to describe the settings (man vdrpbd.conf). Not it is also possible to customize the time range and the amount of keypresses for the emergency reboot feature (see vdrpbd.conf). Please tell me if you still miss something. Download here: http://projects.vdr-developer.org/attachments/download/1363/vdrpbd-0.1.0.tar.xz Yours Manuel ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Problems with VDSB, how to automate in SYSLOG
Hi, on some channels I get Video Data Stream Broken messages, not sure quite what triggers them yet. They continue till the recording has finished. I have switched off the emergency exit when VDSB occurs, two reasons why: 1. It never cures the problem 2. Occasionally I get a single VDSB written when tuning to certain channels, the emergency exit would happen, but after the restart I would get a single VDSB again when the channel was tuned, ending up in a loop, as the VDR restart is not curing the problem. So, I wanted to know if anyone has any code or rules for rsyslog to identify multiple VDSB messages so I could trigger other actions. For example a reboot of the PC or maybe a driver load/unload. I know I could extend the VDR start script to unload/load the DVB drivers after a VDR exit too. Anyone have other suggestions maybe? Cheers Brian ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
