Hi Gene,
To confirm, the only place I was experiencing a crash of any sort is at the
close of the Audacity program.
Concerning screen readers, if NVDA keeps moving forward and progressing as it
has been, I’m all for donating whatever I can to keep things going. Programs
like Jaws are expensive to say the least for what things the Jaws program is
still not accessing correctly. I don’t want to be nit-picky about Jaws since
Jaws is a wonderful program that has given us
Good accessibility for many years. I. E. the setup screens in Netflix for
example. NVDA has no problem accessing that page at all.
John
From: audacity4blind-bounce@xxxxxxxxxxxxx
[mailto:audacity4blind-bounce@xxxxxxxxxxxxx] On Behalf Of Gene
Sent: Wednesday, July 19, 2017 8:38 AM
To: audacity4blind@xxxxxxxxxxxxx
Subject: [audacity4blind] Re: Audacity has stopped working...
In that case, I hope Windows doesn't keep trying to update itself
automatically.
it would be interesting to know, and good to confirm whether the person who
raised the problem yesterday is having a more general crashing problem or just
crashing on exit.
The person said it's time to learn NVDA in earnest, though those weren't his
words. NVDA isn't hard to learn, switching or learning another screen-reader
isn't difficult because, unless you use specific features such as screen
review, most of what you are doing is using program or Windows commands and not
much changes from screen-reader to screen-reader except for interface commands
such as read current line, read to end, and those kinds of commands. There are
things to learn and NVDA has a page on its web site for JAWS users who want to
learn NVDA. I don't know how you use your computer but if NVDA meets your
needs well, as it does a lot of users, you may decide not to keep paying for
JAWS and switch to NVDA for general use while using your current version of
JAWS if it does this or that better.
Also, there are a lot of voices, free and those you pay for, including
Eloquence, if you don't like the built-in synthesizer, and a lot of people
don't.
Gene
----- Original Message -----
From: Ted Galanos <mailto:tr.galanos@xxxxxxxxx>
Sent: Wednesday, July 19, 2017 10:05 AM
To: audacity4blind@xxxxxxxxxxxxx <mailto:audacity4blind@xxxxxxxxxxxxx>
Subject: [audacity4blind] Re: Audacity has stopped working...
I'll continue my thread this morning from this post to answer
something Gene asked yesterday. I do know about sticky-key. Jaws has
in its settings an Insert mode that makes the Jaws key a sticky key.
There is an add on that Rich De Steno found for me to use, making the
NVDA key stick, but it is not streamline. It is a work-around that is
quite cumbersome. Also, I do not use a conventional keyboard. I use a
device whereby I type using two buttons that send morse code and the
device translates it into ascii text.
Teddy
On 7/19/17, Robert Hänggi <aarjay.robert@xxxxxxxxx
<mailto:aarjay.robert@xxxxxxxxx> > wrote:
On 19/07/2017, Andrew Downie <access_tech@xxxxxxxxxxxxxx
<mailto:access_tech@xxxxxxxxxxxxxx> > wrote:
I am using Audacity 2.1.3 on two machines running Windows 10 Creators
with NVDA. I had one hiccough when impatiently saving a file.
Fortunately, Audacity's excellent crash recovery retrieved the file.
Otherwise, all has been boringly stable - the way we like it.
Activate Narrator with Windows-Enter. If that does not work, try
control-Windows-Enter which, strangely, is the deal on my Asus notebook.
Microsoft has changed the key combination for the creator's edition.
Unfortunately, almost all help pages do still list "Windows+Enter"
instead of "Control+Windows+Enter".
In summary: it is a quick check to see if your machine has been updated...
;-)
Robert
Andrew
On 19/07/2017 6:10 AM, David Engebretson Jr. wrote:
Well, if a JAWS script is causing the trouble (it appears jhook.dll is
sending too many onPaint messages) and WinAmp uses scripts then it is
likely the problem is the same.
How does one invoke Narrator nowadays?
Peace,
David
*From:*audacity4blind-bounce@xxxxxxxxxxxxx
[mailto:audacity4blind-bounce@xxxxxxxxxxxxx] *On Behalf Of *Gene
*Sent:* Tuesday, July 18, 2017 1:05 PM
*To:* audacity4blind@xxxxxxxxxxxxx <mailto:audacity4blind@xxxxxxxxxxxxx>
*Subject:* [audacity4blind] Re: Audacity has stopped working...
I doubt the problem is the same. As I understand the problem
discussed earlier, Audacity, when used with JAWS in the most recent
full Windows update would crash when being used. The current problem
appears to be crashing on exit, which is of no practical significance
as long as you save your work before closing the program.
Gene
----- Original Message -----
*From:*Ted Galanos <mailto:tr.galanos@xxxxxxxxx>
*Sent:*Tuesday, July 18, 2017 2:07 PM
*To:*audacity4blind@xxxxxxxxxxxxx <mailto:audacity4blind@xxxxxxxxxxxxx>
*Subject:*[audacity4blind] Re: Audacity has stopped working...
I was getting this message with both Audacity and Winamp back in April
when I upgrated to Creator's Edition. I rolled back Windows and am
reluctant to upgrade again for fear of having the same trouble.
Teddy
On 7/18/17, Johchi <johchi@xxxxxxxxxx <mailto:johchi@xxxxxxxxxx>
<mailto:johchi@xxxxxxxxxx>> wrote:
Hi everyone,well at
Well I installed Audacity for Windows 10 and the installation went
that. But I didn't do anything in the program at all. So I went to theAudacity has
"file" menu and hit exit. Then I got a message saying that
stopped working and Windows will look to see if it sees a fix for thenow. Do I
problem - or something like that.This has happened several times
need to uninstall Audacity and re-install it in order to fix theproblem?
Thanks,
John
--
Teddy
The audacity4blind web site is at
//www.freelists.org/webpage/audacity4blind
Subscribe and unsubscribe information, message archives,
Audacity keyboard commands, and more...
To unsubscribe from audacity4blind, send an email to
audacity4blind-request@xxxxxxxxxxxxx
<mailto:audacity4blind-request@xxxxxxxxxxxxx>
<mailto:audacity4blind-request@xxxxxxxxxxxxx>
with subject line
unsubscribe
The audacity4blind web site is at
//www.freelists.org/webpage/audacity4blind
Subscribe and unsubscribe information, message archives,
Audacity keyboard commands, and more...
To unsubscribe from audacity4blind, send an email to
audacity4blind-request@xxxxxxxxxxxxx
<mailto:audacity4blind-request@xxxxxxxxxxxxx>
with subject line
unsubscribe
