alt Hacker NewsTo look for a certain waveform, wouldn't you need to obtain all of the mic data at all times? I think that's what's implied by "listening" here, but semantics are rarely an interesting discussion.
To look for a certain waveform, wouldn't you need to obtain all of the mic data at all times? I think that's what's implied by "listening" here, but semantics are rarely an interesting discussion.
Yeah, I can see maaaany layers to have to differentiate between when discussing. E.g., for just a few random examples:
- The microphone always vibrates from the sound waves
- The microphone is powered in a way that the sound waves change electrical readings in some way
- The electrical readings are sent to another component reading them
- A component receiving the data does some kind of unbuffered processing related to triggered actions (e.g. a clapper or a activation wave)
- Some component temporarily uses a buffer of the data but not for permanent storage (e.g. live, unstored transcription for the deaf or a 'nevermind' after a triggered activation)
- Some component stores or sends data generated by the sound, but not necessarily the original audio or even any attributions of who (e.g. voice trigger web search sends the search query as text)
- Some component generates a stored copy of the transcription with attribution of who
- Some component stores the actual audio in a way that can be later replayed
I'd say this "sounds" like a mess to deal with, but then I'd be worried about falling into a category ;).