Skip to content
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

Depth conditioning is not working #52

Open
AtlantixJJ opened this issue Nov 26, 2023 · 5 comments
Open

Depth conditioning is not working #52

AtlantixJJ opened this issue Nov 26, 2023 · 5 comments

Comments

@AtlantixJJ
Copy link

I am trying with the following example with a given depth prior.

Screenshot 2023-11-25 at 9 14 58 PM Screenshot 2023-11-25 at 9 15 39 PM

The results are quite out of expectation.

Screenshot 2023-11-25 at 9 16 07 PM

On the other hand, if no depth conditioning is used, the results are somewhat closer:

Screenshot 2023-11-25 at 9 16 34 PM

Do you have a clue what's wrong with the depth conditioning part?

@pragyavaishanav
Copy link

I have similar issues.
4_image (8)
depth_combined (1)
Screen Shot 2023-11-27 at 10 20 50 AM

To me it seems, it is assuming an underlying geometry of the model when we pass the front side image. Then it try to recreate geometry and then draw it on that geometry instead of taking the our custom depth maps into account properly. Look at my results. It was drawing two arms as if reading my depth and its OWN (concept of depth) depth and then try to work with both somehow but terribly failing.

@pragyavaishanav
Copy link

pragyavaishanav commented Nov 27, 2023

At least I know why you (@AtlantixJJ ) have issue. I was having similar problems as yours. I got rid of the scheduler that they are using. Once scheduler wasnt used, then it was drawing the input image on the depth maps (even though still weirdly).
I had added an issue related to the same previously here, #49

@eliphatfs
Copy link
Collaborator

image
The example script should have an output similar to this figure.
If you cannot reproduce the example script, please send me your diffusers, torch version and GPU setup, I guess there are compatibility issues instead of issues with the model.

@eliphatfs
Copy link
Collaborator

If you are good with the example but failing with your input, maybe you could tune the controlnet_scale parameter. In 2D SD controlnets this also needs to be tuned.
Another thing is that maybe the input is not matching the requirements of the depth condition. Please see if your scales or background is different to the example depth input.

@odusseys
Copy link

odusseys commented Feb 4, 2024

This is because of the scheduler used in the example code. Just remove it and the results will be correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants