darktable: custom raster mask module (read-only masks)

[ydyote]

Is your feature request related to a problem? Please describe.
Being able to create masks outside of darktable and use them in darktable

Describe the solution you'd like
A module which would be able to load a mask from a file/clipboard (also quickreload it when the target file changes)

• possible issues when the path is not relevant, so I guess quickreload is optional, one time load would work too

Module can also store the mask into the sidecar file (dirtiest way would be to use some compression and base64) and then also load it from there

Alternatives
Just get better with darktable current mask functionality I guess? But sometimes it would take way too long and not even parametric functionality helps there

or do more editing in gimp but thats only possible after the image export no way to use this within the darktable pipeline

Additional context
I looked at
#5952
#4459
#12295

I understand "DING (Darktable Is Not Gimp)." but thats why I didn't suggest any editing just load from a file or clipboard

common workflow I guess would be:

1. Take the raw photo, export quick jpg from defaults
2. Open the jpg in your editor of choice i.e. GIMP
3. make the mask using just white and transparency/opacity
4. export the mask into png or some other non-destructive format or copy it into clipboard
5. load it into the darktable module
6. Use the "raster mask" button within modules and select the mask from this new module there

There is a lot of issues and one of them that you always have to have full-image mask resolution but compression would fix big sidecar files if the mask is simple enough

[github-actions]

This issue did not get any activity in the past 60 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[github-actions]

This issue was closed because it has been inactive for 300 days since being marked as stale. Please check if the newest release or nightly build has it fixed. Please, create a new issue if the issue is not fixed.