update EMBIGGEN.md

- fix codeblocks
- fix toc
- use admonitions
This commit is contained in:
mauwii 2022-10-11 06:10:25 +02:00
parent 791e6c63ef
commit c1f1dfa714
No known key found for this signature in database
GPG Key ID: D923DB04ADB3F5AB

View File

@ -43,7 +43,7 @@ it's similar to that, except it can work up to an arbitrarily large size
has extra logic to re-run any number of the tile sub-sections of the image has extra logic to re-run any number of the tile sub-sections of the image
if for example a small part of a huge run got messed up. if for example a small part of a huge run got messed up.
## Usage ### Usage
`-embiggen <scaling_factor> <esrgan_strength> <overlap_ratio OR overlap_pixels>` `-embiggen <scaling_factor> <esrgan_strength> <overlap_ratio OR overlap_pixels>`
@ -100,7 +100,9 @@ Tiles are numbered starting with one, and left-to-right,
top-to-bottom. So, if you are generating a 3x3 tiled image, the top-to-bottom. So, if you are generating a 3x3 tiled image, the
middle row would be `4 5 6`. middle row would be `4 5 6`.
## Example Usage ### Examples
!!! example ""
Running Embiggen with 512x512 tiles on an existing image, scaling up by a factor of 2.5x; Running Embiggen with 512x512 tiles on an existing image, scaling up by a factor of 2.5x;
and doing the same again (default ESRGAN strength is 0.75, default overlap between tiles is 0.25): and doing the same again (default ESRGAN strength is 0.75, default overlap between tiles is 0.25):
@ -112,6 +114,8 @@ invoke > a photo of a forest at sunset -s 100 -W 512 -H 512 -I outputs/forest.pn
If your starting image was also 512x512 this should have taken 9 tiles. If your starting image was also 512x512 this should have taken 9 tiles.
!!! example ""
If there weren't enough clouds in the sky of that forest you just made If there weren't enough clouds in the sky of that forest you just made
(and that image is about 1280 pixels (512*2.5) wide A.K.A. three (and that image is about 1280 pixels (512*2.5) wide A.K.A. three
512x512 tiles with 0.25 overlaps wide) we can replace that top row of 512x512 tiles with 0.25 overlaps wide) we can replace that top row of
@ -128,17 +132,17 @@ look up the original prompt and provide an initial image. Just use the
syntax `!fix path/to/file.png <embiggen>`. For example, you can rewrite the syntax `!fix path/to/file.png <embiggen>`. For example, you can rewrite the
previous command to look like this: previous command to look like this:
~~~~ ```bash
invoke> !fix ./outputs/000002.seed.png -embiggen_tiles 1 2 3 invoke> !fix ./outputs/000002.seed.png -embiggen_tiles 1 2 3
~~~~ ```
A new file named `000002.seed.fixed.png` will be created in the output directory. Note that A new file named `000002.seed.fixed.png` will be created in the output directory. Note that
the `!fix` command does not replace the original file, unlike the behavior at generate time. the `!fix` command does not replace the original file, unlike the behavior at generate time.
You do not need to provide the prompt, and `!fix` automatically selects a good strength for You do not need to provide the prompt, and `!fix` automatically selects a good strength for
embiggen-ing. embiggen-ing.
!!! note
**Note**
Because the same prompt is used on all the tiled images, and the model Because the same prompt is used on all the tiled images, and the model
doesn't have the context of anything outside the tile being run - it doesn't have the context of anything outside the tile being run - it
can end up creating repeated pattern (also called 'motifs') across all can end up creating repeated pattern (also called 'motifs') across all