Expected String and got Path #251
Comments
|
Hi @ObscenityIB From your screenshot, best I can tell you have installed this as a Standalone? But you aren't using AllTalks custom built Python Environment aka starting AllTalk with start_alltalk.sh? I can see in the start-up its saying PyTorch 2.3.1: [AllTalk Startup] Current PyTorch Version: 2.3.1+cu121 Which will probably have issues to be honest with you. Many of the older requirements may not like PyTorch 2.3.x You should preferably use atsetup.sh to build the custom Python environment, as that builds a tested environment (It will be Pytorch 2.2.x). And then you should also use start_alltalk.sh which loads in the Python environment before starting AllTalk. That aside, I have also released specific wheel files for DeepSpeed on Linux that will work with the AllTalk custom Python environment details here That aside, the BETA of AllTalk v2, that installation is further simplified as you install it as a Standalone (building the AllTalk Python Environment) which will auto install DeepSpeed pre-compiled for Linux. https://github.com/erew123/alltalk_tts/tree/alltalkbeta Thanks |
|
Hi @erew123, thanks for getting back so quickly.
Yes, I installed it as standalone.
I am, you can see that at the start of the log output (
This is exactly how I have installed alltalk, running atsetup.sh, again listed in my steps to reproduce. Thanks for the other notes on DeepSpeed and the pytorch version, I'll try out that beta now. |
|
@ObscenityIB Theres only 1x way I can think you may have ended up with a PyTorch 2.3.x environment then (on AllTalk v1). The pip application that Python uses to download packages will cache copies of software it downloads. If you have downloaded a version of some software before (in this case PyTorch) and you then attempt another download of the same software, but a different version, even though you explicitly say "download X version" it will just re-use the previously downloaded version.... putting that another way..... If your computer downloaded PyTorch 2.3.1 for some other software, PIP keeps a locally cached installer for 2.3.1. When the AllTalk v1 setup goes to install PyTorch 2.2,1, pip just goes "here you go, use 2.3.1", which is very frustrating. You can wipe the pip cache by running Saying that, the v2 beta doesnt use pip to install Pytorch, but |
|
I've never had anything installed via pip, since using pip is outdated and actively prevented by modern operating systems, where pipx is a replacement for pip. I have tried clearing the cache and still had the same issue using alltalk. A terminal recording of the entire installation process, including the issue at the end, is available here: I am currently testing the beta branch, and will see how it goes. |
|
Thanks for that! Makes it much easier to see whats going on. Ok my suggestion is this (with v1 alltalk):
That should downgrade the torch version correctly. Looks like somewhere a > had crept into the atsetup.sh so that will have been what resulted in pulling the 2.3.1 version. After that, you should be able to |
|
Happy to report that the AllTalk BETA worked with no issues :) Afterwards, v1 started working as well. Thanks for your help on this issue. 👍 |
Downgrading dependency versions shouldn't be the correct solution to fix this very simple issue that can be fixed by passing in string instead of Path to torchaudio.save... |
[F] Fix #251: Expected a value of type 'str'
Describe the bug
Tried this a few months ago and had no luck, tried it again today and still no luck.
After installation, generating a test message fails immediately as python seems to not be accepting the output path, or any path for that matter.
To Reproduce
Use
atsetup.shto install alltalk standalone.Activate the environment with
start_environment.sh.Use
atsetup.shto install DeepSpeed.*Run
start_alltalk.sh.Type in some example text and hit Generate.
Text/logs
Desktop (please complete the following information):
AllTalk was updated: 14/06/2024
Custom Python environment: no
Text-generation-webUI was updated: N/A
Additional context
* Unrelated, but enabling deepspeed afterwards causes cuda compilation errors, and alltalk will not start if enabled, as well as creating a random log file named
'=2.2.1+cu121'in the working directory when installed.diagnostics.log
The text was updated successfully, but these errors were encountered: