You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
.
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 ..
The text was updated successfully, but these errors were encountered: