3 ms·
spitballing: 'her' own hardcoded waveform is a hardcorded wake word exception. i have doubts that it'd be much more complex than that. what i do find interesti
by nickburns 2y ago
spitballing: 'her' own hardcoded waveform is a hardcorded wake word exception. i have doubts that it'd be much more complex than that.
what i do find interesting, however, is that, at times, she'll wake to an utterance from some other media i have playing and seems to 'know' immediately that she was inadvertently awoken. the 'listening' tone and 'end listening' tones sound in quick succession. i do not have voice recognition enabled (to the extent that that setting is respected).
- 01HNNWZ0MV43FF 2y ago> seems to 'know' immediately that she was inadvertently awoken. the 'listening' tone and 'end listening' tones sound in quick succession Speculation: - To reduce latency, the "listening" tone plays as soon as the wake word chip hears the wake word - To improve accuracy, the wake word chip keeps a circular buffer of the last couple seconds of audio, and the main CPU / DSP scans that when it wakes up So you get spurious wakeups exactly the same as a human - You think you hear something, then you re-listen to it in your mind and realize it was something else.
- pklack 2y agoI remember an explanation by some Google employee a while back for the Google Home that was basically this, but a layer further removed. Basically the activation causes audio to start getting streamed to the cloud backend. That runs some more thorough checks on the activation ( like checking for massively concurrent activation with the same audio, etc...) and tells the device to stop and disregard the current activation.