# Always Listening While Always Parsing

**URL:** https://community.openconversational.ai/t/always-listening-while-always-parsing/68
**Category:** Intent Parsers
**Created:** [September 12, 2015, 2:48am UTC](https://community.openconversational.ai/t/always-listening-while-always-parsing/68 "2015-09-12T02:48:06Z")
**Posts on this page:** 8
**Page:** 2

<div class="post-metadata">

### Author: ![festro](https://community.openconversational.ai/letter_avatar_proxy/v4/letter/f/e495f1/32.png) [@festro](https://community.openconversational.ai/u/festro)
#### Post date: [May 21, 2017, 10:42pm UTC](https://community.openconversational.ai/t/always-listening-while-always-parsing/68/21 "2017-05-21T22:42:11Z")

</div>

the paranoid end user likely wouldn’t be using Mycroft in the first place fearing a shadow government may be listening to spoken near an adjacent mic. thing is thing is privacy is antiquated, a commodity that could be kept back in the days when light bulbs, mp3 players, and dog collars were not connected to the internet

---

<div class="post-metadata">

### Author: ![Jonah\_Embry](https://community.openconversational.ai/letter_avatar_proxy/v4/letter/j/8797f3/32.png) [@Jonah\_Embry](https://community.openconversational.ai/u/Jonah_Embry)
#### Post date: [August 3, 2019, 2:12am UTC](https://community.openconversational.ai/t/always-listening-while-always-parsing/68/22 "2019-08-03T02:12:25Z")

</div>

Ok, we’re now 2 years down the road. Where does this idea stand with the current progress Mycroft and Raspberry Pis have made?

---

<div class="post-metadata">

### Author: ![baconator](https://community.openconversational.ai/letter_avatar_proxy/v4/letter/b/d07c76/32.png) [@baconator](https://community.openconversational.ai/u/baconator)
#### Post date: [August 4, 2019, 1:35pm UTC](https://community.openconversational.ai/t/always-listening-while-always-parsing/68/23 "2019-08-04T13:35:26Z")

</div>

Whatever progress you’ve made is going to be it.

---

<div class="post-metadata">

### Author: ![Dominik](https://community.openconversational.ai/user_avatar/community.openconversational.ai/dominik/32/1936_2.png) [@Dominik](https://community.openconversational.ai/u/Dominik)
#### Post date: [August 4, 2019, 7:20pm UTC](https://community.openconversational.ai/t/always-listening-while-always-parsing/68/24 "2019-08-04T19:20:40Z")

</div>

There is [Kaldi-spotter](https://github.com/JarbasAl/kaldi_spotter) by @JarbasAl which goes in the direction of „always listenung“. You can define phrases which trigger intents without using the hotword.

---

<div class="post-metadata">

### Author: ![gez-mycroft](https://community.openconversational.ai/user_avatar/community.openconversational.ai/gez-mycroft/32/1937_2.png) [@gez-mycroft](https://community.openconversational.ai/u/gez-mycroft)
#### Post date: [August 5, 2019, 1:09am UTC](https://community.openconversational.ai/t/always-listening-while-always-parsing/68/25 "2019-08-05T01:09:16Z")

</div>

Disclaimer, I haven’t read this whole thread, however I can pretty confidently say this won’t be coming to Mycroft (at least in the next few years).

Using a local STT engine like Kaldi and defining a limited number of phrases (as Jarbas has) means you could achieve a portion of this. However a broad all listening and all understanding assistant is economically and technically not feasible (on current hardware) at this time.

If you take a look at the cost per minute of STT transcription from even the largest players like Google, this roughly shows how expensive it would be for Mycroft to be performing this. Once more STT moves on device this should be easier, however it would still require significant system resources to be constantly transcribing everything it hears.

---

<div class="post-metadata">

### Author: ![Wallylama](https://community.openconversational.ai/letter_avatar_proxy/v4/letter/w/85e7bf/32.png) [@Wallylama](https://community.openconversational.ai/u/Wallylama)
#### Post date: [August 8, 2019, 1:42am UTC](https://community.openconversational.ai/t/always-listening-while-always-parsing/68/26 "2019-08-08T01:42:59Z")

</div>

Sorry if this is a bit of a high jack, I think it is a closely related idea, but not exactly the same. What about speaker diarization(who is speaking, not what is being said), is it feasible to feed an audio stream to another PI like device and stream back who is talking? in anything approaching realtime? or is the problem as big as continuous stt?

---

<div class="post-metadata">

### Author: ![baconator](https://community.openconversational.ai/letter_avatar_proxy/v4/letter/b/d07c76/32.png) [@baconator](https://community.openconversational.ai/u/baconator)
#### Post date: [August 8, 2019, 2:47am UTC](https://community.openconversational.ai/t/always-listening-while-always-parsing/68/27 "2019-08-08T02:47:30Z")

</div>

Should probably start another thread for that, there’s some work on speaker ID out there already.

---

<div class="post-metadata">

### Author: ![gras64](https://community.openconversational.ai/user_avatar/community.openconversational.ai/gras64/32/2156_2.png) [@gras64](https://community.openconversational.ai/u/gras64)
#### Post date: [August 8, 2019, 12:35pm UTC](https://community.openconversational.ai/t/always-listening-while-always-parsing/68/28 "2019-08-08T12:35:23Z")

</div>

you could create a “skill we have to talk about”. If I am alone and have several inquiries (weather, music, stock market …) you could have a real conversation. Basis for sending the request to the server one could define the audio level. wait until quiet then send to stt. To conclude, thank you for stopping the conversation or stop after 30s.

[Previous page](https://community.openconversational.ai/t/always-listening-while-always-parsing/68.md?page=1)
