Closed nuatmochoi closed 3 years ago
@nuatmochoi Can you try replacing the code for the KVSTranscriber with the code built in this PR: https://github.com/amazon-connect/amazon-connect-realtime-transcription/pull/57 ? That has updated dependencies and should support Korean. I tested with Australian English, which is a newer supported language, and it worked for me.
Sorry for late confirm. I tested with your latest PR, using Korean(ko-KR), and it works well. Thank you for your timely and excellent solution to the problem. This issue was solved, and I close this issue.
After communication with AWS Support Center, I made this issue. In transcribeStreaming, languageCode korean(ko-KR) is not working.
When I tested KVSTranscriber in English(en-US) without any settings, There's no problem in process of speech-to-text. In reference of other language (ex> en-GB, es-US), I set the languageCode to ko-KR, many errors occurred like below:
kvsTranscriber Logs (It's too long, so I cut it. If you wanna whole logs, I can reply it)
I thought main problem is: Your request timed out because no new audio was received for 15 seconds. But I certainly speak on the phone. The call test environment for korean was same with english.
I already know some preconditions are necessary for using added supported languages such as korean, japanese. I took those actions.
AWS Support Center said "Some changes to the Transcribe SDK in the newer version that supports Korean is likely what is causing the issue". And I agree it. So I want to track the change against this issue. And I want to know what is the origin problem that causes this issue?
Thank you. I'll be waiting the response.