Please note, my available time has become VERY limited due to unexpected family commitments Please read here for details. So please DYOR, look at the Wiki here and refer to the TTS manufacturer (Links in the Gradio interface) for issues specific to THEIR TTS engines.

I would also like to say a big thank you to anyone whom has contributed to this project either with PR's (list here) or in any discussion forums/issues tickets. Your input, guidance, help and thoughts are greatly appreciated.

AllTalk V2 Core Functionality

Comprehensive setup utilities for Windows & Linux
Multiple TTS engine support (XTTS, Piper, Parler, VITS)
Easy integration of new TTS engines (some coding required)
Customizable settings for each TTS engine
In-app model downloads for each engine
Gradio web interface for easy management
Standalone application or integration with Text-generation-webui, SillyTavern, KoboldCPP, HomeAssistant
Narrator function for using different voices for characters and narration
Audio Transcoding to multiple formats (mp3, opus, etc.)
About 50 Gradio interface themes
Custom start-up settings
Clear console output for troubleshooting
Binds to all available IP addresses (0.0.0.0)
Fully customizable Global API settings
Retrieval-based Voice Conversion (RVC) pipeline

Documentation and Support

Built-in documentation with web interface
GitHub Wiki documentation

Performance and Optimization (Depending on TTS engine used)

DeepSpeed integration for 2-3x performance boost
Low VRAM mode for systems with limited GPU memory

Voice Customization and Enhancement

Model Finetuning for improved voice reproduction
XTTS Multiple audio sample TTS generation for better voice reproduction

Bulk Operations and Management

Bulk TTS Generator/Editor for large-scale audio production

API and Integration

Comprehensive API Suite
OpenAI-compatible endpoint/API for broader software compatibility
JSON call support for third-party applications

Experimental Features

Multi Engine Manager (MEM) for running multiple TTS instances simultaneously & queuing requests between them.

Screenshots

Screenshots are available here

🟥 Platform-Specific Notes

Windows

Requires Git, Microsoft C++ Build Tools, and Windows SDK.
DeepSpeed works with NVIDIA GPUs.

Linux

Requires specific packages based on your distribution (Debian-based or RPM-based).
DeepSpeed works with NVIDIA GPUs.
Limited experimental support for AMD GPUs (mainly for XTTS).

Mac (Theoretical)

Installation process is untested and theoretical.
No GPU acceleration for AllTalk TTS engines.
Some TTS engines may have limited or no support on Mac.

For more details on Mac support limitations, please refer to the Mac Support Disclaimer.

GPU Support

GPU support is provided by the developer of the individual TTS engine. If their TTS engine support's X GPU, then I can support X GPU, if it doesnt support X GPU, then I cannot support X GPU. Most of the engines will run on CPU, but some may be very slow on CPU.

NVIDIA GPUs: Full support on Windows and Linux.
AMD GPUs: Limited experimental support on Linux (mainly for XTTS).
Intel ARC GPUs: No specific support currently.
Apple Silicon (M1/M2): No GPU acceleration for AllTalk TTS engines currently.

🟩 Quick Setup (Recommended for most users)

For a fast and straightforward installation and recommended:

Standalone Installation
- For users who want to run AllTalk TTS as a standalone application.
- Available for Windows and Linux.
Text-generation-webui Installation
- For users who want to integrate AllTalk TTS as a part of Text-generation-webui.
- Available for Windows and Linux.
- Includes information on the optional/alternative TGWUI Remote Extension.

These methods use scripts that automate most of the installation process, making it easier for users to get started quickly.

🟩 Manual Installation

For users who prefer more control over the installation process or need to troubleshoot:

Manual Installation Guide
- Detailed step-by-step instructions for manual installation.
- Available for Windows, Linux, and Mac (theoretical).
- Recommended for advanced users or those with specific setup requirements.

🟩 Google Colab Installation

For users who want to run AllTalk TTS in a cloud environment:

Google Colab Installation
- Instructions for setting up and running AllTalk TTS in Google Colab.
- Ideal for users who want to try AllTalk TTS without installing it locally.

🟪 Updating

As long as you did the git clone method to setup initially, you will be able to go into the folder and use git pull to download updates.

🟨 Diagnostics Help with Issues/Start-up problems etc.

If you are having issues with starting AllTalk, it may well be because some of the 3rd Party packages versions have changed, or something is not right in your Python environment. Whilst its impossible to constantly ensure that everything is going to work perfectly, after installation, you can use the diagnostics tool to:

Generate a diagnostics.log file which contains information about your Python environment setup and performs various checks to ensure everything is installed.
Identify possible issues by comparing your diagnostics.log file to the AllTalk base basediagnostics.log stored in the alltalk_tts/system/config/ folder.
Provide some semi-automated repair of your Python environment.

Expand here for instructions

Starting diagnostics

Start the diagnostics from the alltalk_tts folder with either:

Windows: start_diagnostics.bat
Linux: ./start_diagnostics.sh
TGWUI: use TGWUI's cmd_{your_os} file
Other: python diagnostics.py after starting your Python environment

You will be presented with a menu. The first thing you will need to do is generate your own diagnostics file, with option 1. This will create your diagnostics.log file in the alltalk_tts folder.

Contents of the `diagnostic.log` file

You are welcome to look through this file and also check the on-screen output for failure notifications or package version issues.

Comparing your `diagnostics.log` to the Standalone `basediagnostics.log`

Back at the main diagnostics menu, you can compare your diagnostics.log file to the basediagnostics.logfile. This comparison will show any version differences between your Python environment and a tested working Python environment, as well as provide the commands to align your environment with the tested environment.

To do this comparison you will:

Select option 2 from the diagnostics menu and wait for the GUI to open.
Drag and drop basediagnostics log from the /alltalk_tts/system/config folder onto the Base Diagnostics File window.
Drag and drop your diagnostics log from the /alltalk_tts/ folder onto the Comparison Diagnostics File window.
Click the Compare the Base and Comparison log files button.

You will now see a comparison of the Base and Comparison versions listed in chart form.

Windows Users note at the top of the GUI window, there are reference to Windows C++ Build Tools, Windows SDK and Espeak-ng. These are part of the base requirements and if missing you should install them as the installation of AllTalk's Python environment will have failed.

At the bottom of the GUI screen you will see:

Organised Results this is the chart above, broken down into a text format and useful for quickly assessing what may be different from the base and useful if you need to create a issues ticket. Though the main thing required for a issues ticket is the diagnostics.log file.
Pip Commands to align versions this list can either be copied to manually use at the command prompt/terminal window in your Python environment. Or, if you are in the AllTalk Python environment, you can use the Run Pip commands and that will install all updates to try match the versions. After doing this you can re-run the diagnostics, generate a new diagnostics.log and perform the compare again.

Things this will not resolve or show

Corrupted packages or a corrupted Python Environment You can always delete your Python Environment and start afresh. It may be worth clearing the PIP cache too (as below) before starting this process.
Corrupted files in your PIP download cache Python caches installable packages so that you dont have to re-download them all the time. Sometimes these get corrupted or even sometimes, PIP will not update versions to newer versions when it finds there is already a copy in the PIP cache. You can clear the pip cache at your termina/command prompt window with pip cache purge
Corrupted Conda packages There are 2x packages installed by Conda. In the Standalone installation of AllTalk, you can re-install these manually if you wish by:
         - Running start_environment as necessary for your OS, from the alltalk_tts folder.
         - cd alltalk_environment
         - cd conda
         - cd scripts
         - conda.exe install -y conda-forge::ffmpeg
         - conda.exe install -y pytorch::faiss-cpu
Other environmental factors I cannot account for

🆘 Support Requests, Troubleshooting, BETA Discussions & Feature requests

Documentation & Known Error codes, please refer to the built in documentation or the Wiki here .

If you wish to code something yourself though, thats perfectly to do and youre welcome to discuss that with me if needed.

General discussions on the BETA should be here in the discussion board

If you have a specifc technical problem, please open an issue ticket here in the issues area.

Please note, my available time has become VERY limited due to unexpected family commitments. So please DYOR, look at the Wiki here and refer to the TTS manufacturer (Links in the Gradio interface) for issues specific to THEIR TTS engines.

README.md

AllTalk TTS v2 BETA