3 ms·
Love it. Don’t really love the idea of audio contents of conversations being routed to a cloud server for processing though — needs to stay on-device for privac
by npunt 8y ago
Love it. Don’t really love the idea of audio contents of conversations being routed to a cloud server for processing though — needs to stay on-device for privacy.
- davitb 8y agoThis technology is already integrated into Krisp app (https://krisp.ai https://krisp.ai) and it runs all locally on device.
- npunt 8y agoThanks for the heads up! I really like what you're doing - not only is it great for the general public, it's a game changer for people with difficulties hearing.
- developer2 8y agoTheir ultimate goal must be to be acquired by Apple, Google, or similar. This will never fly as a third-party app/install, even if it's "promised" to be on-device (such promises can change). Moreover, the average user isn't going to know about, care about, or seek out such an app, let alone pay for it. There's no widespread reach or profit in selling direct to consumer. The only way this works is for it to be built into each device/OS (ie: firmware shipped by manufacturer). If the tech has merit, we'll be seeing it in a couple of years, whether that involves an acquisition here or independent R&D/patenting.
- npunt 8y agoAgree, I wasn't suggesting users would download a special app to use it - I'd like to see the tech make its way into the OS for all voice input. I can see why the cloud processing makes sense for certain applications / licensers / acquirers (e.g. a VoIP provider like Xoom), but voice comms is really the domain of smartphones, and my hunch is most are plenty powerful enough to do this processing locally.