Skip to content
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

New Google Streaming API #43

Open
ifoo opened this issue May 20, 2013 · 2 comments
Open

New Google Streaming API #43

ifoo opened this issue May 20, 2013 · 2 comments

Comments

@ifoo
Copy link

ifoo commented May 20, 2013

While browsing the chrome source archive i found a interesting file: https://src.chromium.org/viewvc/chrome/trunk/src/content/browser/speech/google_streaming_remote_engine.cc

Looks like google is switching to a streaming version (instead of the POST method on https://www.google.com/speech-api/v1/recognize). Basically, you open two HTTP connections - one to https://www.google.com/speech-api/full-duplex/v1/up and one to https://www.google.com/speech-api/full-duplex/v1/down - in order to use duplex capabilities. Audio chunks are streamed to the 'up' connection and the corresponding JSON results are sent back down through the 'down' connection (if I understand it correctly). Also there is some sort of protocol involved (check the comments at the top: https://src.chromium.org/viewvc/chrome/trunk/src/content/browser/speech/google_streaming_remote_engine.h?view=markup). This eliminates the 15 (or so) seconds cap for flac files. Only problem is the requirement of an API key and some sort of request keys.

Just wanted to let you know ..

@JamezQ
Copy link
Owner

JamezQ commented May 20, 2013

Thanks a lot for the info, I will look at this.

On Mon, May 20, 2013 at 2:03 PM, ifoo [email protected] wrote:

While browsing the chrome source archive i found a interesting file:
https://src.chromium.org/viewvc/chrome/trunk/src/content/browser/speech/google_streaming_remote_engine.cc

Looks like google is switching to a streaming version (instead of the POST
method on https://www.google.com/speech-api/v1/recognize). Basically, you
open two HTTP connections - one to
https://www.google.com/speech-api/full-duplex/v1/up and one to
https://www.google.com/speech-api/full-duplex/v1/down - in order to use
duplex capabilities. Audio chunks are streamed to the 'up' connection and
the corresponding JSON results are sent back down through the 'down'
connection (if I understand it correctly). Also there is some sort of
protocol involved (check the comments at the top: https://src.chromium.org/viewvc/chrome/trunk/src/content/browser/speech/google_stre
aming_remote_engine.h?view=markuphttps://src.chromium.org/viewvc/chrome/trunk/src/content/browser/speech/google_streaming_remote_engine.h?view=markup).
This eliminates the 15 (or so) seconds cap for flac files. Only problem is
the requirement of an API key and some sort of request keys.

Just wanted to let you know ..


Reply to this email directly or view it on GitHubhttps://github.com//issues/43
.

@kindziora
Copy link

nice, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants