bangnguyen

Results 11 comments of bangnguyen

Hi etozzato, Sorry my question is not related with your issue. You said "The local prototype works like a charm", Did you test the streaming for audio that have a...

Just want to give the update on my issue, by reading the code [TranscribeStreamingClient:](https://github.com/awslabs/amazon-transcribe-streaming-sdk/blob/develop/amazon_transcribe/client.py). I understood why issue happen, the audio file in my local has the file-size about 100...

Hi @lalogonzalez For the first issue, I have used the snap code of this [example](https://github.com/awslabs/amazon-transcribe-streaming-sdk/blob/develop/examples/simple_file.py). All parameters are the same (chunk_size, sample_rate, ..), only one different is my audio in...

Hi Eduardo, I don't have issue like this, can tested with two different audio files and able to get transcript for more than 20 minutes and did not lose anything,...

Thank you so much @joguSD for your very useful solution. I just take your snap code and do the testing for a big audio file. So far everything is good....

@joguSD `parse_wav_metadata` function test with my audio file. - `assert data_header == b'data'` , throw Exception my audio file return `data_header = 'List'`. I removed this assert to get pass...

@joguSD I was confused when I said it was working well more than 1 hour. I read your code and saw that there is a control on amount of data...

@joguSD I put the log into _**_sign_event**_ method of [eventstream](https://github.com/awslabs/amazon-transcribe-streaming-sdk/blob/develop/amazon_transcribe/eventstream.py), just to get detail the value of parameters before sending signature for each chunk. And I found that, after getting...

Hi @joguSD It seems that current code base using temporary security credentials. I am wondering that during the streaming, if the credentials is changed and is used to create signature...

@joguSD My workaround now is to reuse the existing credential on each sign for stream_chunk, to do this I use the my **MyCustomCredentialResolver** in stead of **AwsCrtCredentialResolver**. Its run smoothly...