Windows version first release about weeablind HOT 14 OPEN

Hi there! First of all, may I know if you're running the release version (the exe) or building it from source with Python? If you don't have ffmpeg installed on your system and in your system path, it will prompt you to download it and add it to the path automatically. Also, your GPU will only be shown as detected if you have the Coqui TTS module installed (i.e. pip install tts ) as well as have CUDA set up properly on your system. You can read the SO thread in the readme to set that up.

from weeablind.

Thanks for the reply. I am using the exe version, and yes, it did prompt me to install FFmpeg, but it's still saying that it's not installed even after I closed and reopened the application; I should have CUDA already set. I use it for some llm, but I need to install the TTS module

from weeablind.

Oh wow, okay I just tested it, and it worked fine. When it finishes downloading ffmpeg, do you have an ffmpeg folder in the output folder and a "install.crumb" file or something like that? If it finds that, it shouldn't prompt you.

from weeablind.

Yes, FFmpeg and install. Crumb was in the output. it wasn’t giving me a prompt. It was just saying that it couldn’t be found

from weeablind.

Yes, they are bought in the folder, but it’s saying that FFmpeg could not be found or avconv

from weeablind.

As in in the terminal like you're getting output errors? Usually I think pydub will run a check and say that because it gets included before the code that runs to add fmpeg to the path, but even when it does that, it still works if it's installed in the output folder.

from weeablind.

If there is a script that I can use to install all the requirements in one go, I keep running into errors

from weeablind.

I will try to rebuild the requirements windows to be more robust and test it on another machine. The thing is, there are a few projects that run into conflicts that sometimes you'll get errors about that don't actually matter like protobuf or librosa but pip still acts like a nonce about it. I need to learn a better way to manage that with like conda or something? Wish I knew someone who knew the best way for managing lots of dependencies like that. Generally though, you should be able to install all the features you want individually (i.e. coqui, spleeter, pyannote, etc) without issue. And when something breaks usually it's because of like one package you can just forcefully install or install with --no-deps or something. I'll look into it again. So sorry for the persistence of this issue

from weeablind.

That's one of the problems. That has happened when I try to install the requirements of different parts that need different versions of the same program. I don't have the skill required to fix the problem, so I use an LLM sometimes but then run into other problems

from weeablind.

@ArtyomVancyan created issue #3 and might have some insight into fixing these problems? I'm going to play with it right now though and see if I can get something better

from weeablind.

Any assistance would be much appreciated.

from weeablind.

Lol trying to reinstall everything to test and all my drives are completely full xD might be a couple days. Need to reinstall my OSes anywways

from weeablind.

Ok latest commit might fix some issues. It seems there's a new fork of Coqui being maintained more actively. Installing straight from requirements.txt just worked on 3.10. If that doesn't work, try installing requirements-win

from weeablind.