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

feat(nodes): inpainting workflow support nodes #7583

Merged
merged 8 commits into from
Jan 21, 2025

Conversation

psychedelicious
Copy link
Collaborator

Summary

A collection of nodes to support inpainting segmentation maps in workflows.

Related Issues / Discussions

n/a

QA Instructions

Try this workflow. The linear view is set up with everything you need to test it.
Inpaint Segmentation Map.json

  • Add an equal number of segmentation maps and source images. I'll attach 3x segmentation maps and 1x source image. You can add the source image to the batch multiple times.
  • Select the target color so that it matches the red blob.
  • Add a prompt for the inpainted region.
  • Select an SDXL model.
  • Create and select a board for the runs.

3x faux-segmentation maps

segmentedimage3
segmentedimage2
segmentedimage

1x source image

a2838ae7-6ea7-498b-afc7-2d019d3d7e0c

Merge Plan

n/a

Checklist

  • The PR has a short but descriptive title, suitable for a changelog

@github-actions github-actions bot added python PRs that change python files invocations PRs that change invocations labels Jan 21, 2025
@github-actions github-actions bot added the frontend PRs that change frontend files label Jan 21, 2025
@psychedelicious psychedelicious merged commit ad8885c into main Jan 21, 2025
15 checks passed
@psychedelicious psychedelicious deleted the psyche/feat/inpainting-workflow-support branch January 21, 2025 06:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
frontend PRs that change frontend files invocations PRs that change invocations python PRs that change python files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants