Skip to content

Revert "Synthesizer dialog: ensure 'Microsoft Sound Mapper' is named#11616

Closed
josephsl wants to merge 1 commit into
nvaccess:betafrom
josephsl:revert11353
Closed

Revert "Synthesizer dialog: ensure 'Microsoft Sound Mapper' is named#11616
josephsl wants to merge 1 commit into
nvaccess:betafrom
josephsl:revert11353

Conversation

@josephsl

Copy link
Copy Markdown
Contributor

Link to issue number:

Reverts #11353
Original issue: #11349

Summary of the issue:

In earlier releases of Windows 10 Version 2004 (May 2020 Update), Microsoft Sound Mapper was not named (empty string). IN a summer cumulative update for 2004 (and 20H2), this problem is gone.

Description of how this pull request fixes the issue:

Reverts PR #11353 via beta branch.

Testing performed:

Tested via source and from Python Console (in 2020.2 and 2020.3 beta) to make sure Microsoft Sound Mapper is listed (tested on both 2004 and 20H2).

Known issues with pull request:

None

Change log entry:

None (#11349 entry removed as part of this PR).

Thanks.

…(PR nvaccess#11353)"

This reverts commit 4eb6f52, as a summer cumulative update for Windows 10 Version 2004 (and 20H2) fixed it.
@josephsl

Copy link
Copy Markdown
Contributor Author

Hi,

Two things:

  1. Should this problem occur again, we can revisit implementation discussion found in Synthesizer dialog: rename empty string in output device names to 'Microsoft Sound Mapper' #11353 until Microsoft fixes it (again).
  2. The reason for basing this on beta branch is due to upcoming translatable string freeze and because the PR being reverted is a 2020.3 material.

Thanks.

@josephsl

Copy link
Copy Markdown
Contributor Author

Hi,

Note that in some cases, "Microsoft Sound Mapper" isn't localized in Windows, but at least the fact that the label for it is back shows the fundamental issue was solved.

Thanks.

@lukaszgo1

Copy link
Copy Markdown
Contributor

As @josephsl pointed out above even though "Microsoft Sound Mapper" is once again named its name is not translated even for locales for which its name was translated for earlier Windows versions. From the end user perspective this is a regression. How about changing this PR such that if the first entry in the devices list is either empty or "Microsoft Sound Mapper" the translated name is used?

@feerrenrut

Copy link
Copy Markdown
Contributor

From the end user perspective this is a regression. How about changing this PR such that if the first entry in the devices list is either empty or "Microsoft Sound Mapper" the translated name is used?

I think this makes sense, there may also be users who haven't yet updated windows to the fixed version.

@josephsl

josephsl commented Sep 17, 2020 via email

Copy link
Copy Markdown
Contributor Author

@josephsl

Copy link
Copy Markdown
Contributor Author

Closed with the merge of #11627 to beta.

@josephsl josephsl closed this Sep 21, 2020
@josephsl josephsl deleted the revert11353 branch September 22, 2020 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants