From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: A version of Speakup... for your cell phone?
Date: Wed, 4 Oct 2006 18:16:11 -0700 [thread overview]
Message-ID: <20061005011611.GB12950@localhost.localdomain> (raw)
In-Reply-To: <4e70cccad0jsd@clara.co.uk>
-----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@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@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFJFzb7s9z/XlyUyARAk6uAKCgCM7LlmlZ8RHZEdw/ZvlT4+TTXACeL/wl
EQ2mVsgW2wYAMjVvCUndcbg=
=kci3
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
James Homuth
` Gregory Nowak
` Jonathan Duddington
` Gregory Nowak
` Marc Mulcahy
` Glenn at home
` Kirk Reiser
` Gregory Nowak
` Michael Whapples
` Jonathan Duddington
` Gregory Nowak [this message]
` Luke Davis
` Jonathan Duddington
` ace
` Gregory Nowak
` Sean McMahon
` Luke Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061005011611.GB12950@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).