Text to speech error timeout waiting for the first audio chunk

BADIANBA 1 Reputation point
2022-10-20T09:25:50.35+00:00

Dear developers, when I was working on text to speech, I had been using your demo code to generate it perfectly, but yesterday it suddenly stopped working and kept reporting the error message: Speech synthesis canceled: CancellationReason.
Error details: USP error: timeout waiting for the first audio chunk
Did you set the speech resource key and region values?

I found out that you changed the way subscription and region are written, so I added the environment variables to my computer, but it still doesn't work, so I'm sad to know what the problem is.
But it is worth mentioning that on the day before yesterday (that is, the day before this module does not work), because my leader deactivated the credit card of this account without my knowledge, I wonder if this is the reason for the non-availability? But then my leader reactivated the card, but it was also not available, and even though we reapplied for the account and changed the card, it was still not available, (although the phone number in the account was the same as the phone number in the previous account)

I'm really frustrated, I've been looking at the lines of code of your demo for two days, but I didn't find any error.

I sincerely hope to communicate with you, can you teach me why this does not work? Is there something wrong, is there something I don't see that is different from the previous changes, or is there something wrong with my account?

Thank you, best wishes for your all.
252360-%E5%BE%AE%E4%BF%A1%E5%9B%BE%E7%89%87-20221020121426.png

Azure AI Speech
Azure AI Speech
An Azure service that integrates speech processing into apps and services.
2,065 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. YutongTie-MSFT 53,966 Reputation points Moderator
    2022-10-20T16:31:39.377+00:00

    Hello @BADIANBA

    Thanks for reporting this issue, this is a known issue of a Windows 10/11 patch on Tuesday (KB5018427/KB5018418) that changed the behavior of TLS in the operating system and a fix has been deployed as this anouncement, please take a look - https://learn.microsoft.com/en-us/windows/release-health/resolved-issues-windows-server-2022#2924msgdesc

    Resolution: This issue was resolved in the out-of-band update KB5020436. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB5020436, search for it in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. Note KB5020436 is not available from Windows Update and will not install automatically.

    Affected platforms:
    ​Client: Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
    ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1

    Regards,
    Yutong

    -Please kindly accept the answer if you feel helpful to support the community, thanks a lot.

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.