Closed Yaffa16 closed 2 months ago
Open up your command prompt from the Windows start menu. Move into the alltalk_tts folder and run the batch file. You will then be able to see whatever error message there is, rather than it closing the command prompt before you can read/see the error message or reason that its not running.
Thanks, I was able to get it running
🔴 If you have installed AllTalk in a custom Python environment, I will only be able to provide limited assistance/support. AllTalk draws on a variety of scripts and libraries that are not written or managed by myself, and they may fail, error or give strange results in custom built python environments.
🔴 Please generate a diagnostics report and upload the "diagnostics.log" as this helps me understand your configuration.
https://github.com/erew123/alltalk_tts/tree/main?#-how-to-make-a-diagnostics-report-file
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behaviour:
Screenshots If applicable, add screenshots to help explain your problem.
Text/logs If applicable, copy/paste in your logs here from the console.
Desktop (please complete the following information): AllTalk was updated: [approx. date] Custom Python environment: [yes/no give details if yes] Text-generation-webUI was updated: [approx. date]
Additional context Add any other context about the problem here.