Import error: Failed to load PyTorch C Extensions #1
Labels
No Label
bug
duplicate
enhancement
help wanted
insufficient info
invalid
news
not a bug
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: mrq/ai-voice-cloning#1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As it says in the image, I tried running start.bat after running the setup for CUDA and this happened, I've been running https://git.ecker.tech/mrq/tortoise-tts reasonably fine so I wanted to try moving over to this one but ran into this error, the other one still works no bother.
Strange, I'll see if I can replicate it. I admittedly haven't tested setting up from a clean slate after cleanup, so I'll pick at it when I get a chance.
For the meantime, you can copy-paste whatever's under the
./tortoise-tts/tortoise-env/
folder inside the./ai-voice-cloning/venv/
folder, to effectively just reuse the venv. And copy the./models/
folder from the old to the new.Right now, there's no real reason to use this over the old repo, as I haven't done any functional changes yet, and the old repo should still be functional to work out of.
Couldn't replicate, although I did find it was bitching at me for not having
psutil
installed.I keep getting the same message, I've tried reinstalling all the packages, doing the exact instructions in the error message, installing different packages, sorting out dependenct conflicts, changing the imports in the code but it wont budge, both versions now give me the same error message which does suggest its something to do with my pytorch or something like that, but all I did was install the versions listed in the readme/re-entry so idk anymore, keep up the good work anyway we need locally hosted AI voices.
Ok, for some reason deleting the folder and re-cloning the repo fixed it, I'm sure some part of my reinstalling various packages and python itself might have helped but either way it works now, good work!
Ah, good to hear it was resolved. I wonder if you happened to clone the repo at a bad time and it bungled up things.
Just in case this happens in the future for you or anyone else again, I suppose I'll cobble together a ready-to-use ZIP (for Windows) to fall back to.
Funny enough just now, I ran into something similar in a Colab notebook, but I needed to restart the runtime for it to get "fixed". I don't think that exactly is a solution for non-Colab environments, but I thought I'd note it somewhere.