lllyasviel / lllyasviel/sd-forge-layerdiffuse

Feature Suggestion: Save/Output the actually transparent image, instead of the one with grid background

Open
#28 7 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
4.1k
Forks
352
PR merge metrics
No merged PRs in 30d

Description

Currently, the extension saves the preview file with a grid background, see below:

![2024-03-04 - 00 58 56](https://github.com/layerdiffusion/sd-forge-layerdiffusion/assets/60541708/51e4c62c-01a5-42bf-8cac-4b4bd9d8ae66)

But this is not actually transparent, it's just an example, to show that it's doing the transparency correctly.

The file I actually want to output is the one WITH transparency:
![image](https://github.com/layerdiffusion/sd-forge-layerdiffusion/assets/60541708/7f859134-8631-4a66-8a85-b7fe3b784a81)

But this has to manually be downloaded, and then it's just saved as image.png, so I don't get my naming done by A1111/Forge.

I suggest to switch which file is saved first, or saved at all. The grid preview is completely useless to me at least. An option would be best I guess in case someone prefers the grid version.

Great work on this tool!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named in the issue. Start by tracing how the Forge/WebUI extension saves the preview and manually downloaded transparent image, then verify which output path controls the generated filename. Done means the transparent image is saved with Forge/WebUI naming, with the grid version retained only if an option requires it.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.