From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eastrmmtao102.cox.net ([68.230.240.8]) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1HsjrF-0005WW-00 for ; Mon, 28 May 2007 14:22:17 -0400 Received: from eastrmimpo01.cox.net ([68.1.16.119]) by eastrmmtao102.cox.net (InterMail vM.7.05.02.00 201-2174-114-20060621) with ESMTP id <20070528182147.CYLU21965.eastrmmtao102.cox.net@eastrmimpo01.cox.net> for ; Mon, 28 May 2007 14:21:47 -0400 Received: from bonus-eruptus ([72.198.87.190]) by eastrmimpo01.cox.net with bizsmtp id 4iMm1X00D46QN3s0000000; Mon, 28 May 2007 14:21:46 -0400 From: cmbrannon@cox.net (C.M. Brannon) To: "Speakup is a screen review system for Linux." Subject: Re: spelling was Re: GRML swspeak? References: <000201c7a081$1e5d3a00$17b2a8c0@oemcomputer> <002101c7a088$612b90f0$6405a8c0@ALBERTLC7SN0ZA> <87bqg6rs6n.fsf_-_@cox.net> <2007-05-27T23-24-26@devnull.michael-prokop.at> Date: Mon, 28 May 2007 13:16:01 -0500 In-Reply-To: <2007-05-27T23-24-26@devnull.michael-prokop.at> (Michael Prokop's message of "Sun, 27 May 2007 23:29:23 +0200") Message-ID: <873b1gstjy.fsf@cox.net> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.9 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2007 18:22:18 -0000 Michael Prokop writes: > * C.M. Brannon wrote: > >> There's a very easy fix for this: >> renice 3 `ps -e |grep speechd-up |head -1 |cut -d' ' -f1` > [...] > > Are we talking about the same grml version? > grml 1.0 automatically does a 'nice -n -20 speechd-up' when invoking > swspeak. Does not that fix your issue? Hi Mika, I'm using the latest and greatest, version 1.0. I have better success when speechd-up has a positive (low) priority, rather than a negative one. I think this is because a low priority process makes fewer reads to /dev/softsynth, so it is more likely to read words, rather than single characters. You can actually view this with a packet capture tool, reading incoming messages on port 6560 (used by speech-dispatcher). When speechd-up runs with priority <= 0, I see a speak message generated and sent to speech-dispatcher for every character in a word, but when it runs with priority > 0, it usually sends a speak message to dispatcher containing a whole word or line of text. I really don't have an explanation for this, especially considering that other people are not encountering the same behavior that I am! I think the solution lies in modifying the speechd-up sources to use a different buffering strategy, rather than recompiling kernels and changing process priorities... -- Chris