2017-09-18 11:57:30 +00:00
|
|
|
six==1.10.0
|
2018-11-05 12:29:18 +00:00
|
|
|
requests==2.20.0
|
2018-11-30 08:20:26 +00:00
|
|
|
gTTS==2.0.1
|
|
|
|
gTTS-token==1.1.3
|
2017-09-02 19:47:34 +00:00
|
|
|
PyAudio==0.2.11
|
2019-01-17 10:11:43 +00:00
|
|
|
pyee==1.0.1
|
2018-01-05 10:24:56 +00:00
|
|
|
SpeechRecognition==3.8.1
|
2018-11-07 17:06:57 +00:00
|
|
|
tornado==4.5.3
|
2016-05-20 14:16:01 +00:00
|
|
|
websocket-client==0.32.0
|
|
|
|
requests-futures==0.9.5
|
|
|
|
pyalsaaudio==0.8.2
|
|
|
|
xmlrunner==1.7.7
|
|
|
|
pyserial==3.0
|
2017-04-15 01:12:43 +00:00
|
|
|
psutil==5.2.1
|
2016-07-29 18:47:40 +00:00
|
|
|
pocketsphinx==0.1.0
|
2017-01-20 21:21:03 +00:00
|
|
|
inflection==0.3.1
|
2017-07-06 21:59:26 +00:00
|
|
|
pillow==4.1.1
|
2017-07-10 20:33:21 +00:00
|
|
|
python-dateutil==2.6.0
|
2017-03-29 19:23:05 +00:00
|
|
|
pychromecast==0.7.7
|
|
|
|
python-vlc==1.1.2
|
2017-07-31 11:29:06 +00:00
|
|
|
pulsectl==17.7.4
|
Add replacment for Google TTS via Google Cloud Speech API
As noted on the Chromium Dev How-to [1] and on the
SpeechRecognition library docs [2], the Google TTS API
is really not the right API to call. While it's simple,
and allows you to authenticate via a simple token, it is
also limited to a max of *50* requests per day.
That's not a lot. I don't think many people will find that
useful, outside of quick testing (if they can even get an
API key - I couldn't figure out how to generate one that
worked correctly).
This commit introduces a new STT backend, google_cloud, so that
the Google STT backend can be deprecated eventually. To do so, we
needed to:
- Install the Google API Client Library
- Create a new STT class which knows how to turn a provided Google
JSON credentials file into a string (the SpeechRecognition library
expects you to pass in the JSON string, not a file path, nor an object).
Any person wishing to use this will need to:
- Enable the Cloud Speech API on the Google Cloud Platform console
- Create a new Service Account Key, and download the credentials to
a secure location
- Configure that location in mycroft.conf, like so:
"stt": {
"google_cloud": {
"credential" {
"json": { contents of downloaded credentials }
}
}
}
It's worth noting that the Cloud Speech API has a free quota of
60 minutes per month, which would probably stretch further than 50
individual requests. So for hobbyists, it should be nothing but
a net benefit.
[1] http://www.chromium.org/developers/how-tos/api-keys
[2] https://github.com/Uberi/speech_recognition/blob/master/reference/library-reference.rst#recognizer_instancerecognize_googleaudio_data-key--none-language--en-us-show_all--false
2017-11-14 04:40:54 +00:00
|
|
|
google-api-python-client==1.6.4
|
2018-09-28 06:26:33 +00:00
|
|
|
fasteners==0.14.1
|
2017-09-05 20:46:37 +00:00
|
|
|
|
2018-12-06 23:29:36 +00:00
|
|
|
msm==0.6.3
|
2018-11-21 11:26:22 +00:00
|
|
|
msk==0.3.12
|
2019-01-17 10:11:43 +00:00
|
|
|
adapt-parser==0.3.0
|
2019-02-01 08:22:11 +00:00
|
|
|
padatious==0.4.6
|
2018-06-25 20:28:34 +00:00
|
|
|
fann2==1.0.7
|
2019-02-01 08:22:11 +00:00
|
|
|
padaos==0.1.9
|
2018-06-18 15:43:40 +00:00
|
|
|
precise-runner==0.2.1
|
|
|
|
petact==0.1.2
|
2018-05-08 00:24:26 +00:00
|
|
|
|
2017-11-02 22:03:27 +00:00
|
|
|
# dev setup tools
|
|
|
|
pep8==1.7.0
|