-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cant run xtts webui #70
Comments
Just upgrading pip helped for me |
Personnally, i have same error on starting start_xtts_webui.bat, during install.bat, i have this error about jamo :
|
I manually put jamo 0.4.0 in site-packages, looks working for me :) |
Took me several hours, but here's what got it started for me: Start a console from
Close console.
Close console.
Now, I did get the error:
But I exited the console anyway, ran Best of luck. |
Thanks that worked for me too !! I had the same problem with installing jamo 0.4.0 |
wasn't expect it to work...but it works |
|
I also had this exact same error. It seems like failure to install jamo causes the entire installation script to cancel the rest of its process. Anyway, i also had another problem which was that activating the virtual enviroment didn't allow me to use pip.exe (Claiming that file cant be found) Anyway, this can be circumvented by simply doing a cmd pip install with --target your\path\here\xtts-webui-main\venv\Lib\site-packages Anyway, once you get to the requirements text you can also do that by simply doing: |
Absolute legend. I signed up for an account just to say thank you! It worked. No idea what I did there but it worked. |
Traceback (most recent call last):
File "G:\TTS\xtts-webui-main\app.py", line 1, in
from scripts.modeldownloader import install_deepspeed_based_on_python_version
File "G:\TTS\xtts-webui-main\scripts\modeldownloader.py", line 4, in
import requests
ModuleNotFoundError: No module named 'requests'
also during pip install requests i get this
DEPRECATION: omegaconf 2.0.6 has a non-standard dependency specifier PyYAML>=5.1.*. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of omegaconf or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at pypa/pip#12063
The text was updated successfully, but these errors were encountered: