4 ms·
"Use case" perhaps wasn't the right word for me to use. Maybe "applications" would have been a better word. What this enables is speech-to-speech applications i
by kaycebasques 2y ago
"Use case" perhaps wasn't the right word for me to use. Maybe "applications" would have been a better word. What this enables is speech-to-speech applications in embedded devices. (From my quick scan) it doesn't seem to do anything around other ML applications that OpenAI could potentially be involved in, such as speech-to-text, text-to-speech, or computer vision.
But yeah, once I figured out that this enables streaming speech-to-speech applications on embedded devices, then it's easy to think up use cases.
- swatcoder 2y agoIt doesn't help that this was posted to HN with the "Usages" section of the README left blank. That alone would probably have addressed your question. The submission is just a little prematue. Beyond that, while it does seem like its primarily vision is for speech-to-speech interfaces, it could easily be stretched to do things like send a templatized text prompt that was constructed based on toggle states, sensor readings, etc and (optimistically) asking for a structured response that could control lights or servos or whatever. Generally, this looks like a very early stage in a hobby project (the code practices fall short of my expectations for good embedded work, being presented as a library would be better than as an application, the README needs lots of work, etc), but something more sophisticated isn't too far out of reach.
- Sean-Der 2y agoI will work on making it better! This was announced Tuesday [0] I still need to give it lots of love. Even though the README isn’t completely done, give it a chance I bet you can have fun with it :) [0] https://youtu.be/14leJ1fg4Pw?t=625&si=aqHm1UAdDEz91TnD https://youtu.be/14leJ1fg4Pw?t=625&si=aqHm1UAdDEz91TnD