You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using DPMSolverSinglestepScheduler and the function set_timesteps, the resulting timesteps might have two times the same value. A bug occurs when we use the function add_noise. An error is thrown if the value of t appears multiple times in self.timesteps
Setting scheduler.use_karras_sigmas = True does not fix the issue.
I get that the bug might not appear with more carefully chosen parameters, but when loading with default parameters (like SDXL 1.0), it seems to exist. So, just wanted to let you know!
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread.
Please note that issues that do not follow the contributing guidelines are likely to be ignored.
Describe the bug
Hello!
When using DPMSolverSinglestepScheduler and the function
set_timesteps
, the resulting timesteps might have two times the same value. A bug occurs when we use the functionadd_noise
. An error is thrown if the value of t appears multiple times in self.timestepsSetting
scheduler.use_karras_sigmas = True
does not fix the issue.The problem probably comes from the line
I get that the bug might not appear with more carefully chosen parameters, but when loading with default parameters (like SDXL 1.0), it seems to exist. So, just wanted to let you know!
Thank you!
Reproduction
Logs
System Info
diffusers
version: 0.24.0Who can help?
@yiyixuxu @PATR
The text was updated successfully, but these errors were encountered: