Skip to content

Latest commit

 

History

History
74 lines (46 loc) · 4.51 KB

README.md

File metadata and controls

74 lines (46 loc) · 4.51 KB

Jasper - Snowboy Hot Word Detection

Build Status Coverage Status Codacy Badge

Client code for the Jasper voice computing platform. Jasper is an open source platform for developing always-on, voice-controlled applications.

Learn more at jasperproject.github.io, where we have assembly and installation instructions, as well as extensive documentation. For the relevant disk image, please visit SourceForge.

The differences with the main project

The problem with stt online, it's the big lack of PriVAcy !!!

In jasper by adding stt_passive_engine in profile.yml you can choose the stt who gonna listen to you til you said "Jasper !". Of course you have to choose a not online stt, if you mind about your PriVAcy...

That's good But !

  • You can't easily choose a wake up word.
  • Due to my accent (I think), when i said "Jasper"... doesn't work all the time...

To address these points, i decide to use "Snowboy Hot Word Detection" https://snowboy.kitt.ai/ as "stt passive engine".

  • Define and train your own hotword
  • High accuracy,
  • Low latency and no internet needed
  • Small memory footprint and cross-platform support

I use code from https://github.com/Uberi/speech_recognition to :

  • Have a new threshold calculation
  • Add bing stt
  • Record

Go try this project individually : -> https://snowboy.kitt.ai/ -> https://github.com/Uberi/speech_recognition

Installation

  • Follow the python installation -> https://github.com/Kitt-AI/snowboy
  • copy _snowboydetect.so (generated in project snowboy/swig/Python) in jasper/client/snowboy
  • create your model -> https://snowboy.kitt.ai/
  • copy your model under the name "model.pmdl" in /jasper/client/snowboy)
  • And here we go !!!

TODO

  • Re add gmail notification

Contributing

If you'd like to contribute to Jasper, please read through our Contributing Guide, which outlines the philosophies to preserve, tests to run, and more. We highly recommend reading through this guide before writing any code.

The Contributing Guide also outlines some prospective features and areas that could use love. However, for a more thorough overview of Jasper's direction and goals, check out the Product Roadmap.

Thanks in advance for any and all work you contribute to Jasper!

Support

If you run into an issue or require technical support, please first look through the closed and open GitHub Issues, as you may find a solution there (or some useful advice, at least).

If you're still having trouble, the next place to look would be the new Google Group support forum. If your problem remains unsolved, feel free to create a post there describing the issue, the steps you've taken to debug it, etc.

Contact

Jasper's core developers are Shubhro Saha, Charles Marsh and Jan Holthuis. All of them can be reached by email at [email protected], [email protected] and [email protected] respectively. However, for technical support and other problems, please go through the channels mentioned above.

For a complete list of code contributors, please see AUTHORS.md.

License

Copyright (c) 2014-2015, Charles Marsh, Shubhro Saha & Jan Holthuis. All rights reserved.

Jasper is covered by the MIT license, a permissive free software license that lets you do anything you want with the source code, as long as you provide back attribution and "don't hold [us] liable". For the full license text see the LICENSE.md file.

Note that this licensing only refers to the Jasper client code (i.e., the code on GitHub) and not to the disk image itself (i.e., the code on SourceForge).