Re: Field names and field data was GoldWave not speakingstatusinformation

[Christopher Wright]

The commands for selecting and copying audio are application commands, not 
screen reading commands.
----- Original Message ----- 
From: "JM Casey" <crystallo...@ca.inter.net>
To: "PC Audio Discussion List" <pc-audio@pc-audio.org>
Sent: Saturday, December 31, 2011 4:23 PM
Subject: Re: Field names and field data was GoldWave not 
speakingstatusinformation


Hi Dave.

Thanks for all this.  yes, you're right...GW definitely has done more than 
any other sound editor to make their programme work well for those of us 
who don't use the screen.

I think you're mostly right with all this stuff. What I'm going to do 
later on is see if I can revert to 5.57, which is the last version I 
remember using that gave a lot of voice feedback and seemed well 
integrated with the scripts. I'll uninstall the scripts so I can see 
exactly how much help they were giving us. The person who created the 
scripts put in a lot of keyboard commands to read status information. For 
example:
To read the selected channel press Alt+Shift+C.
To say the name of the open sound file press alt+shift+o.
To say the open file's format press alt+shift+i.
To report which GoldWave control is active press alt+shift+a.
To say the total playing time of a sound file press Alt+Shift+T.
To say the elapsed time while playing press Alt+shift+e.
To say the time location of the start marker press alt+Shift+s.
To say the time of the finish marker press alt+shift+f.
To say the duration of the selection press Alt+Shift+D.
To say the current zoom level, Press Alt+Shift+Z

Needless to say some of this was pretty useful. I seem to remember certain 
cases where start and finish marker positions were spoken automatically. 
As mentioned, the name of the current file is no longer even read when you 
first move focus to Golwave, or switch from one file to another. Copying 
and pasting of course does actually work, but jaws seems to believe that 
there is nothing on the clipboard and so, consequentially, nothing to 
paste.

Seems that the programme may work better with Window Eyes. I was going to 
ask you how you'd been making out, since you seem to have had considerable 
success with the latest versions, but forgot that you were using W. Eyes. 
I of course have heard that Window Eyes doesn't require as much scripting 
and addictional tweaking as JAWS sometimes does in order to work most 
efficiently with certain programmes.


----- Original Message ---
--
From: "Dave bahr" <dcba...@gmail.com>
To: "PC Audio Discussion List" <pc-audio@pc-audio.org>
Sent: Saturday, December 31, 2011 2:27 PM
Subject: Field names and field data was GoldWave not speaking 
statusinformation


I've alerted Chris, the developer, to the issue of headings not being 
spoken, or that's what I'm calling them, I mean the field name, really. 
But it seems as if the field data isn't being spoken either for jaws 
users? I have the same issue at times with the marker setting dialogue as 
a window-eyes user; sometimes the start and end markers don't read and I 
have to copy the line to a notepad file. That's been happening less and 
less, but I am curious to know if it's a cross-screen reader phinominon. 
So, this is an appeal for both jfw and we users to please let me know if 
they've had the same problem. Just because I think i've confused myself 
I'm going to rehash this in a numbered order. Bear with me please. The 
following are the things I am understanding are not being read by gw at 
this time, or at least not being read consistantly.

1. the data within fields, primarily edit boxes in the time marker 
dialogue for me,
2. the status? of information in these edit boxes or relating to the 
buttons not speaking properly in the jaws scripts, do I have that sort of 
right?
3. The indication of the data to be put into a combo or edit box. I am 
noticing this with the tone meter dialogue where I see a combo box with 
numbers in it but I'm not sure what they signify unless I use the mouse 
keys. It is faster to tab through the dialogues, but I'm not sure how to 
fix this in window-eyes. I am going to post to the gwmicro-info list to 
see if people have suggestions for this one so I can explain it to the 
developer of goldwave.

Feel free to correct me on any of this, and even tell me if I'm flatout 
wrong. I just want to help make this program the most accessible sound 
editor out there because it has been on that path for some time now. This 
Chris guy also seems to have his heart in the right place as far as 
listening to suggestions from me about accessability. And I don't have to 
be the only mediator either, it would be nice to have more people email 
him on the accessability front.

apologies for the longwinded message, but I wanted to spell out what I 
thought were the primary concerns. I'd rather give too much info than not 
enough.

Dave C. Bahr

On 12/31/2011 2:21 AM, JM Casey wrote:
Hey Dave.

As far as I know much of this functionality was due more or less
directly to the scripts. Maybe I am wrong? It seems to me that
GoldWave's developers have done a pretty ace job of making their
software screenreader-friendly up until now. However certain elements
like the reading of time intervalss, filenames, selection areas, etc,
simply don't speak anymore. If I can grab GW 5.57 and test it without
scripts, I will do so.

But it seems that some blind users are having success with this? Are
they simply used to not having this information read for them, though it
would seem fairly essential and necessary? I don't know. I'm cerrtainly
curious about other Jaws users' experiences here.


----- Original Message ----- From: "Dave bahr" <dcba...@gmail.com>
To: "PC Audio Discussion List" <pc-audio@pc-audio.org>
Sent: Friday, December 30, 2011 10:08 PM
Subject: Re: GoldWave not speaking status information


so we're talking about the edit boxes for the time selection in
setting the markers? I don't have the jfw scripts but I do know that
I've had problems with those boxes not being spoken, but that's been
since 5.25 I think. I'd like to send your comment to the developer but
he wouldn't be familiar with the jfw scripts, so can someone who has
the scripts please test it without the scripts and let me/the list
know what they found not to be speaking? Perhaps something did get
changed in the syntax of the program that none of us know about.


Dave C. Bahr

On 12/29/2011 9:56 PM, kim kelly wrote:
You are right; I will look at the manual.
GW. is the best software out there.

Kim McNatt-Kelly
Alternate email:

kim...@samobile.net

Skype:

richies12

Anyone who wants to get a hold of Richie My Other half, email him at:

richandconch...@samobile.net

Or:
webpol...@centurylink.net

We enjoy communicating with anyone who would like to and who needs 
help
with computers and blindness related issues.

Merry Christmas and Happy New Year.


----- Original Message ----- From: "JM Casey"
<crystallo...@ca.inter.net>
To: "PC Audio Discussion List" <pc-audio@pc-audio.org>
Sent: Thursday, December 29, 2011 2:02 PM
Subject: Re: GoldWave not speaking status information


Hey again everyone.

The programme itself is probably not to blame; it seems to me they've
gone above and beyond to make the software accessible. However, we
simply got used to the functionality of the scripts. If nobody's
around to update them anymore and the layout changes, there goes that
functionality. Perhaps someone else can take over? It seems to me 
that
whatever modifications are needed ought to be pretty simple, but I
lack the requisite knowledge myself (always the excuse isn't it?)

I should add that there's still some voice feedback....record, play
etc buttons still speak and the active control read command works
along with some of the others not native to GW (at least I don't 
think
they are). Just seems that any keystroke to do with time selection or
file information no longer reads the required information.

JM

----- Original Message ----- From: "kim kelly" 
<kim...@centurylink.net>
To: "PC Audio Discussion List" <pc-audio@pc-audio.org>
Sent: Thursday, December 29, 2011 3:50 PM
Subject: Re: GoldWave not speaking status information


I am having trouble too.
What do we do?

I'm getting dissapointed I purchased my licens, and I will be mad if
we can't use it.

Kim McNatt-Kelly
Alternate email:

kim...@samobile.net

Skype:

richies12

Anyone who wants to get a hold of Richie My Other half, email him 
at:

richandconch...@samobile.net

Or:
webpol...@centurylink.net

We enjoy communicating with anyone who would like to and who needs
help with computers and blindness related issues.

Merry Christmas and Happy New Year.


----- Original Message ----- From: "Tom Kaufman"
<tomca...@comcast.net>
To: "PC Audio Discussion List" <pc-audio@pc-audio.org>
Sent: Thursday, December 29, 2011 12:12 PM
Subject: Re: GoldWave not speaking status information


Hopefully Gold Wave isn't becoming something that is now
inaccessible as I know many people who like this particular 
program!
Tom Kaufman
----- Original Message ----- From: "Christopher Wright"
<chri...@bestweb.net>
To: "PC Audio Discussion List" <pc-audio@pc-audio.org>
Sent: Thursday, December 29, 2011 3:10 PM
Subject: Re: GoldWave not speaking status information


I experienced the same thing, except that I'm using Jaws 13. After
experiencing the problem you described, regarding selecting audio
and then copying that audio to the clipboard, I got the same
message you heard.

I ended up going back to Goldwave 5.58, which is what I had 
before.
----- Original Message ----- From: "JM Casey"
<crystallo...@ca.inter.net>
To: "PC Audio Discussion List" <pc-audio@pc-audio.org>
Sent: Thursday, December 29, 2011 2:20 PM
Subject: GoldWave not speaking status information


Hello everyone.

I recently obtained GoldWave 5.61. I'm definitely pleased with
what seem to be a bunch of new accessibility-related features,
though I haven't had a chance to try much yet. At any rate, I 
used
to get plenty of feedback messages from the programme, which 
would
speak the name of the file that was open if I, for example,
alt-tabbed over to the goldwave window, or used alt-f6 to switch
between files. I could also get JAWS to speak the name of the 
file
by hitting alt-shift-o, the file format, cursor position, 
markers,
etc. I noticed I was having some problems with the scripts, which
would seem to hang the programme whenever I hit insert-h or used
some other commands. So, I searched around and realised I wasn't
using the most up-to-date version. The laatest I found was 1.60.
Installed these, and I'm still getting very little voice 
feedback,
though there doesn't seem to be any more hanging issue. 
Everything
in the programme seems to work fine, but if I select a piece of
sound from
a file, and copy it to the clipboard, jaws will say "nothing
selected". This is simply untrue as I've tested and know for a
fact that a selection has happened, but for some reason JAWS
and/or scripts are just not tracking things correctly. None of 
the
information keys seem to work; I can't even get the time of the
current file, and using alt-shift-o to speak the current open
filename only results in the word "file" being read. I can see 
the
information is there on the screen using the jaws cursor, but I
don't want to have to do this every time. It's particularly
annoying when moving between files because I don't always know
which one is open. I've turned off visual metres, and all other
elements that I think might be getting in the way of proper
functionality. What's going on here? Has the layout with GoldWave
5.61 changed so much that JAWS simply can't find the relevant
information anymore to read? Can I adjust anything to make it
work? Do I have to regress back to GW 5.57
if I want my status read? I realise that the scripts are not
really essential but I got used to being able to quickly check
things like open file status, elapsed time, marker positions, 
etc,
and editing will take a whole lot longer and involve more
guesswork if I can't do this like I used to. I keep thinking I'm
missing some obvious setting. Any ideas at all? I'm using jaws 11
by the way, which worked fine with v5.57 and even the older
scripts.

Thanks.

JM
To unsubscribe from this list, send a blank email to:
pc-audio-unsubscr...@pc-audio.org



To unsubscribe from this list, send a blank email to:
pc-audio-unsubscr...@pc-audio.org


To unsubscribe from this list, send a blank email to:
pc-audio-unsubscr...@pc-audio.org


To unsubscribe from this list, send a blank email to:
pc-audio-unsubscr...@pc-audio.org


To unsubscribe from this list, send a blank email to:
pc-audio-unsubscr...@pc-audio.org


To unsubscribe from this list, send a blank email to:
pc-audio-unsubscr...@pc-audio.org

To unsubscribe from this list, send a blank email to:
pc-audio-unsubscr...@pc-audio.org


To unsubscribe from this list, send a blank email to:
pc-audio-unsubscr...@pc-audio.org

To unsubscribe from this list, send a blank email to:
pc-audio-unsubscr...@pc-audio.org


To unsubscribe from this list, send a blank email to:
pc-audio-unsubscr...@pc-audio.org



To unsubscribe from this list, send a blank email to:
pc-audio-unsubscr...@pc-audio.org