Fix the issue where SadTalker cannot be used on Stable Diffusion webui 1.8.0 #869
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
修正np版本不同的float类型
修复np版本不同，类型不同的问题
更新版本，支持`np.complex_
kingljl
changed the title
|
this works. please approve this commit |
It's been a while since the official update, so it's probably not possible to merge in the short term. It can only be found and used by whoever finds it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For specific details, update to 1.8.0 using SadTalker with an error message np. complex, and then upgrade librosa to 0.10 Subsequently, we encountered an issue with "AttributeError: module 'numpy' has no attribute 'float'" and updated the code to np.float32
Then we encountered the issue of "alueError: setting an array element with a sequence. The requested array has an inhomogeneous shape after 1 dimension. The detected shape was (5,)+inhomogeneous pa". In response to the error message, we added the dtype attribute of np. array, and now it is running normally
The effect of the final normal image：