-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Difference in Flux scheduler configuration max_shift #10675
Comments
oh yeah not intentional! do you want to help us change? the config in scheduler is correct, so have should not affect the results https://huggingface.co/black-forest-labs/FLUX.1-dev/blob/main/scheduler/scheduler_config.json#L7 |
the value is here, too: Might still not get used as you say, if |
…ingface#10675) This PR updates the max_shift value in flux to 1.15 for consistency across the codebase. In addition to modifying max_shift in flux, all related functions that copy and use this logic, such as calculate_shift in `src/diffusers/pipelines/stable_diffusion_3/pipeline_stable_diffusion_3_img2img.py`, have also been updated to ensure uniform behavior.
…) (#10807) This PR updates the max_shift value in flux to 1.15 for consistency across the codebase. In addition to modifying max_shift in flux, all related functions that copy and use this logic, such as calculate_shift in `src/diffusers/pipelines/stable_diffusion_3/pipeline_stable_diffusion_3_img2img.py`, have also been updated to ensure uniform behavior.
Describe the bug
Could you please check if the value of 1.16 here...
diffusers/src/diffusers/pipelines/flux/pipeline_flux.py
Line 78 in 658e24e
...is intentional or maybe a typo?
max_shift
is 1.15 both in the model configuration...https://huggingface.co/black-forest-labs/FLUX.1-dev/blob/main/scheduler/scheduler_config.json
...and in the original inference code by BFL:
https://github.com/black-forest-labs/flux/blob/d06f82803f5727a91b0cf93fcbb09d920761fba1/src/flux/sampling.py#L214
Reproduction
Logs
System Info
Who can help?
@yiyixuxu @DN6
The text was updated successfully, but these errors were encountered: