Mycroft Mimic: Difference between revisions

Eben (talk | contribs)
 
(2 intermediate revisions by the same user not shown)
Line 13: Line 13:
While setting up a Mycroft device installer will ask to build Mimic 1 locally. If you initially skipped this you can also re-run dev_setup.sh with a -fm flag for "force mimic".<blockquote>./dev_setup.sh -fm</blockquote>You can do the opposite, by running flag to "skip mimic":<blockquote>./dev_setup.sh -sm</blockquote>
While setting up a Mycroft device installer will ask to build Mimic 1 locally. If you initially skipped this you can also re-run dev_setup.sh with a -fm flag for "force mimic".<blockquote>./dev_setup.sh -fm</blockquote>You can do the opposite, by running flag to "skip mimic":<blockquote>./dev_setup.sh -sm</blockquote>


== '''KDE & gnome integration (mimic v1)''' ==
== Installation (mimic v1) ==
 
===== On Arch based distros =====
Install from the AUR: https://aur.archlinux.org/packages/mimic
 
===== On Debian based distros =====
<code>$ sudo apt-get install gcc make pkg-config automake libtool libasound2-dev</code>
 
===== On Fedora based distros =====
<code>$ sudo dnf install gcc make pkgconfig automake libtool alsa-lib-devel</code>
Mimic v1 source: https://github.com/MycroftAI/mimic1
 
== KDE & gnome integration (mimic v1) ==


This setup will let you read text with mimic tts from '''any application''' on your system simply by pressing a keyboard command.
This setup will let you read text with mimic tts from '''any application''' on your system simply by pressing a keyboard command.
Line 24: Line 36:
Stop mimic with:
Stop mimic with:
  <code>pkill mimic</code>
  <code>pkill mimic</code>
'''Important:''' as these commands are run as a scrip instead of in a full shell environment its best to put the full path to each application you call, for example: usr/bin/xsel & usr/bin/mimic etc.