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

Build 15048: if audio ducking is set to "duck when outputting speech", audio always ducks #6933

Closed
josephsl opened this Issue Mar 6, 2017 · 4 comments

Comments

Projects
None yet
6 participants
@josephsl
Collaborator

josephsl commented Mar 6, 2017

Hi,

A possible solution to #6684:

In build 15048, when audio ducking is set to "duck when outputting speech", audio always ducks.

STR:

  1. If you haven't, install 15048 fast ring build.
  2. Run a program such as Winamp, Movies and TV and what not and play something.
  3. Perform step 2 with different audio ducking settings applied.

Expected: if audio ducking is set to "speech", other audio will duck as long as NVDA is speaking:
Actual: audio always ducks.
Reproducible: yes.

Setup:

  • NVDA version: 2017.1, latest next build.
  • OS: Windows 10 build 15048.

Thanks.

@josephsl

This comment has been minimized.

Show comment
Hide comment
@josephsl

josephsl Mar 6, 2017

Collaborator

Hi,

Never mind, misread the specs. Thanks.

Collaborator

josephsl commented Mar 6, 2017

Hi,

Never mind, misread the specs. Thanks.

@josephsl josephsl closed this Mar 6, 2017

@k-kolev1985

This comment has been minimized.

Show comment
Hide comment
@k-kolev1985

k-kolev1985 Mar 6, 2017

Hello,

I can also reproduce this. If I set NVDA to lower the volume of other apps when NVDA outputs speech and audio, the volume level remains lowered constantly and not only when NVDA is speaking.

Test environment:

  • Operating system: Windows 10 Pro Insider Preview (build 15048.0), 32-bit, in English with all locale settings set to "Bulgarian", running in a virtual machine in VMWare Player.
  • NVDA version: next-13899,af44c1d4.
  • Processor: Intel Core i5-2320 at 3.00GHz.
  • RAM Memory: 3.00GB.
  • Graphics: Palit GeForce GT 630, 1024MB dedicated memory + 3071MB shared system memory, desktop resolution set to 1920x1080.
  • Sound Card: Realtek ALC662 at Intel Cougar Point PCH - High Definition Audio Controller.
  • VMware Player version: 12.5.2 build-4638234.

k-kolev1985 commented Mar 6, 2017

Hello,

I can also reproduce this. If I set NVDA to lower the volume of other apps when NVDA outputs speech and audio, the volume level remains lowered constantly and not only when NVDA is speaking.

Test environment:

  • Operating system: Windows 10 Pro Insider Preview (build 15048.0), 32-bit, in English with all locale settings set to "Bulgarian", running in a virtual machine in VMWare Player.
  • NVDA version: next-13899,af44c1d4.
  • Processor: Intel Core i5-2320 at 3.00GHz.
  • RAM Memory: 3.00GB.
  • Graphics: Palit GeForce GT 630, 1024MB dedicated memory + 3071MB shared system memory, desktop resolution set to 1920x1080.
  • Sound Card: Realtek ALC662 at Intel Cougar Point PCH - High Definition Audio Controller.
  • VMware Player version: 12.5.2 build-4638234.

@jcsteh jcsteh reopened this Mar 8, 2017

@jcsteh

This comment has been minimized.

Show comment
Hide comment
@jcsteh

jcsteh Mar 8, 2017

Contributor

No, you're correct: Microsoft reverted the ducking change in build 15048. So, we now need to revert the mitigating change in NVDA.

CC @michaelDCurran.

Contributor

jcsteh commented Mar 8, 2017

No, you're correct: Microsoft reverted the ducking change in build 15048. So, we now need to revert the mitigating change in NVDA.

CC @michaelDCurran.

@feerrenrut feerrenrut added the p2 label Mar 10, 2017

@nvaccessAuto nvaccessAuto added this to the 2017.2 milestone Mar 14, 2017

@derekriemer

This comment has been minimized.

Show comment
Hide comment
@derekriemer

derekriemer Apr 12, 2017

Collaborator

Do we really need anything in the whats new here? Was this in 17.1?

Collaborator

derekriemer commented Apr 12, 2017

Do we really need anything in the whats new here? Was this in 17.1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment