Skip to content
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

Fix support for neural-only voices #160

Merged
merged 2 commits into from
Mar 1, 2023

Conversation

Krxtopher
Copy link
Contributor

Description

This is a bug fix. Prior to this PR, if a developer tried to configure a host to use a voice that was only supported with the Polly neural engine the voice ID would be ignored and the host would default to using the Amy (en-GB) voice.

The root cause was faulty conditional logic that didn't accurately identify when the neural engine was available. This PR fixes that.

Related Issue #

n/a

Reviewer Testing Instructions

In the previous version of the repo, if you modified any of the demos to use a neural-only voice like "Elin" it would instead use "Amy" instead. Now if you modify any of the demos to use a neural-only voice, that voice will be used.

Submission Checklist

I confirm that I have...

  • removed hard-coded Cognito IDs
  • manually smoke-tested the BabylonJS integration tests
  • manually smoke-tested the BabylonJS demos
  • manually smoke-tested the Three.js integration tests
  • manually smoke-tested the Three.js demo

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@JuliaABurch JuliaABurch merged commit 688a15b into aws-samples:mainline2.0 Mar 1, 2023
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