Comments for don't_panic

Comment on Accessing Google Speech API / Chrome 11 by Rob

Rob — Sun, 05 Feb 2012 22:38:12 +0000

I have no idea what I’m doing wrong or what this output means when I do wget. I’ve tried everyone’s statements here for wget and none seem to work for me.

wget http://www.google.com/speech-api/v1/recognize?lang=en-us -header “Content-Type: audio/x-flac; rate=16000? -post-file=rec1.flac -output-file=output.txt

SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = C:\Program Files\GnuWin32/etc/wgetrc
–2012-02-05 17:34:11– http://www.google.com/speech-api/v1/recognize?lang=en-us
Resolving http://www.google.com... 74.125.113.104, 74.125.113.105, 74.125.113.106, …
Connecting to http://www.google.com|74.125.113.104|:80… connected.
HTTP request sent, awaiting response… 405 HTTP method GET is not supported by this URL
2012-02-05 17:34:12 ERROR 405: HTTP method GET is not supported by this URL.

–2012-02-05 17:34:12– http://%96header/
Resolving \226header… failed: No data record of requested type.
wget: unable to resolve host address `-header’
–2012-02-05 17:34:14– ftp://%93content-type/
=> `.listing’
Resolving \223content-type… failed: No data record of requested type.
wget: unable to resolve host address `”content-type’
unlink: No such file or directory
–2012-02-05 17:34:16– http://audio/x-flac;
Resolving audio… failed: No data record of requested type.
wget: unable to resolve host address `audio’
–2012-02-05 17:34:18– http://rate=16000/?
Resolving rate=16000… failed: No data record of requested type.
wget: unable to resolve host address `rate=16000′
–2012-02-05 17:34:21– http://%96post-file=rec1.flac/
Resolving \226post-file=rec1.flac… failed: No data record of requested type.
wget: unable to resolve host address `-post-file=rec1.flac’
–2012-02-05 17:34:21– http://%96output-file=output.txt/
Resolving \226output-file=output.txt… failed: No data record of requested type.

wget: unable to resolve host address `-output-file=output.txt’

Comment on Accessing Google Speech API / Chrome 11 by Asiri: Let Siri Speak Your Language | Abdulrahman Alotaiba's Blog

Asiri: Let Siri Speak Your Language | Abdulrahman Alotaiba's Blog — Mon, 30 Jan 2012 04:19:19 +0000

[...] draft papers, I came across the speech API. It was proposed by Google. Further research led me to an actual implementation and usage of Google [...]

Comment on Accessing Google Speech API / Chrome 11 by gluxon

gluxon — Sun, 29 Jan 2012 03:35:00 +0000

This is the command that worked for me on Ubuntu 11.10

wget http://www.google.com/speech-api/v1/recognize?lang=en-us –header “Content-Type: audio/x-flac; rate=16000″ –post-file=NameOfFile.flac –output-file=output.txt

Hope this helped!

Comment on Accessing Google Speech API / Chrome 11 by TrkHefner_

TrkHefner_ — Fri, 27 Jan 2012 16:19:45 +0000

Okay, I finally got it working.
I’m sorry for the blob comments I placed in the process.
Since I figure I won’t be the last person to walk in on the troubles I experienced, I’ll try to make up my blobbing by explaining how I resolved the matter. I hope that by doing so I can help others googling into this thread.

First of all, I must point out that I have been trying to make this work on a windows machine. So in order to successfully make a wget call I had to install GnuWin Wget (http://sourceforge.net/projects/gnuwin32/files/wget/1.11.4-1/). The problems I experienced earlier were due to the fact that I was using the wrong release. Make sure you download and run the setup program with all dependency files included.

Second of all, the win32 version of wget seems to accept its parameters slightly different than explained in this article and the comments underneath.
The command I issue is now “wget –post-file=”out.flac” –header=”Content-Type: audio/x-flac; rate=16000″ –output-file=”result.txt” –no-check-certificate https://www.google.com/speech-api/v1/recognize?lang=en“.
Unlike I expected this didn’t write the actual desired google JSON response to result.txt.
Instead it writes the wget log to the file. This log contained “HTTP request sent, awaiting response… 200 OK Length: unspecified [application/json] Saving to: ‘recognize@lang=en’”. Why on earth it writes the JSON obj to a file called ‘recognize@lang=en’ is a riddle to me, but sure enough, the file (saved in the wget executable dir) contains the text I desired.

Strangely, the accuracy is pretty low and thus the result/recognition level is quite bad. The api recognizes only half of the words the example at html5rocks and google translate do. I figure they use a higher bitrate or something or there’s something else I am not taking into account.

Anyway, thanks for this article and the comments that helped my on my way, I hope I was able to contribute.

Comment on Accessing Google Speech API / Chrome 11 by TrkHefner_

TrkHefner_ — Wed, 25 Jan 2012 20:50:44 +0000

Okay, I did the wget call working in the end, but I’m still not there.

I am calling the API from a php file with an exec command with the api call.
Strangely, the addressbar changes from “speech.php” (my file) to “main?url=out.flac&tid=0&w=1440&h=809″ and my result file contains some weird html containing an iframe (with main?url=out.flac&tid=0&w=1440&h=809 as its src).

Here’s my code:

$cmd = ‘wget –post-file out.flac -header=”Content-Type: audio/x-flac; rate=16000″ -O resultaat.html https://www.google.com/speech-api/v1/recognize?xjerr=1&client=chromium&lang=en-US';
exec($cmd);
echo file_get_contents(“resultaat.html”);

It seems like instead of returning the JSON object I desire, the API tries to redirect the call.
I hardly doubt the Google people have just now restricted the use of their speech-to-text, so I figure it’s me who fails.

Any pointers would be greatly appreciated.