-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 My main concern was not espeak, since I know that has a small footprint, another thing that makes it a great software synth. I was thinking more in terms of the RAM used by speech-dispatcher/speechd-up, and festival for example, (which someone, somewhere might want to use instead of espeak for some weird reason). While by themselves speech-dispatcher and speechd-up might not seem like much, if you put that concern in the context of all the other applications that people run today on their PDA cell phones, every single k-byte counts. As I've stated in my previous post though, if you eliminate speech-dispatcher/speechd-up, and use something like espeak, it does seem doable. Greg On Thu, Oct 05, 2006 at 02:06:25AM +0100, Jonathan Duddington wrote: > I did a test on Linux, with the command: > speak -w test.wav -f longTextFile > > This showed the speak process's memory usage as: > VmSize: 3.4 MByte (total amount of virtual memory). > VmRss: 1.5 MByte (total amount of physical memory). > > I'm not sure why it's using virtual memory, but these figures seem > modest by today's standards. > > Using the portaudio interface increases the VmSize to 28 MByte. > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup - -- web site: http://www.romuald.net.eu.org gpg public key: http://www.romuald.net.eu.org/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) - -- Free domains: http://www.eu.org/ or mail dns-manager at EU.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFJFzb7s9z/XlyUyARAk6uAKCgCM7LlmlZ8RHZEdw/ZvlT4+TTXACeL/wl EQ2mVsgW2wYAMjVvCUndcbg= =kci3 -----END PGP SIGNATURE-----
