darktable-org / darktable-org/darktable
residual layer in retouch wavlet decomposition differs between opencl and cpu
Open
Nobody has claimed this yet.
bug: pending
priority: low
reproduce: confirmed
- Dominant language
- C
- Stars
- 13.1k
- Forks
- 1.4k
- Avg merge
- 22h 14m
- Merged PRs (30d)
- 198
Description
Describe the bug
deactivating gpu processing results in a darkened residual layer
opencl on:
opencl off:
Steps to reproduce
- show residual layer in retouch
- enable/disable opencl
Where did you obtain darktable from?
self compiled
darktable version
windows: 4.9.0+1227gbb12aceef5gfabbd1d450
macos: 4.9.0+1229
What OS are you using?
Windows
also reproducible on macos
What is the version of your OS?
Win 10, MacOS1 5
Describe your system?
Prozessor 13th Gen Intel(R) Core(TM) i7-1365U 1.80 GHz
Installierter RAM 32,0 GB (31,7 GB verwendbar)
apple m1max
Are you using OpenCL GPU in darktable?
Yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in darktable's retouch module by showing the residual layer, then toggling OpenCL as described. Compare the CPU and OpenCL results on the reported Windows or macOS setups; done means both paths produce the same residual-layer appearance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100