NVDA 2018.3 bitta sometimes staacking when pressing arrows

jacobchawala commented 6 years ago

when pressing arrows or cursor keys, NVDA 2018.3 bitta sometimes remain silent when navigating in word, excel, web page, and windows menus. this behaviour does not occur always. you have to be keen enough to discover it.

Steps to reproduce:

Actual behavior: sometimes remaining silent when navigating using cursor keys in various applications and menus

Expected behavior: to pronounce whatever is navigated

System configuration:

NVDA Installed/portable/running from source: NVDA installer running from the computer

NVDA version: NVDA 2018.3 bitta

Windows version: windows 10 of april

Name and version of other software in use when reproducing the issue: Windows 10, Word 2016, excel 2016,

Other information about your system:

         Machine name: DESKTOP-R0NVNF4
           Machine Id: {F1EFE585-AA4A-485E-9FE9-4DC0FCCDACBF}
     Operating System: Windows 10 Pro 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)
             Language: English (Regional Setting: English)
  System Manufacturer: TOSHIBA
         System Model: Satellite C850-C035
                 BIOS: InsydeH2O Version 03.72.306.50 (type: BIOS)
            Processor: Intel(R) Core(TM) i3-2348M CPU @ 2.30GHz (4 CPUs), ~2.3GHz
               Memory: 8192MB RAM
  Available OS Memory: 8074MB RAM

Other questions:

Does the issue still occur after restarting your PC?

yes

Have you tried any other versions of NVDA?

yes but the issue remains the same

DrSooom commented 6 years ago

Three questions:

Which synthesizer are you using?
Does the braille output work as usual after the speech output "muted"?
Which NVDA version exactly did you test as well?

jacobchawala commented 6 years ago

I am using Espeak NG Unfortunately, I have not tested braille output as i don't have any notetaker or embosser.

On Thu, Aug 30, 2018 at 12:46 PM Daniel Mayr notifications@github.com wrote:

Two questions:

Which synthesizer are you using?

Does the braille output works as usual after the speech output "muted"?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/8695#issuecomment-417259495, or mute the thread https://github.com/notifications/unsubscribe-auth/ARQUb5PPD2K3dnQu7jE6U71u1SRWlas-ks5uV7RvgaJpZM4WS2id .

-- +++ Yours Sincerely, Jacob Florian Chawala JFC

Phone No. 0787016381

Emails: jacobchawala@gmail.com jacobchawala@yahoo.com

Webmail: www.caict.netai.net

Skype ID: Jacob.Florian.Chawala +++

DrSooom commented 6 years ago

The speech output only goes silent for a few seconds. After this eSpeak NG sounds as usual. Correct?

And could you please list all the other versions of NVDA on which you ancounter this issue as well. (I added this third question later in my previous comment.)

It would also be nice to know when you have encountered this issue the very first time. It could caused by a performance limitation. Maybe the devs can say what kind of logfile would be helpful in this situation.

jacobchawala commented 6 years ago

very correct. NVDA 2018.2.1.1. but it is too much in bitta of NVDA of 2018.3

On Thu, Aug 30, 2018 at 2:36 PM Daniel Mayr notifications@github.com wrote:

The speech output only goes silent for a few seconds. After this eSpeak NG sounds as usual. Correct?

And could you please list all the other versions of NVDA on which you ancounter this issue as well. (I added this third question later in my previous comment.)

It would also be nice to know when you have encountered this issue the very first time. It could caused by a performance limitation. Maybe the devs can say what kind of logfile would be helpful in this situation.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/8695#issuecomment-417288055, or mute the thread https://github.com/notifications/unsubscribe-auth/ARQUb6PjsXVgaddDMYYUs9WlHdclG7pOks5uV84jgaJpZM4WS2id .

-- +++ Yours Sincerely, Jacob Florian Chawala JFC

Phone No. 0787016381

Emails: jacobchawala@gmail.com jacobchawala@yahoo.com

Webmail: www.caict.netai.net

Skype ID: Jacob.Florian.Chawala +++

DrSooom commented 6 years ago

Just to clarify it: You mean NVDA 2018.2.1 and 2018.3 Beta 3. Correct?

As you are using Windows 10, could you please try to figure out if this issue also occurs with the OneCore synthesizer?

Adriani90 commented 5 years ago

@jacobchawala could you test it wil one core synthesizer on last Windows 10 1809 Update? Is it still an issue in NVDA 2018.4?

jacobchawala commented 5 years ago

the issue solved even in NVDA 2018.4 Espeak NG

On Sat, Jan 12, 2019 at 3:56 PM Adriani90 notifications@github.com wrote:

@jacobchawala https://github.com/jacobchawala could you test it wil one core synthesizer on last Windows 10 1809 Update? Is it still an issue in NVDA 2018.4?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/8695#issuecomment-453745428, or mute the thread https://github.com/notifications/unsubscribe-auth/ARQUb3GPcZ9-v1JPxMLRktWLbMl72_vbks5vCduZgaJpZM4WS2id .

-- +++ Yours Sincerely, Jacob Florian Chawala JFC

Phone No. 0787016381

Emails: jacobchawala@gmail.com jacobchawala@yahoo.com

Webmail: www.caict.netai.net

Skype ID: Jacob.Florian.Chawala +++

Adriani90 commented 5 years ago

Ok @jacobchawala if this is also solved, than I will close it as works for me. Please feel free to comment on it if it occurs again and we will reopen it. Thanks.

nvaccess / nvda