Description
Describe the bug
It seems that disabling open-cl can lead to a picture not being fully rendered. I get a black bar at the bottom of the image.
Steps to reproduce
darktable-cli ./MEP05404.arw ./MEP05404.arw.xmp /tmp/fine.jpg --core --conf plugins/imageio/format/jpeg/quality=80 --conf plugins/imageio/storage/disk/overwrite=1
produces the right image
darktable-cli ./MEP05404.arw ./MEP05404.arw.xmp /tmp/broken.jpg --core --conf plugins/imageio/format/jpeg/quality=80 --conf plugins/imageio/storage/disk/overwrite=1 --disable-opencl
produces the incomplete one
The raw files and generated jpgs are available here: https://drive.google.com/drive/folders/1q8_-WJ0C6ljQsvqfF3rO_hjoKqJzf_A0?usp=sharing (because Sony's RAW files are so large, it didn't fit on github ^^')
Expected behavior
borken.jpg
and fine.jpg
should be the same (or very close to)
Logfile | Screenshot | Screencast
Here are the logs files using -d all
for the broken jpg (without open-cl) the working jpg (with open-cl)
Commit
No response
Where did you obtain darktable from?
distro packaging
darktable version
darktable 5.0.0
What OS are you using?
Linux
What is the version of your OS?
NixOS 24.11.20241230.3ffbbdb (Vicuna) x86_64
Describe your system?
I can reproduce the same problem on two machines with very different hardware configuration (one server and one desktop) but running the exact same os and version of darktable.
Are you using OpenCL GPU in darktable?
None
If yes, what is the GPU card and driver?
No response
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
The bug is a few months older than version 5.0.0 and was already present in at least 4.8. But things used to be fully functional before.
It seems that more complex edits can lead to a larger black band at the bottom, but it is a bit inconsistent.
I am quite confused by this bug, since there are no error messages in the logs or anywhere else on my computers.