-
Notifications
You must be signed in to change notification settings - Fork 20
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
api key #17
Comments
Could you check the log.txt file inside the log folder, and tell me what's inside? |
Interestingly, there is nothing in the log file. |
I'm sorry, I've now found out what the log file says. |
This engine will take the "region" text and append ".tts.speech.microsoft.com" to it to get the host domain name. For example, if the region is "japaneast", the host domain name will be "japaneast.tts.speech.microsoft.com". You can ping this host, so this host exists and the region is correct. You can check if your region setting is correct. Make sure it's copied from the "Keys and Endpoint" page, and does not contain extra spaces. |
my region is set to france central. |
Then the region should just be "francecentral". |
Thank you very, very much. |
now the problem is completely solved! |
Usually you will be able to copy everything you need in the |
Yes, I understand. |
This is an interesting idea. Currently it's not possible, but I will consider adding the feature in a future release. A problem with the multilingual voices is that it may use the wrong language, and speak the text in a weird pronunciation. The issue #2 mentions that problem. An SSML tag Maybe I can give users an option to split one Azure multilingual voices into different SAPI voices for each language. For example, Do you think this is a good idea, or do you have a better way? |
Wow! |
yes, it is true that multilingual voices pronounce some sentences in a strange way, I agree with that! |
Hello. |
The fix will be in the next release. |
This should be fixed in v0.2.2. |
Thank you very much indeed for the correction. |
Hello.
I downloaded the latest update to my computer.
I got an api key.
I entered the api key and the region and saved it.
the azure sounds appear among the sapi 5 sounds, but it does not synthesize.
when i enter the same api key in balabolkaya and make it synthesize, it synthesizes without any problem.
also there was only edge sound list in the app data folder, I deleted the sound list manually.
so the azure tts voice list does not appear in my app data folder, but the voices do not speak even though they appear in sapi 5 voices.
can you please help me?
thank you.
The text was updated successfully, but these errors were encountered: