-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
After updating WebUI 1.8, Sadtalker error appears and the tab is not visible #822
Comments
same here |
same here. Sad talker not working after updating to |
If you upgrade from v1.7 to v1.8 Automatic1111 then it's ok as long as you DON'T upgrade torch & xformers (by running webui.bat with --reinstall-torch --reinstall-xformer) SadTalker works ok with version: v1.8.0 • python: 3.10.13 • torch: 2.0.1+cu118 • xformers: 0.0.20 I find that Automatic v1.8 runs about 25% faster than v1.7 for image generation, haven't tested speed difference of SadTalker, so yeah would be good to have SadTalker work with the latest v1.8 and latest torch & xformers. |
Why cant sadtalker just upgrade to the latest torch and xformers |
Python 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:38:17) [MSC v.1929 64 bit (AMD64)] - np.complex_ was a deprecated alias for the builtin complex. To avoid this error in existing code, use complex by itself. Doing this - will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use np.complex128 here.
- The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:
- https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations |
is there a plan for sadtalker to be compatible with v 1.8? |
The bug seems not to be with SadTalker, but with the librosa python library. You can fix it by first finding the file "constantq.py" in your venv directory: venv\lib\site-packages\librosa\core\constantq.py Stop your WebGUI. Then edit this file and find the line 1058. It should read: dtype=np.complex, which is outdated and causes the error. Change that to: dtype=complex, Save and restart your WebGUI. Now, everything should start without error and the SadTalker tab re-appears. WARNING: This may cause problems at a later point in time when the librosa library is updated. Or maybe it won't, I don't know. Just be careful and make a backup before changing stuff :-) |
Thanks Buddy working perfect |
thanks buddy
|
THis worked and allowed the Sadtalker to be in the tab again but there is an error |
i am running webui forge. is it possible to install a stable diffusion webui 1.7 with sadtalker on the same drive as a standalone version? where do i get the older installation files? |
I upgraded librosa (command: python -m pip install -U librosa) to the latest version (0.10.1) and found it fixed. |
it works.well done,thanks. |
Sadtalker will show again in the tab after fixing with the work arounds mentioned above but if you try to click generate another error will appear: AttributeError: module 'numpy' has no attribute 'float' |
To resolve the issue with Sad Talker in the WebUI, please follow the instructions below: Changes in
|
Its working fine now. Thx. I used https://www.sublimetext.com/download_thanks?target=win-x64 because IDLE 3.10 64 bit cant open my_awing_arch.py in my win 10 pc. Sadtalker is now running fine in version 1.8. Im just wondering: is it that hard to just update sadtalker so that we wont have to edit the .py files manually? Im not a programmer so i have no idea |
@AppStolz Thanks for providing the fix. Seems firstly need to fix venv/Lib/site-packages/librosa/core/constantq.py line 1058 as mentioned by @Zhjhp2020. And I suspect updating the venv's librosa version to 0.10.1 as mentioned by @Timo9Madrid7 on thread #862 also work tho I didn't try. Otherwise it will give the following when importing librosa *** Error executing callback ui_tabs_callback for D:\PycharmProjects\CSCI-E104-FinalProjTest\stable-diffusion-webui\extensions\SadTalker\scripts\extension.py After that, it will still say various np.float problem as you described and your solution helped fixing that. my librosa is |
Hey, thanks for all the info and tips. Sadly this all doesn't fix it for me. I have updated librosa, no success. I have done the mentioned changes, no success. I am still stuck with the "complex" error. EDIT; also tried the pull request here: #869 Any further ideas? |
Could you please visit to If you have updated Otherwise, you have probably updated |
Gotcha. The global pip is version librosa 10.1. But when calling from the console in the venv of stable-diffusion-webui it told me librosa version 0.8.0. I have updated it with python -m pip install -U librosa now. And now it shows version 0.10.1. And now i have my sadtalker tab and no errors anymore. Many thanks. This solved it for me :) |
This is correct. I don't have a Windows machine and cannot reproduce it. It should be related to the environment. Your library should still be incorrect |
I see you solved it. Sorry for the late reply |
Great solution!!!
Replace this line with:
|
holyshit, it works in sd 1.9.4 |
Tried like every fix here its still not showing |
Applied all fixes, no more errors in the console but the SadTalker tab is missing. |
After updating webUI 1.8, Sadtalker error appears and the tab is not visible in the webUI.
Is there any solution for this?
The text was updated successfully, but these errors were encountered: