From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.surferie.net ([63.175.116.33]) by speech.braille.uwo.ca with esmtp (Exim 3.35 #1 (Debian)) id 19GO19-0008UK-00 for ; Thu, 15 May 2003 15:03:51 -0400 Received: from localhost.localdomain [205.162.139.118] by mail.surferie.net with ESMTP (SMTPD32-6.06) id A37D6FC80052; Thu, 15 May 2003 14:59:09 -0400 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id h4FJ3ZbN004186 for ; Thu, 15 May 2003 15:03:35 -0400 Received: (from jacobs@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id h4FJ3YZk004184 for speakup@braille.uwo.ca; Thu, 15 May 2003 15:03:34 -0400 Date: Thu, 15 May 2003 15:03:34 -0400 From: jacobs@surferie.net To: speakup@braille.uwo.ca Subject: Re: dectalk express bug in cvs speakup? Message-ID: <20030515190334.GA4094@localhost.localdomain> References: <20030515041805.GA4375@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: Hi Kirk Logically then, what you're saying is that 100 should be dectalk's highest pitch if that is the range. However, it is not. I do see how rate was handled, but pitch seems to keep the dectalk-specific values. Therefore, pitch 100 is actually pitch 100 on the dectalk. After changing the pitch range my /proc/speakup stuff, including pitch, still works. As for the rate, it is locked in 0 to 18, not 0 to 100. I don't have a problem with starting at 0, but how can 18 values cover 500 different rates? On Thu, May 15, 2003 at 06:14:15AM -0400, Kirk Reiser wrote: > The rate is only relatively locked between 0-100. That covers the > entire range. All values to all settings except punctuation are > 0-... ranges for consistancy. If you change it in the driver it won't > work correctly when you modify it via the /proc/ file system entries.