-
Notifications
You must be signed in to change notification settings - Fork 139
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update docs
- Loading branch information
Showing
9 changed files
with
270 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
--- | ||
title: Using AllTalk | ||
order: 14 | ||
--- | ||
|
||
Navigate to [AllTalk](https://github.com/erew123/alltalk_tts) and follow the instructions below to set up AllTalk using Docker or manually. | ||
|
||
## Setting Up AllTalk Locally | ||
|
||
### Method 1: Manual Setup | ||
|
||
For manual setup, follow the official instructions provided [here](https://github.com/erew123/alltalk_tts/blob/main/README.md#-manual-installation---as-a-standalone-application). | ||
|
||
1. Clone the AllTalk repository: | ||
```bash | ||
git clone https://github.com/erew123/alltalk_tts.git | ||
cd alltalk_tts | ||
``` | ||
|
||
2. Create conda environment and activated it: | ||
```bash | ||
conda create --name alltalkenv python=3.11.5 | ||
conda activate alltalkenv | ||
``` | ||
|
||
3. Install the required dependencies: | ||
```bash | ||
pip install -r system/requirements/requirements_standalone.txt | ||
``` | ||
|
||
4. Run the AllTalk server: | ||
```bash | ||
python script.py | ||
``` | ||
|
||
5. Access the server at `localhost:7851`. | ||
|
||
### Method 2: Setup via Docker | ||
|
||
1. Pull the AllTalk Docker image: | ||
```bash | ||
docker pull flukexp/alltalkenv | ||
``` | ||
|
||
2. Run the AllTalk Docker container: | ||
```bash | ||
docker run -d -p 7851:7851 --name alltalk-server flukexp/alltalkenv | ||
``` | ||
|
||
3. The server will be available at `localhost:7851`. | ||
|
||
## Make sure AllTalk is enabled for TTS: | ||
|
||
```bash | ||
Settings -> Text-to-Speech -> TTS Backend -> AllTalk | ||
``` | ||
|
||
### Notes | ||
- AllTalk can be used as a local text-to-speech backend in your application. | ||
- For further details, refer to the official [AllTalk GitHub repository](https://github.com/erew123/alltalk_tts). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,83 @@ | ||
--- | ||
title: Using Piper | ||
order: 13 | ||
--- | ||
|
||
Navigate to [Piper](https://github.com/rhasspy/piper) and follow the setup instructions below to run Piper locally as a TTS backend. | ||
|
||
## Setting Up Piper Locally | ||
|
||
### Method 1: Setup via Docker | ||
|
||
1. Clone the artibex/piper repository: | ||
```bash | ||
git clone [email protected]:artibex/piper-http.git | ||
``` | ||
|
||
2. Navigate to the `piper-http` directory: | ||
```bash | ||
cd piper-http | ||
``` | ||
|
||
3. Add CORS support by installing Flask CORS in the Dockerfile. To do this, locate the Dockerfile and add the following line: | ||
```bash | ||
RUN pip install flask_cors | ||
``` | ||
|
||
4. Build the Piper Docker image: | ||
```bash | ||
docker build -t http-piper . | ||
``` | ||
|
||
5. Run the Piper Docker container: | ||
```bash | ||
docker run --name piper -p 5000:5000 piper | ||
``` | ||
|
||
6. To allow CORS within the Piper server, modify the `http_server.py` file inside the running Docker container: | ||
|
||
- Navigate to the `piper-http` container's files: | ||
```bash | ||
docker exec -it piper /bin/bash | ||
``` | ||
- Locate the `http_server.py` file: | ||
```bash | ||
cd /app/piper/src/python_run/piper | ||
``` | ||
- Edit `http_server.py` and add the following lines at the top to enable CORS: | ||
```python | ||
from flask_cors import CORS | ||
CORS(app) | ||
``` | ||
7. Save the changes and restart the Piper server inside the container: | ||
```bash | ||
python3 http_server.py | ||
``` | ||
### Method 2: Manual Setup | ||
1. Clone the repository: | ||
```bash | ||
git clone https://github.com/flukexp/PiperTTS-API-Wrapper.git | ||
``` | ||
2. Navigate to the project directory: | ||
```bash | ||
cd PiperTTS-API-Wrapper | ||
``` | ||
4. Download piper, install Piper sample voices and start piper server: | ||
```bash | ||
./piper_installer.sh | ||
``` | ||
## Make sure Piper is enabled for TTS: | ||
```bash | ||
Settings -> Text-to-Speech -> TTS Backend -> Piper | ||
``` | ||
### Notes | ||
- Piper can be used as a local text-to-speech backend in your application. | ||
- For more details on models and configurations, refer to the official [Piper GitHub repository](https://github.com/rhasspy/piper). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
--- | ||
title: Features | ||
order: 3 | ||
--- | ||
|
||
Read the [Local Setup](../getting-started/installation.md) guide if you are interested in getting everything running locally quickly. | ||
|
||
## Amica Life Features | ||
|
||
Amica Life is designed to operate in a semi-autonomous mode, incorporating animations, sleep functionality, function calling, a subconscious subroutine, and self-prompting features to create a seamless virtual assistant experience. | ||
|
||
### Key Features of Amica Life | ||
|
||
* **Subconscious Subroutine**: Amica stores compressed conversation logs with timestamps, enabling it to remember past interactions and influence future responses. This enhances conversation continuity and provides a more personalized experience over time. | ||
|
||
* **Random Animation Playback**: Amica supports customizable VRM (Virtual Reality Model) avatars. These avatars can randomly trigger animations, dynamically express emotions, sync with speech, and react in real-time, providing an immersive interface. | ||
|
||
* **News Function Calling**: Amica can autonomously retrieve real-time news and relevant information based on contextual triggers within conversations. This feature ensures users stay informed without the need for manual searches. | ||
|
||
* **Self-Prompting System**: Amica’s self-prompting system can independently generate follow-up questions or perform actions based on ongoing discussions. This makes conversations more interactive and allows the assistant to anticipate user needs. | ||
|
||
## Load/Save VRM Feature | ||
|
||
Amica supports loading and saving customizable VRM avatars, allowing users to personalize their virtual assistant. Avatars can be loaded or saved for future use, with dynamic expression of emotions and lip-syncing in real-time. | ||
|
||
## Load/Save Conversation Feature | ||
|
||
Users can load and save chat conversations as `.txt` files. This feature is ideal for storing conversation histories, reviewing past discussions, or continuing from where a previous session left off. | ||
|
||
## Wake Word Feature | ||
|
||
Amica includes a wake word detection feature, allowing users to activate the assistant with a specific phrase. This enables hands-free operation and provides a more natural interaction with the system. | ||
|
||
## Chat Mode Feature | ||
|
||
In Chat Mode, Amica’s avatar minimizes into a corner of the screen, providing a compact interface. This feature is useful for multitasking, allowing users to interact with Amica while focusing on other tasks. | ||
|
||
## Plugin System (Function Calling) Feature | ||
|
||
Amica Life supports a customizable plugin system that allows users to add their own function calls. By placing scripts in the designated plugin folder, new functionalities can be seamlessly integrated, expanding Amica's capabilities. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters