-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[bug] Fix float/int guidance scale not working in StableVideoDiffusionPipeline
#7143
Conversation
Nice catch. We should definitely add a test case for this as well here: https://github.com/huggingface/diffusers/blob/main/tests/pipelines/stable_video_diffusion/test_stable_video_diffusion.py. @yiyixuxu WDYT? |
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good 👍🏽 I think a test to check disabling cfg would be a nice addition.
@DN6 Added a test, let me know how it looks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking solid. Thanks!
@DN6 feel free to merge once you're good! |
Side note: I was looking at the tests and see that the test config sets both height and width 32. It's probably a good idea to change those to different numbers to catch shape errors where the height/width are switched mistakenly. |
Welcome you to add them in a separate PR. |
What does this PR do?
fa3c86b caused a regression in the support for disabling CFG. Specifically,
do_classifier_free_guidance
was no longer returning a boolean value and causing the following error when using max_guidance_scale = 1.Adding this change allows the pipeline to run without error.
Before submitting
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Tagging @patrickvonplaten who wrote the original commit.
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.