From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fed1rmmtao11.cox.net ([68.230.241.28]) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1BM7ZI-00051j-00 for ; Fri, 07 May 2004 11:47:20 -0400 Received: from lnx1.holmesgrown.com ([68.99.198.226]) by fed1rmmtao11.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20040507154644.NEQT19283.fed1rmmtao11.cox.net@lnx1.holmesgrown.com> for ; Fri, 7 May 2004 11:46:45 -0400 Received: from lnx3.holmesgrown.com ([192.168.1.5] ident=mail) by lnx1.holmesgrown.com with esmtp (Exim 4.20) id 1BM7Yh-0000dg-Q8 for speakup@braille.uwo.ca; Fri, 07 May 2004 08:46:43 -0700 Received: from steve by lnx3.holmesgrown.com with local (Exim 4.20) id 1BM7Yk-0001Ij-Ns for speakup@braille.uwo.ca; Fri, 07 May 2004 08:46:46 -0700 Date: Fri, 7 May 2004 08:46:46 -0700 From: Steve Holmes To: speakup@braille.uwo.ca Message-ID: <20040507154643.GE422@lnx3.holmesgrown.com> Mail-Followup-To: speakup@braille.uwo.ca References: <20040506145902.GA1496@volny.cz> <20040506181219.GA27689@lnx3.holmesgrown.com> <20040506224433.GB1330@volny.cz> <20040507055741.GA29004@lnx3.holmesgrown.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <20040507055741.GA29004@lnx3.holmesgrown.com> User-Agent: Mutt/1.5.6i Sender: "Steve Holmes,,," Subject: Re: Flite and different voices X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.4 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: Fri, 07 May 2004 15:47:20 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, I tried the suggested coding changes to include 16 bit voices and I got the same unresolved references at link time that Chuck reported recently. Now I started digging around in flite.c in the src/modules directory and found two other code references containing 'kal' so I changed them to kal16 but I still got the same unresolved errors. I then looked more in the flite source to see if I could find anything and I came across an interesting file in the cmu_us_kal16 directory. It is called voxdefs.h. In there, it mentions kal but not kal16 for the defined register functions. So I went back into speech-dispatcher's source and changed flite.c back to 'kal' all around and looked at the Makefile in the modules directory. It linked to -lcmu_us_kal so I changed it to -lcum_us_kal16. You see, flite builds complete static and shared libraries for each voice it compiles. Alas, after doing all that, I still get the shitty 8-bit voice! I've run out of ideas at the moment. - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAm69iWSjv55S0LfERAuk8AKC0jDx552f0o7mHtY70CGn0NYRyIwCgrRTM 7uuOIJ2MgFHt0l5zovpF1VE= =f9h4 -----END PGP SIGNATURE-----