From patchwork Fri Apr  1 16:30:07 2005
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Patchwork-Submitter: Luca Olivetti <luca@ventoso.org>
X-Patchwork-Id: 11839
Received: from 232.red-213-97-27.pooles.rima-tde.net ([213.97.27.232])
	by www.linuxtv.org with esmtp (Exim 4.34) id 1DHP2V-00068v-49
	for vdr@linuxtv.org; Fri, 01 Apr 2005 18:30:31 +0200
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1])
	by 232.Red-213-97-27.pooles.rima-tde.net (Postfix) with ESMTP id
	5B03118A4513
	for <vdr@linuxtv.org>; Fri,  1 Apr 2005 18:30:14 +0200 (CEST)
Message-ID: <424D770F.1060102@ventoso.org>
Date: Fri, 01 Apr 2005 18:30:07 +0200
From: Luca Olivetti <luca@ventoso.org>
User-Agent: Mozilla Thunderbird 0.9 (X11/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Klaus Schmidinger's VDR <vdr@linuxtv.org>
Subject: Re: [vdr] Motorised dish tuning delays and vdr
References: <424D6712.7030108@iki.fi>
In-Reply-To: <424D6712.7030108@iki.fi>
X-Enigmail-Version: 0.89.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-BeenThere: vdr@linuxtv.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Klaus Schmidinger's VDR <vdr@linuxtv.org>
List-Id: Klaus Schmidinger's VDR <vdr.linuxtv.org>
List-Unsubscribe: <http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr>,
	<mailto:vdr-request@linuxtv.org?subject=unsubscribe>
List-Archive: <http://www.linuxtv.org/pipermail/vdr>
List-Post: <mailto:vdr@linuxtv.org>
List-Help: <mailto:vdr-request@linuxtv.org?subject=help>
List-Subscribe: <http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr>,
	<mailto:vdr-request@linuxtv.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2005 16:30:31 -0000
Status: O
X-Status: 
X-Keywords: 
X-UID: 1331

Seppo Ingalsuo wrote:
> Hi,
> 
> Have you seen problems in getting picture after first channel change 
> which requires dish movement?
> 
> I'm controlling motorized dish directly trough diseqc.conf without rotor 
> or actuator plugins. I didn't have problems with earlier VDR 1.3.x  
> versions. Since upgrading from linux 2.6.9 to 2.6.11 I have seen 
> occassionally similar problems even with DVB-T when new channel is on 
> different frequency (multiplexes A, B, C).
> 
> What is the corrent place to experiment with VDR tuning timeout values?

As a stop-gag measure, while core vdr is properly adapted to steerable 
dishes (Klaus, you promised it ;-), you can use the attached patch. What 
it does is explained at 
http://linuxtv.org/vdrwiki/index.php/Actuator-plugin#Patches

Bye

--- device.c.steerable	2005-01-09 18:09:19.996328466 +0100
+++ device.c	2005-01-09 18:10:10.572853731 +0100
@@ -1057,10 +1057,12 @@
      return false;
   if (Receiver->device == this)
      return true;
+  /*   
   if (!HasLock(TUNER_LOCK_TIMEOUT)) {
      esyslog("ERROR: device %d has no lock, can't attach receiver!", CardIndex() + 1);
      return false;
      }
+  */   
   cMutexLock MutexLock(&mutexReceiver);
   for (int i = 0; i < MAXRECEIVERS; i++) {
       if (!receiver[i]) {
--- recorder.c.steerable	2005-01-09 18:12:09.844359502 +0100
+++ recorder.c	2005-01-09 18:13:37.276606354 +0100
@@ -96,11 +96,14 @@
 void cFileWriter::Action(void)
 {
   time_t t = time(NULL);
+  time_t m = MAXBROKENTIMEOUT * 10;  //give more time to first packet
+   
   active = true;
   while (active) {
         int Count;
         uchar *p = remux->Get(Count, &pictureType);
         if (p) {
+           m = MAXBROKENTIMEOUT;
            //XXX+ active??? see old version (Busy)
            if (!active && pictureType == I_FRAME) // finish the recording before the next 'I' frame
               break;
@@ -118,7 +121,7 @@
               break;
            t = time(NULL);
            }
-        else if (time(NULL) - t > MAXBROKENTIMEOUT) {
+        else if (time(NULL) - t > m) {
            esyslog("ERROR: video data stream broken");
            cThread::EmergencyExit(true);
            t = time(NULL);