I have placed the JGauge sound file set on my web site as its own
thing. To read about it and/or download it, go to
http://www.dlee.org/gauge_sounds.htm
This can quickly be used to create an alternative set of sound files
for this project.
Note that a renfiles.bat file is included to provide a quick way to
rename the files. For Window-Eyes' ProgressBar scripts, you would run
renfiles gauge progress
then manually figure out what files to use for the two special
*default.wav files in the Window-Eyes sound file set.
The README file from the set follows.
This is a set of sounds for reporting progress bar status. I
originally created these sounds in 2003 for JAWS and an experimental
set of scripts I called JGauge. I am now making the sounds available
for any other project. For convenience, the file set also comes with
a batch file that can be used to change the basename of all sound
files in the set.
For the curious, the files were generated using an old Unix-based
command-line tool called augen. The Perl program that drives augen to
make the files, genwavs.pl, is included in this file set as well.
Sound and Theory:
Each of the 101 position files consists of three tones: A bottom border
tone of 220 Hz, a top border tone of 880 Hz, and a somewhat louder tone
between the two indicating the current position. The tones are triangle
waves, thus a bit clearer in pitch to the ear than sine waves yet less
obnoxious in headphones than square waves. The idea of having three
tones is to make the ear recognize the distance from current position
to one or both borders without requiring perfect pitch.
There are four additional sound files with special meanings:
gaugenew.wav is for indicating the arrival of a new progress bar and
consists of the two border tones plus a short and rapidly ascending
sweep sound. Similarly, gaugeexp.wav is to indicate the disappearance
of a progress bar and consists of the two border tones plus a rapidly
descending sweep.
gaugeobs.wav indicates an obscured but still present progress bar.
When MSAA is used to get progress bar values, this may not be
necessary. However, for special progress bars that don't report MSAA
and must be read via pixel examinations on screen, this can be used to
indicate when a bar is present but whose position can't be reliably
determined. This file contains the two border tones and a small burst
of white noise to indicate the ambiguity of position.
Finally, gaugeunr.wav is to indicate completely unreadable
progress bars. This file is just a burst of white noise without the
border tones. This file may no longer be needed for MSAA capable
bars.
Since different projects may prefer different file name prefixes, a
renfiles.bat file is also included to rename all the sound files in
the set at once: Usage: renfiles oldPrefix newPrefix. Example:
renfiles gauge progress
will rename the files progress0.wav, progress100.wav, progressnew.wav,
etc.
Doug Lee
November 15, 2009
On Sun, Nov 15, 2009 at 11:09:54PM -0000, Steve Nutt wrote:
Hi,
The only difficult situation for the others for me was laptop speakers, but
I did prefer them overall. I think a piano might do it.
All the best
Steve
-----Original Message-----
From: J.J. Meddaugh [mailto:[email protected]]
Sent: Sunday 15 November 2009 21:03
To: [email protected]
Subject: Re: Feedback about the Latest Progress Indicator Script
The others were too muted to me. But there's probably a middle ground.
There's also a difference in headphones vs. speakers vs. laptop speakers.
J.J. Meddaugh - ATGuys.com
A premier Licensed Code Factory and KNFB Reader distributor
----- Original Message -----
From: "Steve Nutt" <[email protected]>
To: <[email protected]>
Sent: Sunday, November 15, 2009 2:47 PM
Subject: RE: Feedback about the Latest Progress Indicator Script
> Hi JJ,
>
> Sorry, but you must admit, they are loud and horrid sounds <Smile>.
>
> All the best
>
> Steve
>
> -----Original Message-----
> From: J.J. Meddaugh [mailto:[email protected]]
> Sent: Sunday 15 November 2009 18:37
> To: [email protected]
> Subject: Re: Feedback about the Latest Progress Indicator Script
>
> Wow. Guess I should have never touched the old sounds, grin.
> I'll see what I can do.
>
> J.J. Meddaugh - ATGuys.com
> A premier Licensed Code Factory and KNFB Reader distributor
> ----- Original Message -----
> From: "Steve Nutt" <[email protected]>
> To: <[email protected]>
> Sent: Sunday, November 15, 2009 1:16 PM
> Subject: RE: Feedback about the Latest Progress Indicator Script
>
>
>> Hi Curtis,
>>
>> Could you send the wavs to me please? Don't like these horrible noises.
>>
>> Thanks.
>>
>> All the best
>>
>> Steve
>>
>> -----Original Message-----
>> From: Curtis Delzer [mailto:[email protected]]
>> Sent: Sunday 15 November 2009 17:29
>> To: [email protected]
>> Subject: RE: Feedback about the Latest Progress Indicator Script
>>
>> I do have them now.
>>
>>
>> Curtis Delzer.
>> HS.
>>
>>
>> on Sunday 11/15/2009 02:49 AM, Steve Nutt said:
>>>I would go back to the original sounds, but since updating I don't know
>> what
>>>the original wav files were that were used. Anyone have them?
>>>
>>>All the best
>>>
>>>Steve
>>>
>>>-----Original Message-----
>>>From: Life My Way [mailto:[email protected]]
>>>Sent: Sunday 15 November 2009 02:50
>>>To: [email protected]
>>>Subject: Re: Feedback about the Latest Progress Indicator Script
>>>
>>>why not use a real panio to make the notes or go back to the orginal
>>>sounds?
>>>----- Original Message -----
>>>From: "Steve Nutt" <[email protected]>
>>>To: <[email protected]>
>>>Sent: Saturday, November 14, 2009 5:51 PM
>>>Subject: RE: Feedback about the Latest Progress Indicator Script
>>>
>>>
>>>Hi J J,
>>>
>>>I prefer the older sounds. They were no good for laptops, but I liked
>>>them
>>>for the desktop. Any way we can get them back other than downgrading? I
>>>think we should be able to choose the ascending sounds, between those
>>>two.
>>>These now are too loud and harsh for a desktop or headphones situation.
>>>
>>>All the best
>>>
>>>Steve
>>>
>>>-----Original Message-----
>>>From: J.J. Meddaugh [mailto:[email protected]]
>>>Sent: Saturday 14 November 2009 20:41
>>>To: [email protected]
>>>Subject: Re: Feedback about the Latest Progress Indicator Script
>>>
>>>I'm open to ideas. Agreed those aren't the greatest sounds either.
>>>Ideally
>>>there would be a tone generator function in VBScript but alas there
>>>isn't.
>>>
>>>J.J. Meddaugh - ATGuys.com
>>>A premier Licensed Code Factory and KNFB Reader distributor
>>>----- Original Message -----
>>>From: "Curtis Delzer" <[email protected]>
>>>To: "Steve Pattison" <[email protected]>; "GW Info"
>> <[email protected]>
>>>Cc: "the gw-micro scripting list" <[email protected]>
>>>Sent: Saturday, November 14, 2009 1:59 PM
>>>Subject: Re: Feedback about the Latest Progress Indicator Script
>>>
>>>
>>> >I believe the reasons for the sounds are percentages of one. The other
>>> >sounds, the whole tone scale as it was, I think only 20 rather than 100
>>> >sounds? Guessing but that is a default of 5 percentage. I don't like
>>> >that
>>> >"raspy" sound either, which actually are square waves as opposed to
>>> >sine
>>> >waves, and seems to me that they are the same as the NVDA sounds which
>>> >indicate progress bars. The problem with 100 sounds, is the range of
>>> >most
>>> >speaker systems on computers, and maintaining some kind of musical
>> context
>>> >as in the earlier sounds. I'll see if I can work out something, because
>> it
>>> >would be fun to hear musical sounds as opposed to this rasp. :)
>>> >
>>> >
>>> > Curtis Delzer.
>>> > HS.
>>> > sounds. Problem,
>>> >
>>> > At Thursday 11/12/2009 03:40 AM, Steve Pattison wrote:
>>> >>First of all I appreciate the hard work people who write scripts do to
>>> >>provide so many useful scripts for people like me who don't have the
>>> >>slightest clue how to write scripts or any other type of program.
>>> >>
>>> >>However I am very disappointed with the new sounds in the latest
>>> >>version
>>> >>of the Progress Indicator script. I find the new sounds very harsh
>>> >>and
>>> >>bordering on being annoying. However I appreciate other people prefer
>>> >>these sounds and I understand why GW Micro feel the new sounds are
>>> >>better for people using laptops etc.
>>> >>
>>> >>I have a suggestion that could possibly please everyone. Why not
>>> >>create
>>> >>another script with the original sounds and call it something like
>>> >>Progress Indicator Classic or similar and make it identical to the new
>>> >>Progress Indicator script except for the sounds. Then you could
>>> >>include
>>> >>the edition of the script with the new sounds as the default script
>>> >>with
>>> >>Window-eyes and also on Script Central and as well make another
>>> >>edition
>>> >>of the script available on Script Central with the sounds that wer
>>> >>used
>>> >>previously with this script.
>>> >>
>>> >>Regards Steve
>>> >>Email: [email protected]
>>> >>MSN Messenger: [email protected]
>>> >>Skype: steve1963
>>> >>Twitter: steve9782
>>> >>
>>> >>If you reply to this message it will be delivered to the original
>>> >>sender only. If your reply would benefit others on the list and
>>> >>your message is related to GW Micro, then please consider sending
>>> >>your message to [email protected] so the entire list will receive
>>> >>it.
>>> >>
>>> >>All GW-Info messages are archived at http://www.gwmicro.com/gwinfo,
>>> >>and
>>> >>can be searched through and sorted using the search
>>> >>form at the bottom of the page.
>>> >>
>>> >>If you wish to unsubscribe from this list, send a message to
>>> >>[email protected] and include leave gw-info in the body
>>> >>of the message.
>>> >
>>> >
>>
>>
>>
>>
>
>
>
>
--
Doug Lee, Senior Accessibility Programmer
SSB BART Group - Accessibility-on-Demand
mailto:[email protected] http://www.ssbbartgroup.com
"While they were saying among themselves it cannot be done,
it was done." --Helen Keller
