Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing the sound effects for NVDA #1007

Closed
nvaccessAuto opened this issue Oct 30, 2010 · 13 comments
Closed

Changing the sound effects for NVDA #1007

nvaccessAuto opened this issue Oct 30, 2010 · 13 comments
Labels
enhancement p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority

Comments

@nvaccessAuto
Copy link

Reported by KevanGC on 2010-10-30 10:51
There are sounds that are played with NVDA. For example, the sounds for focus and browse modes. They work fine, but I would like to be able to change those to other .wav sounds. Can you add a dialog or something that allows you to do that?

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2010-10-30 11:32
Changes:
Milestone changed from None to None

@nvaccessAuto
Copy link
Author

Comment 2 by RamboUdin on 2010-11-02 06:46
delete the file, and copy your new file with the same ile name.

@nvaccessAuto
Copy link
Author

Comment 3 by KevanGC on 2010-11-08 02:21
OK I did that, it worked. I created some browse and focus mode replacement sounds. Here they are.
http://www.4shared.com/file/XXa8aX8j/Browse_And_Focus_Mode_Replacem.html
I recommend using these instead of the originals, these sound better. To install them, just delete the original browseMode.wav and focusMode.wav files in the "Waves" folder for NVDA, and copy these into that folder.

@feerrenrut
Copy link
Contributor

Some additional discussion from duplicate issue #5978:

All the same, a GUI for sound scheme management and its volume control
would be extremely helpful, but I think there is a ticket that covers
that functionality already.

@feerrenrut feerrenrut added the p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority label Oct 28, 2016
@feerrenrut
Copy link
Contributor

P3 This would provide value in the overall "look and feel" and polish of NVDA helping with early impressions. As well as having the byproduct of providing indirect training on the meaning of the sounds. The cost to implement is likely not very high, and of low complexity.

@derekriemer
Copy link
Collaborator

If volume control is done, please implement tones.beep volume control as
well.

Thanks.

On 10/27/2016 10:48 PM, Reef Turner wrote:

P3 This would provide value in the overall "look and feel" and polish
of NVDA helping with early impressions. As well as having the
byproduct of providing indirect training on the meaning of the sounds.
The cost to implement is likely not very high, and of low complexity.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1007 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFGivfwDiaLfZRkFSSlzCqFCX-e8xYLJks5q4X6DgaJpZM4KjEtF.


Derek Riemer
  • Department of computer science, third year undergraduate student.
  • Proud user of the NVDA screen reader.
  • Open source enthusiast.
  • Member of Bridge Cu
  • Avid skiier.

Websites:
Honors portfolio http://derekriemer.com
Awesome little hand built weather app!
http://django.derekriemer.com/weather/

email me at derek.riemer@colorado.edu mailto:derek.riemer@colorado.edu
Phone: (303) 906-2194

@jcsteh
Copy link
Contributor

jcsteh commented Oct 28, 2016

I'm not convinced on UX/polish here. It seems a lot of common stuff doesn't allow customisation of "core" sounds. For example, iOS allows customisation of ring and message tones, but you can't, for example, change the lock sound, charging sound, typing sounds, VoiceOver screen reader sounds, etc. Furthermore, one could argue sounds are actually a part of branding. Users can't (and shouldn't be able to) customise the logo. That's not necessarily an argument against allowing sound customisation, but it certainly lowers the priority a lot.

@bhavyashah
Copy link

Hi,
If sound customization may affect NVDA's branding, at least volume
control for NVDA's audio schemes should be implemented. Also, if not
deemed excessively confusing for existing users to adapt to this
change, at least the focus mode sound scheme should be revised to
something softer and pleasanter. Bearing in mind the untempting voice
of ESpeak-NG, which is often felt robotic, for improved initial
impressions with regards to overall user experience of NVDA, as has
been noted by several in related duplicate tickets, NVDA's sounds do
need modification, either minor changes or a complete revamp, for
apart from (subjective) lack of polish in them, their relative volumes
to each other are also quite different, making at least the focus mode
sound all the more prominent in its loudness. Also, if the NVDA user
is using a softer speech synthesizer in terms of volume, such as a
female SAPI 5 voice, a softer ESpeak variant, or any other
comparatively softer TTS engine, that too while using earphones or
headphones, the NVDA sounds could well become quite irritatingly
unpleasant (apologies for the word choice). Having personally
experienced this, I have currently completely disabled the browse mode
and focus mode auditory feedback in favour of their speech feedback,
and often toggle NVDA to not beep and indicate progress bar updates.
Apologies for the lack of particularity in the above comment. Having
said the above though, I don't necessarily disagree about the priority
assigned to this ticket.
Thanks.

On 10/28/16, James Teh notifications@github.com wrote:

I'm not convinced on UX/polish here. It seems a lot of common stuff doesn't
allow customisation of "core" sounds. For example, iOS allows customisation
of ring and message tones, but you can't, for example, change the lock
sound, charging sound, typing sounds, VoiceOver screen reader sounds, etc.
Furthermore, one could argue sounds are actually a part of branding. Users
can't (and shouldn't be able to) customise the logo. That's not necessarily
an argument against allowing sound customisation, but it certainly lowers
the priority a lot.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#1007 (comment)

Best Regards
Bhavya Shah

Avid Enthusiast and User of the Free NVDA Screen Reader (www.nvaccess.org)

Contacting Me
E-mail Address: bhavya.shah125@gmail.com
Follow me on Twitter @BhavyaShah125 or www.twitter.com/BhavyaShah125
Mobile Number: +91 7506221750

@Brian1Gaff
Copy link

Why would anyone want to change the sound effects? I would have thought they
had been around so long now that people would find a change annoying. That
is not to say of course that the ability to select others should not be
offered to users who would like that feature, but leave defaults alone.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "bhavyashah" notifications@github.com
To: "nvaccess/nvda" nvda@noreply.github.com
Sent: Friday, October 28, 2016 6:34 AM
Subject: Re: [nvaccess/nvda] Changing the sound effects for NVDA (#1007)

Hi,
If sound customization may affect NVDA's branding, at least volume
control for NVDA's audio schemes should be implemented. Also, if not
deemed excessively confusing for existing users to adapt to this
change, at least the focus mode sound scheme should be revised to
something softer and pleasanter. Bearing in mind the untempting voice
of ESpeak-NG, which is often felt robotic, for improved initial
impressions with regards to overall user experience of NVDA, as has
been noted by several in related duplicate tickets, NVDA's sounds do
need modification, either minor changes or a complete revamp, for
apart from (subjective) lack of polish in them, their relative volumes
to each other are also quite different, making at least the focus mode
sound all the more prominent in its loudness. Also, if the NVDA user
is using a softer speech synthesizer in terms of volume, such as a
female SAPI 5 voice, a softer ESpeak variant, or any other
comparatively softer TTS engine, that too while using earphones or
headphones, the NVDA sounds could well become quite irritatingly
unpleasant (apologies for the word choice). Having personally
experienced this, I have currently completely disabled the browse mode
and focus mode auditory feedback in favour of their speech feedback,
and often toggle NVDA to not beep and indicate progress bar updates.
Apologies for the lack of particularity in the above comment. Having
said the above though, I don't necessarily disagree about the priority
assigned to this ticket.
Thanks.

On 10/28/16, James Teh notifications@github.com wrote:

I'm not convinced on UX/polish here. It seems a lot of common stuff
doesn't
allow customisation of "core" sounds. For example, iOS allows
customisation
of ring and message tones, but you can't, for example, change the lock
sound, charging sound, typing sounds, VoiceOver screen reader sounds,
etc.
Furthermore, one could argue sounds are actually a part of branding.
Users
can't (and shouldn't be able to) customise the logo. That's not
necessarily
an argument against allowing sound customisation, but it certainly lowers
the priority a lot.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#1007 (comment)

Best Regards
Bhavya Shah

Avid Enthusiast and User of the Free NVDA Screen Reader (www.nvaccess.org)

Contacting Me
E-mail Address: bhavya.shah125@gmail.com
Follow me on Twitter @BhavyaShah125 or www.twitter.com/BhavyaShah125
Mobile Number: +91 7506221750

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#1007 (comment)

@jcsteh
Copy link
Contributor

jcsteh commented Aug 1, 2017

We attempted to change the default sounds in #7218, but users were quite divided as to the new sounds being better or worse, so this has been reverted. We will not consider a change to the default sounds in the near term. Our current thinking is that in future, we should allow add-ons to provide sound packs, though this would probably require a small global plugin to hook the playWave function (#3393 will provide a much nicer hooking mechanism than monkey patching).

@bhavyashah
Copy link

bhavyashah commented Aug 1, 2017 via email

@jcsteh
Copy link
Contributor

jcsteh commented Aug 1, 2017

@bhavyashah commented on 1 Aug 2017, 12:49 GMT+10:

Umm, shouldn't we give another try to a different sound pack, in the
hope that something more likeable might be produced? We should
experiment with at least a couple sound schemes with users before we
throw in the towel.

No alternatives have been proposed over the years that don't fail to meet the requirements in #7218 in some way. From the feedback received, there isn't even sufficient clear, common detail on exactly what might address user concerns. We can't hope to fix an issue if there isn't enough objective data about what might actually fix it. Finally, going around and around on this just isn't a good use of time given other priorities; we've already sunk a decent amount of time into this and gained a grand sum total of nothing useful. As I noted elsewhere, we are not going to consider this in the near term.

@nvaccess nvaccess locked and limited conversation to collaborators Aug 1, 2017
@derekriemer
Copy link
Collaborator

If we do further discuss this, we'll offer sound themes that can be installed. Thus, this is being closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Projects
None yet
Development

No branches or pull requests

6 participants