From 2ad489a1ef9dde06edcc5eab232d25fa4b2673ff Mon Sep 17 00:00:00 2001 From: Lincoln Stein Date: Wed, 2 Nov 2022 23:18:30 -0400 Subject: [PATCH] dream->invoke in inpainting docs --- docs/features/INPAINTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/features/INPAINTING.md b/docs/features/INPAINTING.md index 864a1fd05a..71ede303e0 100644 --- a/docs/features/INPAINTING.md +++ b/docs/features/INPAINTING.md @@ -9,7 +9,7 @@ title: Inpainting Inpainting is really cool. To do it, you start with an initial image and use a photoeditor to make one or more regions transparent (i.e. they have a "hole" in them). You then provide the path to this -image at the dream> command line using the `-I` switch. Stable +image at the invoke> command line using the `-I` switch. Stable Diffusion will only paint within the transparent region. There's a catch. In the current implementation, you have to prepare @@ -25,7 +25,7 @@ color information is preserved. There is often an option in the export dialog that lets you specify this. If your photoeditor is erasing the underlying color information, -`dream.py` will give you a big fat warning. If you can't find a way to +`invoke.py` will give you a big fat warning. If you can't find a way to coax your photoeditor to retain color values under transparent areas, then you can combine the `-I` and `-M` switches to provide both the original unedited image and the masked (partially transparent) image: