Just wondering why DT, on my machine at least, can’t read the “dng” output files from any Topaz PhotoAi/DenoiseAi raw denoising process - but CAN read those from DXO Pure Raw 3?
Oddly enough, Raw Therapee can read and display BOTH DXO and Topaz files.
DT does an awesome job of working up the DXO files!
I’m on a clean installation of the Apple Silicon version of DT, and was just wondering if anyone knew what the problem is, and if there is a workaround for it.
Neither app output is a real, fully compliant dng file - you can’t dictate the demoz algo for a start, but none the less, it would be nice if I could find a way to at least open the Topaz ones.
Which version of Denoise AI do you use? I have 3.7.2, and everything works fine. Maybe Topaz messed something up with 3.7.3? Would you mind sharing a file?
Ya no worries it was a hail Mary… I just saw someone complaining that the Topaz files from their D850 were almost 300Mb after processing so I figured it might just be a tiff with a lazy packaging into a dng…
Hi Todd, as far as I’m aware all dng files are basically a TIFF, but there the similarity seems to end - something about TIFF 6 compliance?? All a bit beyond me to be honest.
But if I run a raw file through Adobe DNG Converter - (without embedding the raw) - I can open said dng in RT or DT and change the demoz algo, use RT capture sharpening and everything else under the demosaic tab.
Topaz and DXO dng’s do not allow any change under demosaicing in either RT or DT - so I always imagine them to be a straight TIFF in a dng container. Why this happens I don’t understand, because the correct Adobe DNG format is freely available as far as I understand.
I want to get all this out in a video in the next 48 hours, so I just wanted to check things out about the Topaz stuff - terrible company to try and deal with, and they never answer my damn emails.
This is a common misconception. Both TIFF and DNG are containers that can deliver a variety of image content types. There is no such thing as “straight TIFF” image type strictly speaking, but in reality it does deliver an RGB image in most cases, so it became a misnomer. So is “correct Adobe DNG format” to imply only something like a straight out of camera raw.
A dng written by those tools is full resolution r, g and b.
Maybe with some compression.
Your raw file (assuming Bayer array ) is full resolution but monochrome (or 4 channels but 1/4th of the full resolution, however you look at it ).
So it’s only normal for those files to be larger than the input . Demosaicing is in basic a form of upscaling , so the output is larger than the input .
These dng files ARE in the basic form a tiff file. Dng files containing the raw Bayer data are also in essence a tiff file , but just as the input raw file , still one channel full resolution of data in it.
DxO photolab files have worked fine forever in Darktable (and i never had colour shifts or something when importing them into Lightroom ).
Always something different with the dng files by on1 tools. Never tried topaz stuff (I’m having enough issues with their tiff output).
Darktable isn’t really picky I’m guessing in reading dng files … so I’m surprised they even refuse to open. Maybe a rewrite of the camera model , or a wrong value in the channel-type (or whatever field normally holds if it is raw Bayer data in inside or regular RGB data ).
I agree with that @kmilos said here & in Darktable and Topaz Photo AI DNG incompatibility,
that metadata does look non-sensical, but there is an argument to be made
that [DNG] tiles can have padding rows/cols, and while it may seem, err, non-conventional,
to have a single tile with size much larger than the actual image size, that isn’t exactly illegal.
The files are big - what do you want me to do, crop the output dng file down to 12Mp?
That’s why I gave you the link to the full size files earlier, so you could do what you want with them!
In my original post, the couple of missing data fields on the Topaz files - well, running the file through Adobes DNG converter fills those missing data fields in.
