gradio-app / gradio

Build and share delightful machine learning apps, all in Python. 🌟 Star to support our work!
http://www.gradio.app
Apache License 2.0
33.41k stars 2.53k forks source link

REQ outplainting with options #2229

Closed TwistedFromArma closed 10 months ago

TwistedFromArma commented 2 years ago

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Often the head or feet or both are cut off. someitmes its the sides cut off by the AI. Its frustrating.

Describe the solution you'd like
An option for outpainitng would let you automatically expand the canvas by 100 or so pixels in any chosen direction. Plus option to auto mask these new areas as where to regenerate the visual. Plus the options to run the SD AI using the same seed/algorithm/CFG and even description again to fill in the new blank areas.

Additional context
[Add any other context or screenshots about the feature request here.] It's been done very well here but that required multiple and involved steps. the author says it was exhausting as theres no itnerface to do this in. (https://www.reddit.com/gallery/xb4jr5)

abidlabs commented 11 months ago

Hi! We've now made it possible for Gradio users to create their own custom components -- meaning that you can write some Python and JavaScript (Svelte), and publish it as a Gradio component. You can use it in your own Gradio apps, or share it so that anyone can use it in their Gradio apps. Here are some examples of custom Gradio components:

You can see the source code for those components by clicking the "Files" icon and then clicking "src". The complete source code for the backend and frontend is visible. In particular, its very fast if you want to build off an existing component. We've put together a Guide: https://www.gradio.app/guides/five-minute-guide, and we're happy to help if you'd like to put together a custom component for this issue

abidlabs commented 10 months ago

I'll go ahead and close this issue since we are not planning to include this in the core Gradio library. But happy to help if you are interested in making this a custom Gradio component (feel free to ask questions in this issue).