-
-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
closed #420
Comments
@quakeman00 Have you read my statement on Support and why I am restricted/cannot spend all my time supporting people? Do you mean like these on the Wiki? https://github.com/erew123/alltalk_tts/wiki/Install-%E2%80%90-Standalone-Installation#quick-setup---video-guide And the new version has very clear documentation on every page: What exactly are you installing into/which guide are you following? If you are following the Standard installation, you shouldnt have any messages about "fairseq-0.12.4-cp311-cp311-win_amd64.whl is not a supported wheel on this platform" which would typically come up because you are installing it in a non Python 3.11 environment OR trying to install into a non-windows environment. You are welcome to post the full error up and explain what exactly you are doing and Ill help you thorough it. |
Hi @quakeman00 Please glance the over the quick intro to Python environments this may explain that to you and it a 2 minute read. Because AllTalk is installing so many requirements for so many TTS engines, the requirements have to be carefully managed as other software may upgrade/downgrade packages causing instability, conflicts, so many unknown situations. This is unfortunately the way Python is. The reason you don't hand out zip files is due to both the size it would need to be e.g. here is the Python environment folder that AllTalk needs/would be built for its environment by atsetup (10GB): And, because of the open nature of Python code, and packages, they settled on Python PIP as the manager, which is a messy sod at times dealing with conflict resolution issues. Down the chain of AllTalk there is probably code from 1,000-2,000 other projects that PIP figures out what works with what and what to do if one of those people update/change their code because of a bug or security issue (this is called dependency resolution). In short its a complicated mess, but, it is the way Python code/scripts work. The utility atsetup.bat or atsetup.sh will create its own custom python environment. It should just be loaded at a normal command prompt or terminal, not in a currently loaded Python virtual environment, just a plain old command prompt. e.g it should look exactly like this when you start out: Over the next few days I will be updating atsetup.bat and atsetup.sh to not only log out its progress, but also carry a little bit more reporting on errors/issues it may encounter. Youre welcome to get me a screenshot of an error code or copy/paste the text, typically this would be say the final 10-20 lines of the error. Re Discord or similar.I would still have an overhead to manage it at a base level. Hopefully some other people will come on board one day and want to take on that responsibility, but I just have too much on my plate at the moment. So the slower pace and one central point of contact allows me to deal with things a bit easier. However, people do respond on the Discussions forums, so you can always post there. Let me know. Thanks |
Hi @quakeman00 I think I have it figured based on the above. I am going to make some assumptions from that error which are:
Installing AllTalkBe it that the 2nd one is correct or not, Ill tell you the fix and then I will tell you the why.
to looking like this:
Once you are have cloned the alltalk_tts folder and then in your command prompt moved into that folder, you will run And then Install AllTalk as a Standalone Application This will create a full custom python environment and do all the things necessary. It should run through to the end without any problems and you should get a screen at the end of that installation which says something like this: That will be AllTalk installed as a standalone. When you want to use AllTalk, you will go into its folder and run "starts_alltalk.bat` Getting AllTalk working with Text-generation-webuiNow that AllTalk is running, I am assuming you want it working with Text-generation-webui? To do that you will follow the installation instructions for Text‐generation‐webui Remote Extension This will install a small extension into TGWUI, that has all the functionality etc. What has the issue beenThe atsetup, when running the "Text Generation Webui" install, and not the "Standalone Installation", the TGWUI installation will NOT install a custom Python environment, because you would be installing into TGWUI's custom Python environment. Because TGWUI's custom Python environment's package requirements have moved its version requirements so high up, Installing Alltalk's main installation directly into its Python environment would damage it. I reference this issue https://github.com/erew123/alltalk_tts/wiki/Install-%E2%80%90-Text%E2%80%90generation%E2%80%90webui-Installation#read-before-installing-into-tgwuis-python-environment And here #377 Hopefully that will answer your question and get you up and running. If so, please feel free to close the ticket. Once you are up and running, you can check things like the quick start guide to help you though any initial questions https://github.com/erew123/alltalk_tts/wiki Thanks |
This error message here???
where at the bottom of the error message it says: with cmd_{yourOS} before running atsetup.bat? This is the error message you are getting still? |
Ok. At no point should you be using that menu option: I assume you DID remove the AllTalk folder that you had previously created? (from my instructions above): And then you install the TGWUI remote extension (from my instructions above): Please follow these instructions TGWUI remote extension (from my instructions above): Thanks |
I dont understand what you mean by where does it spawn. The instructions in for the TGWUI Remote extension tell you to create that folder: In the TGWUI Instructions it EXPLICITLY says what to do and links to the relevant sections: It repeats that instruction, on the same page to draw your attention to it: Nowhere in the instructions for Standalone installation OR the TGWUI Remote Extension does it tell you to go back into the installation utility Do you think I need to explicitly caveat that? |
If you are using Text-generation-webui from Oobabooga https://github.com/oobabooga/text-generation-webui that is the standard folder name it will create when you follow their installation instructions. https://github.com/oobabooga/text-generation-webui?tab=readme-ov-file#how-to-install |
If you are NOT using Text-generation-webui, then you wouldn't follow the instructions for that. |
You don't need another one! If you just want it to use it with SillyTavern, you just want to install it as a Standalone. https://github.com/erew123/alltalk_tts/wiki/Install-%E2%80%90-Standalone-Installation TGWUI is a completely different thing. No-where in the Standalone instructions does it say to install the TGWUI requirements, or install it in Google Colab, or Docker etc. This is an Options list that you pick the option you want/need to match your requirements: If all you want it AllTalk to work with SillyTavern and you have whatever backend loader for your AI model (OpenAI, Claude, Kobold, TGWUI, whatever) you can just install AllTalk as a Standalone install and it will speak to SillyTavern which and SillyTavern will speak to your AI model however you set that up. AllTalk is used across 50+ different projects on the internet, its not just for SillyTavern, so I cannot caveat every individual persons custom scenario on a - If you have XX and Also YY and want ZZ then you need to install ABC way. Unfortunately that is far too complicated for me to cover every scenario for every person. I will take on board what you say though and what you found difficult and think about how to re-visit it. Though I did check the Sillytavern documentation and it does state the choice in their documentation https://docs.sillytavern.app/extensions/alltalk/ which is explicit instructions for SillyTavern and links to the correct AllTalk instructions as you need. Are you at least up and running now? |
Please go to this link and click the download (as shown in the image below): https://github.com/erew123/alltalk_tts/blob/alltalkbeta/system/TGWUI_Extension/script.py You want to save that over the top (replacing) the other That will solve your first problem. As for your second problem, have you looked at the quick start guide?: https://github.com/erew123/alltalk_tts/wiki/AllTalk-V2-QuickStart-Guide Each TTS engine has various locations for different things and there is help throughout the whole of the Gradio interface. Typically most voices are stored in the voices folder. As mentioned in the quickstart guide, you can press Ctrl+left click on the clickable links to to open it: Each TTS engine has its own help page/guide e.g. And pretty much every single page in the interface has an expandable help section detailing what is on that page and how to use it: Beyond that, the Wiki is full of lots of other information. |
I just wanted to comment - that Alltalk's install and download - as well as the UI for training has a been a breeze to work, max appreciate. And dev showed so much patience on this thread x.x |
I know...dev needs an award for sticking this one out, lol... |
nope
The text was updated successfully, but these errors were encountered: