AttributeError: module 'ffmpeg' has no attribute 'Error' #16
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#16
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?
Getting this whenever I try to start training, I followed the instructions here but it's not made a difference. Here's my output after following those instructions:
I also added ffmpeg to my /bin/ folder as instructed here
Using
bbc2d26289
on Windows 10, R7 5700X, RX 6900 XTXH, 16GB RAM.Many thanks.
Any way you can zip up and send your
venv
folder? I might be able to figure it out if I can probe the current state.Actually, not to rain on your parade, but, on Windows at least, finetuning/training is only on Nvidia cards, as I haven't been able to find a way to cram DirectML wrappers into DLAS yet.
While it doesn't exactly solve your issue, it'd be best to use a Colab notebook to train, as you're most definitely going to run into being unable to train with your AMD card, on Windows at least (until I find a way to get DLAS to use DirectML, which may not even work).
I assume training works for AMD on Linux then?
I've attached my venv folder anyway.
https://litter.catbox.moe/hyyx4h.7z
Should be, I haven't tested it, but if it's anything like getting tortoise-tts working under ROCm, it's just as easy as running
./setup-rocm.sh
and making sure you already have ROCm drivers/runtime installed.Took a small bit of elbow grease to get it to work (for simplicity I just thrown it at
C:\Tortoise\ai-voice-cloning\
so I don't need to edit some paths, and had to edit.\venv\pyvenv.conf
with my python39 path) and did get it to replicate, but I humored myself with just running:And it worked:
I'll zip the venv back up and send it to you.
Thanks very much for your prompt response.
I might have to download a Linux distro and test it there, if you think it should work with GPU accel
Almost forgot the venv. Should be as easy as deleting your old one and dropping this in place.
The hardest part is actually getting ROCm drivers/runtime working, since it didn't seem to work at first on an Arch Linux flavor I had used. I imagine on a Debian/Debian-variant it'd be easy peasy.
Thank you bud, that's resolved it.