This is how I usually process 30MPx JPG files that are shot with a Canon 5D Mark IV. This is a square artifact. But it doesn’t always have to be square. Sometimes it’s just a stripe or a weird shape. They are always randomly generated on different photos and in different places. I always use DeNoise as a standalone program for batch photo processing. But as far as I know, it also happens as a plugin.
I batch processed 126 JPGs as an experiment, using DNAI’s Auto setting and in standalone mode. I was unable to find any artefacts similar to yours. When you say it’s random, do you mean that you can process the same image a second time and the artefact won’t appear? Or does it always appear on specific images only and always in the same place?
By the way, my processing also crashed after about 100 images. Since no one from Topaz development tends monitor this forum, you need to send your crash report to company Support. I shall be doing the same,
I am on an M1 Mac Mini with 16GB RAM running Ventura 13.1.
Yes, it happens randomly. The second time, the artifact may be elsewhere, or it may not be there anymore. As for the crash of the program. it happens mostly after 30 +/-. I will also send it directly to support.
I work on a MacBook M1 Max, 32gb ram (Ventura13.1).
I haven’t done much batch processing with this version of DNAI so don’t know how common the crashes are. And anyway, I shoot RAW these days. Certainly worth reporting, since you have more RAM than me!
Regarding the artefacts, there is nothing anyone can do unless they can replicate it. If it’s only happening in batch mode, you might need to send them a large enough batch of your images for them to test. You could upload some to WeTransfer or the like for people here to take a look. I’d be happy to do so later today.
By the way, do you have access to the new Photo AI? If so, you could see if the same issues occur there.
it also happens in single mode. I shoot in raw, but first I edit the raw and then process the jpg with DeNoise
You should always do your denoising at the START of the editing process. Anthony Morganti just did an updated YouTube video on using TDNAI as a Lightroom plugin. He’ll be doing others in the next few days. Take a look for his tips.
I don’t like denoising at the beginning of the process. first, one loses some details in the beginning. second, when you shoot in raw, you know that each camera has its own raw profile. Converting to DNG format will lose color data and profile. Dng is lossless, but it still loses the camera-specific profile. why almost every brand has its own raw file (cr2, cr3, neff, arw) because it contains this raw data that dng can never have. I don’t like the dng format. It seems like an unnecessary format to me
As I said, check out the AM video. He explains what should be edited before denoising. However, each to his own.
Any news about updated version of DeNoise??? 
Your guess is as good as anyone’s! They are supposedly concentrating on the development of Photo AI for the time being. As a beta tester, you will be advised if DeNoise gets another beta.
1 Like
I looked at the video and the only thing I do differently is that I edit it directly in camera raw via adobe bridge.
This is because the library and collection system in adobe lightroom is really terrible. My procedure is exactly like this. I’ll make some basic edits and then export them. If it’s important, then in 16bit, tiff, adobe rgb. and then I’ll send that to DeNoise. if the project is unimportant, I export to jpg, adobe rgb and then upload it to DeNoise. Unfortunately, the result is still the same. artifacts appear randomly in photos.
I found a similar topic here on the forum and I’ll let you know if it helped
I’ve searched this forum and this thread and I’m not the only one with this problem. I’ll see if reducing memory to minimum will work. the problems other users have had are quite similar.
This thing happens on about 5-10% of my photos when I process them with severe or low light. I have thousands of photos with these weird squares and every time I batch process, I need to carefully look though every photo to see whether it is affected.
Clear AI on the other hand produces weird green dots in overexposed areas (when I use it to denoise jpegs). About 10-20% photos with such highlights have them.
My workflow is A5100 or A7iii → Capture One → jpeg 97% → Denoise
Try using TIFF rather than JPEG to see if it is an issue with the export process.
Enviroment: Sony A9/A1, MacBook Pro M1 w/ 16GB, Topaz Denoise 3.70
I’ve come across so many annoying bugs, that using Topaz Denoise in productivity environment is really cumbersome.
I also got those distracting random pixelated boxes, @rinooow showed us. They appear so randomly that it gave me many extra working hours.
Then the denoise quality is always try and error. Most of the time only Low light does address low amplitude color noise and gets the most natural sharpness (on TIFFs).
But then, sometime, RAW algo does the best job (on Sony RAWs). But when using RAW denoise, my DNGs suffer:
- camera brand and model gone (lens corrections only manual)
- light levels quite different
- color balance different (okay, that one seems obvious)
- loss of highlight details
- difficult balance of denoising and sharpening - look of sharpening not very nice
- bad debayering and bad sharpening with low ISO RAWs.
And I have to disagree that cleaning the image before editing it is the way to go (except for pictures where the RAW algo works): I always get better results in first pushing shadows and highlights with LR and then denoise the exported TIF.
I really wish I just could throw my RAWs at Topaz Denoise and have them batch processed. Maybe with ISO adaptive parameters.
