Live data from Hacker News

Build your own Jarvis

jasperproject.github.io

21–30 of 31 posts

Re: Build your own Jarvis

#21

This is cute, and definitely a good educational resource about mature foss HCI applications, but this will not give the degree of quality that many have come to expect from assistants as simple as even Amazon's Alexa. Sirius is much closer to what you want. http://sirius.clarity-lab.org/sirius-suite/

Didn't know that Caffe can be used for speech recognition! Does it convert the audio to spectral images and do it that way?

I wonder how good the results are compared to to Google's stack - http://googleresearch.blogspot.co.uk/2015/08/the-neural-netw... - check arxiv for more info. Haven't seen any open source implementations yet

Re: Build your own Jarvis

#22
The recommended mic is probably ok, but for far field audio, or even slightly noisy environments, a microphone array enabling beamforming (like on Amazon Echo) would be much better

Re: Build your own Jarvis

#23
Did anyone try installing it on Linux? If so I'd love some pointers, I tried unsuccessfully tonight.

It seems it was build solely for Pi, I don't think there will be issues though since it is written in Python

Re: Build your own Jarvis

#24
post #9

I went through the code a little while ago when I first saw this on HN. My thoughts: It really doesn't scale. It is designed for running on a single instance of physical hardware, RPi. In it's current guise it is really difficult to separate out, particularly, the TTS part which is tied to outputting to a speaker. There is also no way to process different parts on different machines, wrap up the answer and post it ba…

Thanks for the thoughtful feedback--I think these are very fair comments.

When we first designed Jasper, it was just for us to hack around with, so regex matching, the priority system, the single-instance configuration, etc.--these all made a lot of sense for our use case (and the use cases that we foresaw w/r/t casual hackers). Our goal was just to make things simple and accessible (hence our focus on documentation). Since our initial release, Jan Holthuis has taken over much of the development, and he's put a big emphasis on abstracting out the STT and TSS libraries (as you mentioned) and improving the design more generally. My hope is that Jasper will continue to grow and mature, and that the suggestions and possibilities you mention become realities.

Re: Build your own Jarvis

#25

This is cute, and definitely a good educational resource about mature foss HCI applications, but this will not give the degree of quality that many have come to expect from assistants as simple as even Amazon's Alexa. Sirius is much closer to what you want. http://sirius.clarity-lab.org/sirius-suite/

Was interested in this but from my reading of the docs it looks like it just queries a local instance of Wikipedia? So I couldn't ask "What's the weather today" or "Do I have an appointment on Saturday" or "Who won last night's Redskins game?". Which means it's a neat toy but nothing I'd ever use.

Re: Build your own Jarvis

#27
Looks very simple to create your own module. Would be great to see it work independent of raspberrypi. At least so you can run in text mode on your laptop to give it a whirl. Also would be awesome to see some sort of jasper-cluster where you could have it running on multiple devices that can push updates to all devices when modules are added/configurations changed.

Re: Build your own Jarvis

#28
It would be cool if you could make a HTTP request with the voice command as text , then have it speak the result. Would make it easy to write services for it.

I would be very interested in a product like this with the above functionality.

Re: Build your own Jarvis

#29
post #12
post #5

If you're interested in this stuff (AI, Cybernetics, ML, etc) come jump on Playa with me. http://getplaya.com/

Just a tip. I do not understand what kind and what for your service is. Poor presentation in your website.

It's basically the platform for a "Jarvis" type interface.

Re: Build your own Jarvis

#30
post #24
post #9

I went through the code a little while ago when I first saw this on HN. My thoughts: It really doesn't scale. It is designed for running on a single instance of physical hardware, RPi. In it's current guise it is really difficult to separate out, particularly, the TTS part which is tied to outputting to a speaker. There is also no way to process different parts on different machines, wrap up the answer and post it ba…

Thanks for the thoughtful feedback--I think these are very fair comments. When we first designed Jasper, it was just for us to hack around with, so regex matching, the priority system, the single-instance configuration, etc.--these all made a lot of sense for our use case (and the use cases that we foresaw w/r/t casual hackers). Our goal was just to make things simple and accessible (hence our focus on documentation)…

That's entirely fair. I realise my use case wasn't the same as your intended goals so I was trying to not be too critical -- also half remembered ;)

You've done some really great stuff in terms of documentation and platform support and it's been designed perfectly for people to start hacking on, which I hope will bring in more interest and in turn bring in faster development.

Post reply on HN