Thank you for bringing this to our attention. I have not been able to reproduce the results reported here. When I tested a .wav PCM 16-bit little-endian signed recording, the result was exactly as described above. I first received an operation name from the async API call and eventually got a response JSON with the Operation GET API that included transcribed text.
This may be be an issue with the audio file, language recognition, or something else specific to your use. Please submit a new issue on our Google Cloud Platform public issue tracker <https://code.google.com/p/google-cloud-platform/issues/list> and we can investigate this further. Be sure to attach the file used and the *AudioConfig* <https://cloud.google.com/speech/reference/rest/v1beta1/RecognitionConfig#audioencoding> sent with the recording so that we may attempt to reproduce your results. Also, please link to it from here and back so that others may follow. Thanks in advance for your patience. On Wednesday, August 10, 2016 at 8:30:55 PM UTC-4, Bruno Leitão wrote: > > Hi all, > > I perform a async request to google speech-to-text, and now i do not know > how to get the result of operation. > > I already know that operation was successful > > Thanks > BL > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/a7f0f9d5-e36d-4c3c-878e-97ac94203b5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
