From: Gregory Nowak <greg@romuald.net.eu.org>
To: speakup@braille.uwo.ca
Subject: Re: reading the full screen
Date: Thu, 25 Oct 2007 11:43:06 -0700 [thread overview]
Message-ID: <20071025184306.GA29010@localhost.localdomain> (raw)
In-Reply-To: <20071025174354.GF21584@opera.rednote.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Well, I haven't been playing audio so far while trying to read the
screen with the bns at the same time yet in the vm. In fact, I didn't
mention that with bns being selected as the default synth, it does get
detected when speakup probes for it, even if the bns is turned off and
unpluged. Again, I haven't seen that happen outside of a vbox vm
either.
Greg
On Thu, Oct 25, 2007 at 01:43:54PM -0400, Frank Carmickle wrote:
> More at issue here is most likely the scheduler. I am sure that all of us know very well the trouble one can get in to when running audio on the same system that speakup is running on. Just listen to an ogg file while listening to screen fulls of stuff. The other way arround is also true. If you use a softsynth like ttsynth, even with a small bit of code like spk-connect-ttsynth and you run a bunch of system tasks your synth gets interupted. I do some silly tricks with renice to help this but it only goes so far. The fact of the matter is that speakup is not scheduled like other tasks in the kernel. It runs and when it is done it lets the rest of the system run. This actually opens a large can o worms. I suppose that one of the reasons why we like speakup so much is that we like that we can see the screen when we want to see the screen. Meaning that speakup in a really nasty way preempts everything. I have excepted this as it is for the time being. My solution for it is to run speakup on one machine and log in to other machines from their. Most of us these days are able to find old slow machines that people don't want any more and do this. I do hope that some day speakup does become a kernel thread and then we can run it on all of our machines.
>
> --Frank
>
> _______________________________________________
> 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.6 (GNU/Linux)
iD8DBQFHIOO67s9z/XlyUyARAvkbAKCBiDd5tNsB5L4S5V2VybfchVEzvgCeM9Kc
YeFCXob42DBX3KW9C4Ve+5M=
=H/pw
-----END PGP SIGNATURE-----
prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak
` Gaijin
` Gregory Nowak
` Kirk Reiser
` Gregory Nowak
` Frank Carmickle
` Gregory Nowak [this message]
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=20071025184306.GA29010@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).