Mycroft, neon, ovos oh my! where to start untangling the options?

General Discussion
1

Like many, I received my mark II and, while I’m happy the hardware shipped, but a bit disappointed in the interpretation of privcy. Reading up on mycroft-dinkim, the history and software development problems, I’ve become very interested in hacking it into what I was expecting.

I can see the writing on the walls regarding the mycroft software development and the lack of interest in community input. I’m ready to dive into an alternative. I burned the neon image and like it’s interface and privacy focus but I can see it’s not quite ready for prime time, but is in a state I’d like to get involved in. The question is how do the 3 projects relate to each other at a technical software level?

This diagram from neon was helpful to see the components of diana and started to spell out the different features of each → Systems Architecture Diagram | Neon AI

By looking at that, it looks like they all work together? or some features from each have been combined with others in different projects?

I look forward to reading up and figuring it out, but where to start? is it worth learning mycroft classic core to understand features that are used in the other 2? Should I just start with neon and depend on it’s documentation to cover anything I would have learned from reading up on ovos and/or mycroft?

I really appreciate the k8’s container focus from neon, and I plan to dive into hosting all of it on prem (deep speech etc.). I have not looked into ovos very much yet so I’m not sure if those same features are present in that project’s focus.

Also, is there another forum to discuss the alternatives instead of using mycrofts to discuss replacements for their product?

5 Likes
2

Here are a few links that might help:

Image Features:
https://openvoiceos.github.io/community-docs/comparison/

Core Features:
https://openvoiceos.github.io/community-docs/mycroft/

Some of the answers to your questions on how things are related or aren’t related:
https://openvoiceos.github.io/community-docs/faq/

7 Likes
3

The formating needs to be adjusted on this page, it is really hard to read.

1 Like
4

Yep, I didn’t realise there were all those columns when I first looked.

5
6

Some remarks to the STT section for the images in the documentation: Mycroft dinkum supports local STT (coqui and vosk) and has cloud STT proxied as well (according to Customizations - Mycroft Mark II).

I was able to switch it to vosk pretty easily.

7

indeed dinkum seems to have coqui and vosk, missed that since there isnt a individual plugin repo for those…

Just saw the docs linked above, missed the before

plugins can be found here, guess i should port coqui as a ovos plugin, we have had vosk for some time

mycroft-dinkum/plugins at master · MycroftAI/mycroft-dinkum · GitHub

by the way, PRs and issues are very welcome, these docs are in early days and need some love, we have been more concerned about getting the info out there rather than making them look good, so things like image sizes etc dont look great yet. There may be some mistakes such as this one in the comparison table

8

Yes, I thought that I could have made a PR instead after I wrote the message. Will have to reactivate my GitHub account at some point… :slight_smile:

I tried coqui and vosk on dinkum, and vosk worked way better for me. So I don’t know if it’s worth the hassle porting coqui to ovos.

9

Unfortunately it starts becoming clearer Update from the CEO: Part 1

10

It’s not at all clear to me which option to use on my Mark 2 - from my superficial usability point of view

  • Dinkum doesn’t do much. I stopped using it.
  • Neon OS seems OK
  • OVOS wins me over because it works as a spotify device and answers my 3 year old grandchilds’s requests for songs.
3 Likes