(Oh, and: this is a 100% crop of a a photo showing a professional dancer performing live, just in case it isn't quite clear) This is a difficult shot in very dim light, there's a lot of stage-haze and I took the pic from at least 50 meters from the stage from the soundengineer's position (which is my daytime job). Both are with all settings at default (both in IXT and LR). The IXT-rendered dng (left) is sharper, there's much more detail but it has that "wormy" noise pattern. Sooner or later, this will generate confusion.Īs I have mentioned before, I'm impressed with the fine detail rendering of IXT, but it renders the "wormy things" in low-light pics as shown here: (I mean hopefully it shows, this is a screenshot from LR, I don't know how this will render on the forum): I don't think that creating a bunch of TIFF files that are actually DNG files is a good thing. And this method will avoid potential conflicts. It's quick and synchronizing the folder to get the DNG file into the catalog takes only a few seconds. So I continue to prefer the script method. Photoshop command in LR (and export as TIFF) ? Edit the original (the DNG-wanna-be-TIFF file) ? Edit a copy with LR adjustments ? In which case there will be a possible name collision. What if you want to do some retouching in Photoshop and use the Edit in. Moreover, although LR will handle that file correctly, this may generate confusion if you are accessing your files from other apps which may not react as LR when accessing a TIFF file being actually a DNG file. Which takes as much time as synchronizing the folder when using the script method. You can only do that from outside and then fix the "file not found" problem that this operation will generate. Also, you can't change the file extension in Lightroom.
So you can't use it to "mark" the filename in order to signal that it is not a TIFF but a DNG file.
In the External Editing preferences of LR, the renaming template applies to all files edited externally. When choosing the "Edit in" method, the file returned by IXT in LR will have a TIF extension. I made some further testing and found another few problems. This video IS the magic workflow!! Pay close attention to the details and settings and process. LR + Iridient Developer makes me a fulfilled Fuji X shooter now. Now that Iridient can integrate so smoothly and easily with LR, it's a no-brainer. Iridient is nothing short of stunning, and truly nothing else is as good with Fuji RAW.įuji X-Trans RAW in LR alone is just plain dull and mushy, and LR's sharpening algorithm just kinda sucks with these files. I wind up throwing away most of my RAW files in LR to save space, but for any shot where Iridient would be beneficial, I keep those RAWs. When I import them all to LR, I'll typically keep and use the wonderful Fuji JPEGs, but for those special shots where I really do want to work in RAW and take advantage of highlight and shadow recovery and especially want to go for that extreme detail and ability to sharpen, I'll edit externally with Iridient. After watching this video and doing EXACTLY what he instructs, it's now simply a fantastic workflow for me.
I use Iridient as an external editor from inside Lightroom.