Whenever an error is encountered which is written to the log, in alpha
and beta versions of NVDA, this produces an audible beep.  That's the
error sound you can hear.  In fact, you likely encounter many of the
same errors running a release candidate or version and they also get
written to the log - but there is no audible sound.

The sound is because alpha versions are often used by developers, add-on
authors and code contributors, to test new features and fixes and
knowing when an error is encountered helps with this.

NVDA may often try something else when it hits an error, and so from an
end user perspective, you may never know that error was encountered.  So
running the beta version, you may hear the beep, even when nothing seems
wrong.

While you can report the errors which cause these beeps if you can
ascertain exactly how to reproduce them - the most important errors are
those which have an impact on use.

Kind regards

Quentin.

On Wed, Aug 31, 2022 at 10:43 AM Chris Smart <ve3rwj@...
<mailto:ve3rwj@...>> wrote:

Well, it's beta software, so some bugs are a assumed. Right? That's
how this works?




-----Original Message-----
From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
<nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>> On Behalf Of Don H
Sent: August 30, 2022 8:42 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: [nvda] running beta

Running the latest NvVDA beta.  Why when running beta's do you get
that wonderful error ding when openning a web page?













--
Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org <http://www.nvaccess.org/>
Training: https://www.nvaccess.org/shop/ <https://www.nvaccess.org/shop/>
Certification: https://certification.nvaccess.org/
<https://certification.nvaccess.org/>
User group: https://nvda.groups.io/g/nvda <https://nvda.groups.io/g/nvda>
Facebook: http://www.facebook.com/NVAccess
<http://www.facebook.com/NVAccess>
Twitter: @NVAccess <https://twitter.com/NVAccess>