Closed LaptopDev closed 8 months ago
Hi @LaptopDev
I've tided up the documentation so hopefully this will clear things up for you and others. In short though, when running as a standalone:
atsetup.sh
will create a custom python environment, specifically for AllTalk.start_environment.sh
will start that environment when run from the alltalk_tts folder.Please check on:
Understanding Python Environments Simplified in the help section DeepSpeed Installation options here
Hopefully these should cover off anything else you need (as mentioned, I've updated them).
Thanks
@erew123 Thank you for the added clarification for the deespseed installation.
I was able to print cuda version 12.1 following your update to the deepspeed standalone installation instructions and installed deepspeed after both entering the environment with 'start_environment.sh' and setting the environment variables. However, when I attempted to run ./start_alltalk.sh within the environment, I am now missing some packages, which wasn't indicated previously running start_alltalk.sh (outside of the environment?). Am I supposed to exit the environment before running ./start_alltalk.sh ?
Thank you for your last prompt response and helping me with this. My estimation is I should uninstall alltalk because I surely messed up the requirements, re-install and follow the deepspeed instructions, but just exit the environment before running ./start_alltalk.sh.
Hi @LaptopDev
There is no need to exit the environment, if its the Python environment you want to use, however, just as a point of reference, you exit a conda built environment with conda deactivate
or close the terminal console and open a new one.
As for your missing packages that is very strange. I don't have Fedora nor have I tried AllTalk on it, though the Python libraries are typically universal across Windows, Mac and Linux variants, so there should be no issues there.
First off to get AllTalk working you have 2x things I would suggest. You can either start the environment ./start_environment.sh
and then run pip install -r requirements_nvidia.txt
(I am assuming you have an Nvidia card, I dont know) and that will refresh the installation requirements.
OR
Start ./atsetup.sh
not in the environment, and select option 2 Delete AllTalk's custom Python environment
and then select option 1 to rebuild the Python environment. This is pretty much the above process, but with a complete rebuild of the environment. This will require DeepSpeed installing again.
Either option would be pretty quick this time around, as the packages should already be downloaded and stored in your PIP cache. I would look in the logs for a "cant download/cant find xxxxx` package.
However, saying that, you can run ./atsetup.sh
and run the diagnostics, which will give you an overview of your environment both on screen and more indepth in the diagnostics.log
file it generates.
Thanks
Hi @LaptopDev
To fully answer the question, does AllTalk have any issues with Fedora or Red-Hat based systems, also to confirm my re-write of the instructions in the documentation, I have gone through a Fedora virtual machine installation and tested. I have taken screen grabs throughout the process and you can see all the steps here
My conclusion is that there are no issues running AllTalk on Fedora and I would suggest you follow my earlier steps and rebuild the AllTalk Python environment & check your system for any conflicting issues within your configurations.
Thanks
@erew123 Thank you for helping me! My cause for confusion I think occurred because I was assuming requirements_nvidia.txt was installed after selecting my gpu as nvidia using the atsetup.sh program, which I corrected by using pip install -r requirements_nvidia.txt in the order you describe here and in your new Fedora installation guide. That really cleared it up with the simple graphical guide. Feels like I got special treatment 😄 , but I am sure that will aid others. Thank you for your attention.
I've initiated the alltalk_tts app with
start_alltalk.sh
after installing alltalk withatsetup.sh
and can access alltalk's WebUI, but I'm uncertain about theatsetup.sh
deepspeed installation which hinges seemingly on creating a conda environment to export a env var to set my cuda path to a secondary cuda installation.Main points:
.bashrc
./usr/local
.atsetup.sh
may handle it.CUDA_HOME
and executestart_environment.sh
/conda activate alltalkenv
.python venv
.Questions:
atsetup.sh
, or is it managed by the script?CUDA_HOME
and runningatsetup.sh
?Additionally,
Start the alltalk_tts Python environment 'conda activate alltalkenv'
, but it's unclear for me whether to create a new environment or use one that pre-exists fromatsetup.sh
orstart_environment.sh
.System: Fedora Linux Standalone alltalk_tts
How should I set my environment up and set my environment variables? Any guidance to streamline the setup process would be appreciated. Thank you.