Open adegerard opened 1 year ago
Should the options in settings for SCUNet just be removed, and to never use tiling then?
imho, tiling should not be used with SCUNet, unless someone find a way to remove or reduce these artifacts. Drawback is that an OOM error may occur depending on the image size and the amount of VRAM.
example: with my RTX4080, I can denoise images up to 4096x3277 without oom but it takes so long time. (more than 1 minute). I usually denoise lower images (720x576) without any problem.
I do not know if there a way to detect if an OOM error may occur before running it.
edit: sometimes, this is not noticeable. Maybe set the tiling size by default to 0 and display a (red?) warning when the user enables it.
Is there an existing issue for this?
What happened?
Denoise a picture with tiling enabled. tile size: 256, overlap: 64
This is a side effect because SCUNet uses local and non-local properties. Tiling is a non sense.
Steps to reproduce the problem
What should have happened?
In fact, this is due to the fact that the SCUNet algo uses local and non-local properties. Tiling is a non sense for SCUNet: refer to the paper.
Version or Commit where the problem happens
68f336b
What Python version are you running on ?
Python 3.10.x
What platforms do you use to access the UI ?
Windows
What device are you running WebUI on?
Nvidia GPUs (RTX 20 above)
Cross attention optimization
Automatic
What browsers do you use to access the UI ?
Mozilla Firefox
Command Line Arguments
List of extensions
No
Console logs
Additional information
Disable Tiling.