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

My custom implemetation in Automatic1111's WebUI #5

Open
pkuliyi2015 opened this issue Mar 6, 2023 · 1 comment
Open

My custom implemetation in Automatic1111's WebUI #5

pkuliyi2015 opened this issue Mar 6, 2023 · 1 comment

Comments

@pkuliyi2015
Copy link

pkuliyi2015 commented Mar 6, 2023

Dear authors,

I have implemented your algorithm to Automatic1111's WebUI with the following optimization:

  • Cropping views in a more symmetric way to get a better result.
  • Pre-calculate weights to save time (as weights won't change once the views are determined.
  • Batched latent view processing for acceleration.

Some WebUI related stuffs:

  • Compatibility with all samplers.
  • Compatibility with ControlNet.

Here is the link:

Great thanks to your fantastic work especially in img2img and panorama generation! We are working on text prompt now.

But the uncontrolled large image generation is not ideal at all, as repeated patterns always appears and the image is mostly unusable.

Would you please give us some insights, if we can generate large images without a user-specified prompt mask?

For example, I have an idea (without proof): we may generate a small reference image first, obtain the prompt attention map, scale it to a larger resolution, and finally we automatically locate the prompt to its correct views during multi-diffusion.

Thank you very much!

@pkuliyi2015 pkuliyi2015 changed the title Implemetation in Automatic1111's WebUI My custom implemetation in Automatic1111's WebUI Mar 6, 2023
@omerbt
Copy link
Owner

omerbt commented Mar 8, 2023

Thank you for implementing MultiDiffusion with the WebUI -- looks great!

Regarding larger images -- in the simplest setting of having the same prompt for all views, then almost by definition it may be unsuitable for certain prompts/resolutions (e.g., when generating a single object that should not appear in each view).
I think that a coarse-to-fine generation approach can help with this.

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

2 participants