[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [nas] 'elementRate == 0! Forcing to 5000' message is back...



On Thu, Feb 19, 2009 at 11:23 AM, Steve McIntyre <steve@xxxxxxxxxx> wrote:
On Thu, Feb 19, 2009 at 11:04:03AM -0600, hugo vanwoerkom wrote:
>Hi,
>
>I just did a dist-upgrade on Debian Sid and
>nas 1.9.1-4
>got replaced by
>nas 1.9.1-5
>and the syslog message 'elementRate == 0! Forcing to 5000' message is
>back...
>
>Did that fix get dropped by Debian?

Nope, the only changes I made between -4 and -5 were translations of
Debconf templates. No code changes.

--
Steve McIntyre, Cambridge, UK.                                steve@xxxxxxxxxx
"Because heaters aren't purple!" -- Catherine Pitt


Then upstream never incorporated the change. Could we do that please?
This refers to a patch to eliminate subject message that was sent me July 21, 2008. I attach it.
Let me know if I should report a bug.
Thanks.

Hugo Vanwoerkom
Index: server/dia/auprocess.c
===================================================================
--- server/dia/auprocess.c	(revision 273)
+++ server/dia/auprocess.c	(working copy)
@@ -30,6 +30,8 @@
 #include <audio/Aproto.h>
 #include "au.h"
 
+#include "nasconf.h"
+
 AuInt32 auMinibufSamples;
 AuUint32 auPhysicalOutputBuffersSize;
 AuUint8 *auPhysicalOutputBuffers;
@@ -1100,8 +1102,9 @@
 
     /* sanity - 6/20/2004, for bug report by Tobias Diedrich */
     if (!elementRate) {
-        osLogMsg("doSetup: elementRate == 0! Forcing to %d\n",
-                 auSetup.minSampleRate);
+        if (NasConfig.DoDebug > 10)
+            osLogMsg("doSetup: elementRate == 0! Forcing to %d\n",
+                     auSetup.minSampleRate);
         elementRate = auSetup.minSampleRate;
     }