Skip to content

Possible bug in pipelines that use denoising_start and denoising_end #6495

@a-r-r-o-w

Description

@a-r-r-o-w

Here are a few examples of what I think is a possible bug.

denoising_start=self.denoising_start if denoising_value_valid else None,

denoising_start=self.denoising_start if denoising_value_valid else None,

denoising_start=self.denoising_start if denoising_value_valid else None,

We can see that denoising_value_valid is defined, but not called, and is used in determining whether self.denoising_start or None is passed into self.get_timesteps.

# ...
        timesteps, num_inference_steps = self.get_timesteps(
            num_inference_steps,
            strength,
            device,
            denoising_start=self.denoising_start if denoising_value_valid else None,
        )

However, it is not called which evaluates condition to True always. This does not seem like the intended behaviour, no?

@yiyixuxu @patrickvonplaten

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions