Yep, precisely, and please do check that the issue still reproduces after crop.
Maybe even let’s go down to 6MPix.
I understand that you’ve provided a google drive with the samples,
but we need a sample on RPU in order to deal with this.
Also, i’m a bit saddened that this forum is being used as a bug tracker.
I guess it’s good for driving up the forum activity.
Hi Lars, I honestly wasn’t wanting this to be taken as a ‘bug’ in DT, more a negative on the quality of Topaz!
Here is a small crop of one of the files - it won’t open in DT on my machine:
CROPGX2R4019-topaz-denoiseraw.dng (2.6 MB)
And here it is after running through the Adobe DNG Converter, which WILL open in DT:
CROPGX2R4019-topaz-denoiserawADC.dng (1.7 MB)
I find the file size differential a bit odd…
Great. Topaz save uncompressed and Adobe DNG Converter does lossless compression in addition to massaging the tags. (The 30-40% saving is typical for lossless.)
Again, TIA for uploading (only the “failing” small sample) directly to https://raw.pixls.us/ (you might have to check “the file hasn’t been modified” box even if it is not strictly true…)
Okay, done that.
Right, but it does highlight an issue in darktable.
Awesome, thank you!
The problem with Topaz DenoiseAI is their problem purely, not darktable’s one. I have just used DenoiseAI latest version (3.7.2) or a photo from Google Pixel 6 Pro, and the photo is rotated 180° in QuickLook (macOS file preview).
I took another photo that I took by Samsung S8 several years ago, and I see that the latest version of DenoiseAI still changes the colors slightly (again, in macOS QuickLook).
Also, I can see that after DenoiseAI, files loose a lot of metadata (like location, exposition, ISO, etc.).
And finally, I have raised the issue to them more than a year ago; they have replied that that put it in their backlog. Now it seems that their previous softwares are abandonware, and they release a new product PhotoAI, without any discounts to the owners of DenoiseAI, SharpenAI, or GigaPixelAI. So, my plan is to just continue to use the versions of their previous softwares for now, and then at some point just switch to something else. Actually, with Google Pixel 6 Pro, I did not have any need so far to use DenoiseAI; somehow, they remove the noise by themselves).
@kmilos I did not quite understand what images I should upload? The ones that give color issues with the DenoiseAI?
It’d be interesting to see how the proprietary denoise stacks up against nind-denoise/README.md at master · trougnouf/nind-denoise · GitHub and if we keep providing better training data if we can surpass the proprietary stuff
hopefully it’ll make it into dt 4.4
@Dmitry visual noise is not what is being described in the starter post here, that is a different issue.
@Dmitry We got the sample failing to load, thanks.
Interesting development on this question!
If I fire up my old Intel Mac that runs Darktables latest Intel version together with the Topaz latest Intel versions, I can make a linear dng in Topaz DeNoise Ai 3.7.2 that opens in Darktable Intel no problem.
If I transfer that dng to my Apple Silicon machine, the M1 version of Darktable can read and open it without problem.
But the dng made in M1 Topaz will NOT open in Intel Darktable!
Topaz Photo Ai dngs produced on Intel versions will NOT open in either iteration of Darktable.
So either Mac version of PhotoAi produces the same error as M1 silicon DeNoise Ai.
Very convoluted problem!
That seems to be written by “Topaz Photo AI 1.3.4” and here you tried Topaz DeNoise Ai 3.7.2. You’re comparing apples and oranges, even if they’re sold by the same vendor.
In any case, RawSpeed/darktable have relaxed the requirements and will deal with those files in some future version.
Any further “weirdness” about Topaz software is beyond the scope of this forum, as it is proprietary and there’s no telling about its inner workings.