Replies: 6 comments 10 replies
-
Actually it is supposed to do that. If conda and pip are working correctly, all of the pip dependencies during install should be within the tts-webui folder, not outside. However, some features always get made that use some 'user' cache, like C:/Users/user/.cache or app_data etc etc and you only realize that by checking the internal code. I.e., the official and original bark uses .cache due to huggingface's 'download' implementation.
Thanks, I will make an issue for adding more feedback on gradio/React about what is visible in the console: #488
Yes, at this point I think I have the capacity to improve the UX for changing the cache location. One note - for better or worse, most projects such as Audiocraft, Bark, Tortoise etc have adapted this pattern for the last 2+ years. I think as a webui I should explore ways of 'patching' these features. I will review more later. |
Beta Was this translation helpful? Give feedback.
-
By the way - one note - SD webui does download some transformers to HF Cache last I checked. |
Beta Was this translation helpful? Give feedback.
-
During installation, ask the user where to put the various extra folders (Hugging Face Cache, Torch Hub Cache, others?) and suggest reasonable choices (e.g. either a location to keep the application self-contained, the default location in the home folder or a custom folder) I really like this idea - here's an issue to track it: #489 |
Beta Was this translation helpful? Give feedback.
-
I think I had some info on it, but originally I wanted to convert everything to React. React is meant to be the definitive while gradio is meant to be the uncomfortable pro barebones mode. |
Beta Was this translation helpful? Give feedback.
-
Thanks for taking my feedback in account. One extra thing:
The "output.log" file doesn't seem to give more details but I can provide it if needed. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
After reading #186, I'd like to add to this topic as a Windows user with little space on their C drive.
I've used a few other generative AI tools (e.g. https://github.com/oobabooga/text-generation-webui, https://github.com/lllyasviel/Fooocus/, https://github.com/lllyasviel/stable-diffusion-webui-forge) and expected a similar experience with this one.
I really appreciate the one-click installers and having the whole tool and dependencies being contained in their own folder.
However, the experience was slightly different with this tool:
During the install, pip was downloading and building packages in my temp folder (on C:). I had enough space left but it used about 10 GB and that could have been an issue. I don't think other AI tools did that (but I may have not noticed). Opting to install all the dependencies at once probably amplified the storage required.
If there's a way to tell pip to use a specific working folder and set that to a temp folder inside tts-generation-webui's folder, that would be great.
So far, I've only tried Bark and MAGNet and mostly used the React UI.
I figured that Bark models go in the "voices" folder but I got a bit confused when trying to use MAGNeT. The React UI or the terminal didn't provide any info when I first attempted to generate something with MAGNeT, until it suddenly started to download files (which was only visible on the terminal) and eventually generated what I had requested. I think some feedback was missing there.
Also, while I expected the downloaded files to be put somewhere inside the tts-generation-webui's folder (just like "voices"), I eventually realized they were created on my C: drive and found the HuggingFace cache folder.
This lead me to find #186 and wonder what would be the best way to change the environment variables.
Just now, I've found that the Gradio interface allows setting the environment variables and hope that it will solve my problem. I still have to figure the format to make it a relative path. I didn't find that setting in the React UI.
Even though it can be set later, I think the cache locations is something that should be asked when launching the tool for the first time.
Proposed solutions to improve the first launch experience:
Anyway, thanks a lot for your work on this project, it's very appreciated.
Beta Was this translation helpful? Give feedback.
All reactions