It definitely looks like a black level issue, but it’s curious that raw refinery works fine apparently.
I pushed 0.2.4 which removes the duplicate, but it is a black level issue that I can’t directly fix in rawforge otherwise.
I could add in an optional black level subtract tag as a fix if that would help. Then you could manually supply the black level
Sorry, my answer hasn’t been totaly correct…I mixed up some things:
Yes, the camera was R6M3, and the image I used with rawforge was cr3, but I convert the images to dng before using rawrefinery.
rawforge works fine with dng! I will keep the step ‘convert images to dng before denoising’ in my workflow - it’s already a step in my automation.
(I’ll try to have my breakfast before answering next time, at least my pot of coffee!!).
But thank you for removing the duplicates. And I also noticed, that I can leave out the step of copying the exif from the original to the denoised image. And don’t care about black levels of unsupported cameras!
1 Like
Yes for RawRefinery, I only missed the python3-devel package. But very slow for “cpu” and “light” compiled on a Fedora 44 box (AMD Ryzen™ 7 6800H with Radeon™ Graphics with 32 Go of RAM). . Thanks
No for RawForge installed in an other venv. The DNG created with normal progress bar is saved but unreadable. His properties shows an width of 3 pixels ! Tested with ARW and cr2 files.
I noticed that rawforge now writes something like ‘{“shape”: [4638, 6958]}’ into exif ‘image description’? Is this necessary? I’d like to have this empty.