|
Post by Peterj on Feb 1, 2020 0:12:28 GMT
I'll be changing my work flow based on my testing, but certainly won't be opening rw2 files in DNAI.
|
|
|
Post by kdcintx on Feb 1, 2020 0:20:51 GMT
Thank you Peter and Helen for sharing your comparison. This exercise was very information. I use DNAI (standalone) on jpg files because of poorer results with Raw files. I thought maybe I was doing something wrong but apparently not.
|
|
|
Post by tonyw on Feb 1, 2020 1:11:37 GMT
I'm a bit curious how people are processing raw files directly - I've been using it from within Lightroom and it won't let me "Edit In" Topaz without LR first converting it to a TIF file. For me, whether I do it from LR or move it into PS seems to make no difference and it's giving good results on TIF files.
Tony
|
|
|
Post by hmca on Feb 1, 2020 2:08:24 GMT
Tony I have a preset to export my Sony arw file to a folder on my desktop. I then open the DeNoise standalone from my desktop and add the arw file. It returns it as a tif with the ProPhoto color profile. To compare, I select edit in PSCC from LR. Using the filter menu I select Topaz DeNoise and send the arw file. It returns with the ProPhoto color profile but doesn't have the filmy/matte look that I get if I export an arw file from LR.
I am happy with what I get going the PSCC route and can't account for the difference. But I have tried this on more than one file and the results are always similar.
I haven't tried following the same procedure but sending a tif file instead.
During the webinar he used jpeg. images which surprised me as I would think that a tif. would have been a better choice.
|
|
|
Post by Sepiana on Feb 1, 2020 2:22:23 GMT
I'm a bit curious how people are processing raw files directly - I've been using it from within Lightroom and it won't let me "Edit In" Topaz without LR first converting it to a TIF file. Tony Tony, I don’t use DeNoise from within Lightroom because of this conversion to TIF. I go to . . . Edit in Photoshop and apply it there. In this way, I am still working with a Raw file.
|
|
|
Post by hmca on Feb 1, 2020 2:35:43 GMT
So I tried to send a tif file to DeNoise from LR and it returned without that filmy/matt look. I can't explain the difference but like Sepiana I will continue to use the PS route. return of tiff...no further edits.
|
|
|
Post by srmoment on Feb 1, 2020 6:41:28 GMT
I thought I would try some tests too. #1. Original raw file (Olympus .orc file) pulled into Elements2020 and saved as jpeg. #2. Three tests: a) raw file into Elements2020, Topaz AI Clear filter (in Elements), the OnOne Sunshine/HDR ...[basically Elements than AI Clear then On1] b) raw file into Elements2020, OnOne Sunshine filter, AI Clear filter, finishing with OnOne HDR filter .....[Elements then On1 back to AI Clear back to OnOne] c) raw file directly into Topaz AIClear, exported as dng file, pulled into Elements 2020 and processed with OnOne. It is interesting that pulling the raw file into Topaz AIClear first produced a dng file that was considerably lighter than the other methods and required further processing in OnOne. Also, please note that you need to click on the trial image and pull it into full sized resolution to see the changes.
|
|
|
Post by hmca on Feb 1, 2020 12:50:01 GMT
Thanks for sharing your experiment, Pat. What I notice is that in your experiment the image that went to AI Clear first has more detail in the feathers and branches.
We probably should be posting a close-up of the amount of noise in our starter images. Mine were shot at ISO 5000 and had a considerable amount of noise for example.
|
|
|
Post by Peterj on Feb 1, 2020 18:59:38 GMT
I submitted a support ticket to Topaz raising the anomaly I discovered with Panasonic raw (rw2) files. I'll follow up here with their response.
|
|
|
Post by srmoment on Feb 1, 2020 19:03:07 GMT
My ISO was 800, 'S' 1250, F8 taken with a 2.0 magnification on a 300mm lens. Originally, when I looked at the raw file and enlarged it, I would not have kept it as it was blurry in the feathers and detail was lost in the head. (p.s. I think if I lighten the first two images they will be closer to the lighter image for detail....). (p.s.p.s. I enlarged the raw photo and put it into the original post. The noise is really noticeable in the sky and there is definitely a difference after AI Clear is used)
|
|
|
Post by tonyw on Feb 1, 2020 23:07:05 GMT
Sorry if I ramble on but I've been trying to explain to myself what I and others are experiencing. This article was helpful in understanding raw and dng files. One consideration is that Topaz DeNoise can never actually do anything to the raw file as it comes out of the camera because that never changes and requires demosaicing into an image format before it will even look like an image. If you use DeNoise as a standalone on a raw file from the camera it must handle the demosaicing internally and it will let you save the result as a DNG - leaving the original raw file untouched. If you use it from Lightroom you have to create a TIFF file because Lightroom can't store the denoise edits in an XMP file as it does with its own edits. If you use it having opened in Photoshop you are likely using it on a dng file as that's what LR/PS uses internally but when you come to save the denoised file it has to be a new file (so again a TIFF file or one of the other available image file formats (but I don't think dng is available) I compared all three (using Fuji RAF files) and the only difference I see is that using it as a Standalone gave that rather pale result that others have seen compared to using it in LR or going from LR to PS and using it there (and saving it back to LR). The latter two looked the same to me. It's possible that the standalone is different because of the different demosaicing compared to Adobe but more likely it's because dng files from Adobe automatically have a camera profile applied (Adobe Color for example which is Adobe's idea of a starting point for your adjustments) but the dng files from Denoise don't seem to have one so you would have to make your own or just apply more adjustments than you would with a camera raw file imported using Adobe. I've seen different opinions on when you should denoise - I've typically done it towards the end of editing but before any sharpening and have seen that recommended but then I've also seen the opposite recommended so whatever works! Regardless of all that technical stuff and trying to understand the best way to use it, it certainly does seem to work and I'll be finding it useful for theatre dress rehearsal shots where I usually have to use very high ISO with the resultant noise. Tony
|
|
|
Post by hmca on Feb 3, 2020 0:31:14 GMT
Regardless of all that technical stuff and trying to understand the best way to use it, it certainly does seem to work and I'll be finding it useful for theatre dress rehearsal shots where I usually have to use very high ISO with the resultant noise. I agree. Shooting with an ISO of 4000 yesterday, I was happy to be able to start with an image with a considerable amount of noise.... And end up with a much better rendition using the De Noise auto setting and then adjusting the outcome using manual. Additional processing in PS. Only problem now is that it looks like she was not moving......this was part of a wolf turn sequence where the gymnast starts in a squat facing sideways on the beam. One leg is in a squat and the other is straight out to the side. She then twirls around to the front again.
|
|
|
Post by Peterj on Feb 3, 2020 23:30:50 GMT
I submitted a support ticket to Topaz raising the anomaly I discovered with Panasonic raw (rw2) files. I'll follow up here with their response.
Response from Topaz ...
Peter,
For some less common raw files, DeNoise AI has some conflicts that we expect to improve in a coming update. For files that experience this type of unexpected behavior (desaturation, color shift, etc), the solution, as you seem to have discovered through On1, is to use a TIFF.
TIFF files are essentially modified DNG files so you should still get full editing capability without the conflict until the raw processing conflict is resolved.
Thanks!
Eric Lowery Operations Manager
|
|