Repository navigation
Replies: 2 comments
|
The error is the small part of the problem — the bigger one is that FluxFill cannot run on Flux is a rectified-flow (flow-matching) model: it was trained to predict the velocity that moves points along a straight path between noise and data, not the DDPM epsilon/VP formulation that What you can actually use with FluxFill, all within the flow-matching family:
scheduler = FlowMatchEulerDiscreteScheduler.from_config(
pipe.scheduler.config, shift=1.15 # higher shift spends more steps near the data end
)
pipe.scheduler = scheduler
If you were after ancestral stochasticity specifically: there is no flow-matching ancestral scheduler in diffusers today, and ComfyUI-style samplers can't be dropped in directly — the model's parameterization would still mismatch. If your real goal was a custom sigma schedule (that's what the exception is guarding), |
|
FluxFill uses flow matching, so the vanilla Use the flow-match Euler instead: from diffusers import FlowMatchEulerDiscreteScheduler
SAMPLER_MAP = {
"Euler": lambda config: FlowMatchEulerDiscreteScheduler.from_config(config)
}If you'd rather just swap the scheduler on an existing pipeline, — |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
I am using the customfluxfill function and want to use the Euler scheduler (EulerAncestralDiscreteScheduler) in my code. However, I am encountering the following error:
Reproduction
from diffusers.schedulers import EulerDiscreteScheduler
SAMPLER_MAP = {
"Euler": lambda config: EulerDiscreteScheduler.from_config(config)
}
Logs
ValueError: The current scheduler class <class 'diffusers.schedulers.scheduling_euler_ancestral_discrete.EulerAncestralDiscreteScheduler'> 's set_timesteps does not support custom sigmas schedules. Please check whether you are using the correct scheduler.
I am using Diffusers, not ComfyUI. Does this mean I cannot use a custom sigma schedule with this particular scheduler? Or is there a workaround to make it work?"
All reactions