Tarcisio
(Tarcisio Alves de Menezes)
April 28, 2022, 7:43am
1
With the addition of the voice type “JennyMultilingualNeural” by Microsoft, I believe that now It could be possible to add the option to choose the language when calling the service.
tts:
platform: microsoft
api_key: YOUR_API_KEY
language: en-us
gender: Female
type: JennyMultilingualNeural
So when JennyMultilingualNeural is set in the configuration.yaml, we could be able to choose the “language skill” (screenshot attached) when calling the microsoft tts service.
nfh
August 8, 2022, 9:41pm
2
The platform is actually missing two important parameters: the speaking style (I suppose it’s always defaulting to General - BTW, on the API this seems to be the “type” parameter) and the Language Skill.
For instance, there are some voices that are able to whisper (good for voice notifications triggered very late ), but only if those parameters can be set.
1 Like
Tarcisio
(Tarcisio Alves de Menezes)
August 10, 2022, 5:11am
3
Yeah. It would be awesome to have those parameters available in home assistant. It would take this platform to another level.
iridris
(Steven)
September 17, 2022, 12:38pm
4
There is a pending pull request that bumps up the version of the underlying library for the Microsoft TTS service. If that PR was approved, you could embed Microsoft’s SSML which would let you add in special XML that configures the speaking style and many other settings. But that PR has been stalled out for a long time.
home-assistant:dev
← joshmwilliams:dev
opened 01:38AM - 30 Jan 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
This change is a dependency bump for Microsoft TTS to update pycsspeechtts to a newer version that allows use of inline XML tags to increase flexibility of voice synthesis.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [X] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #65221
- This PR is related to issue: #65221
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
3 Likes
Denny_Le
(Denny Le)
August 3, 2023, 4:34pm
5
@iridris @nfh @Tarcisio
Just letting you know that these parameters can be done with the current implementation of the Microsoft TTS integration. See this post:
SSML will just give TTS that extra edge.
(and unfortunately, Google Cloud TTS is very unstable in my region, but MS does).
I was able to use all the emotions like friendly, excited, shouting, whispering etc.
1 Like