nvaccess / nvda

NVDA, the free and open source Screen Reader for Microsoft Windows
https://www.nvaccess.org/
Other
2.12k stars 638 forks source link

nvda freezes in sibelius with wosapi enabled in the sibelius program #17385

Closed alireza1385mamani closed 1 week ago

alireza1385mamani commented 1 week ago

Steps to reproduce:

with nvda wasapi enabled and device set to speakers 1- download sibelius from https://www.avid.com/sibelius 2- install it. 3- when installed open a project from the recent tab. 4- go to the menue and choose the play tab. 5- go to playback devices. 6- go to audio engin options. 7- change the audio interface from the default one to speakers realtech wasapi.

Actual behavior:

nvda freezes and speech stops completely.

Expected behavior:

nvda should speak as usual.

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

installed

NVDA version:

2024.3.1.33894

Windows version:

Windows 11 24H2 (AMD64) build 26100.1742

Name and version of other software in use when reproducing the issue:

sibelius 2024.10

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

nvda 2023 abd erlier versions do have this problem as well.

If NVDA add-ons are disabled, is your problem still occurring?

yes

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

yes nvda freeses in siblius.log

Adriani90 commented 1 week ago

Can you confirm that this does not happen when Wasapi is disabled in advanced settings? Please upload a log file with log level set to debug in NVDA general settings.

alireza1385mamani commented 1 week ago

Can you confirm that this does not happen when Wasapi is disabled in advanced settings? it is still happening with wasapi disabled Please upload a log file with log level set to debug in NVDA general settings. nvda freezes sibelius.log

seanbudd commented 1 week ago

Closing as invalid. This is the intended behaviour of how Sibelius is using WASAPI. Please report this issue to the developers of Sibelius

Adriani90 commented 1 week ago

@seanbudd this doesn't seem to be related to wASAPI, see the last comment from the user above. This happens also when WASAPI is disabled.

seanbudd commented 1 week ago

@Adriani90 - winMM uses WASAPI as an underlying API these days. The issue is with how Sibelius uses WASAPI exclusively, it's going to mess with a lot of other software and is probably the intended behaviour of using that audio output method

XLTechie commented 1 week ago

I wonder if this is solved by unchecking "Let applications take exclusive control of this device" under sound properties? At least, I think you can do that for output devices.