-
after installing alltalk V2 when i start it and open ( http://127.0.0.1:7852/ ) i got this error on cmd
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
also during the setup i see this error
|
Beta Was this translation helpful? Give feedback.
-
runing 3) Re-Apply/Update the requirements file leaves me with this error at the end
|
Beta Was this translation helpful? Give feedback.
-
Hi @thexwts Here is my suggestion:
This will look like the following: Thanks |
Beta Was this translation helpful? Give feedback.
-
Thank you soo much now its working perfectly |
Beta Was this translation helpful? Give feedback.
-
Today, i just installed the awesome alltalk tts beta using the manual method, and it was working fine for a few generations, but eventually ran into the "ASGI" error. I followed the instructions here. i wasn't sure how to erase the python env on linux, so i just skipped that part and run setup for the server version, which i'm using. all the packages were already installed and up to date except the transformers thing, leading me to believe that it was just the transformers module that wasn't synced properly, possibly indicating the version wasn't correct or up to date somewhere in the manual installation process. it ran fine after the suggested instructions provided above, and without having to wipe the python env. edit: i had a problem when i tried to use parler, it wasn't installed properly or recognized by alltalk beta or gradio. I was given a possible solution in another thread or possibly an email. erew123's response was: first, run start_environment, then: this didn't work, alltalk beta still won't load. think i found a linux bug. i got the error "models/parler" directory was not found. so i went into /models and mkdir parler. this caused alltalk beta to progress further without the "waiting for tts" endless loop. will edit this comment further as necessary. from the tts web interface, i tried to change engines from parler to xtts and it threw errors and crashed. so i started the setup script again, and it seemed to download something again. ok, i tried a bunch of things, force reinstalling stuff, and eventually was able to change the engine to xtts, and it was working, generating WAVS, etc. but since i have parler installed i wanted to try it. now i'm back at square one. alltalk won't load anymore, here is the error log:
|
Beta Was this translation helpful? Give feedback.
Hi @thexwts
Here is my suggestion:
alltalk_tts
folder where you have installed version 2.start_environment.bat
to start the Python environment.pip cache purge
to clear the pip download cache of however many files are in it.git pull
to update any missing files. It may say "Already up to date" or it may download some files.rd /s /q alltalk_environment
to remove the damaged Python environment.atsetup.bat
and assuming you want to install a standalone version, select option 2 and then option 1.ERROR: pip's dependency resolver does not currently take int…