brazerzkidaifeeds.blogg.se

Iridient developer 3.0
Iridient developer 3.0











iridient developer 3.0

In 2.0 I also made improvements for the color cast issue for the SD1 which in my testing seemed to apply well to the DP1M/DP2M despite the format of the metadata being changed slightly with these models. This is the very first release I've made with DP Merrill support so something may not be getting handled with these cameras as well as it should. That said some users, particularly it seems with the DP2M model, seem to be still getting images with significant color cast, such as this example. Regarding color casts, I actually do apply correction processing for these images using embedded X3F metadata and without correction things would actually be worse (at least in all test images I have at this time). My R-L Deconvolution sharpening method in particular can really pull an amazing amount of detail out of these Sigma files. If you want a crisper, sharper result, especially with distant objects, try increasing the amount of sharpening in Iridient Developer or try one of the other sharpening methods. Some seems to be applied even with sharpening set to its minimum -2.0 value. So "better" here may be an individual preference.Ģ) Regarding distant detail, SPP uses a lot of sharpening in its defaults. there are various special monochrome conversions styles available on the Mono tab, such as custom channel mixers, that would obviously give a different look. This monochrome processing is completely unique to the Foveon sensor used in the Sigmas and should give better results than the standard monochrome modes found on the Mono tab, at least in regards to getting the most possible data out of the sensor data. If SPP were able to read Tiff's, it would be interesting to see if the results on traditional bayer sensor images were similar to what we see with Foveon images processed with SPP.ġ) For monochrome conversions be sure sure to checkout the "Sigma XDR Monochrome" option found under the Input Profile popup menu near the bottom of the In tab pane. There is a lot of non user controllable processing going on behind the scenes with Sigma Photo Pro.

iridient developer 3.0 iridient developer 3.0

Iridient doesn't "know" about this issue, and produces images with full-blown color shifts. DP2M images from SPP often have moderate color shift towards the edges, but SPP appears to (partially) correct for this. As is, I'd still need to use SPP for many of my shots, though purchasing Iridient might still be worthwhile for avoiding SPP in other cases.Īnother Iridient issue: strong color shifts. If Iridient was better on distance and color-filtered B&W conversions (two areas where I think the Foveon sensor has the greatest advantage over other cameras), it would be a no-brainer purchase to replace SPP. Black and white from red-filtered photos comes out dull/noisy from Iridient (no matter what conversion settings I choose). Iridient (note how the mid-frame trees are complete mush, compared to the shading SPP was able to extract): SPP seems to preserve a lot of detail through distance/haze, where Iridient results are mushy (similar to non-Foveon results). There are also a couple areas where I prefer SPP's processing: crushed, desaturated shadow tones to hide chroma noise) Creates more "natural" (or at least "closer to original sensor data") results, not enforcing Sigma's idiosyncratic processing "look" (e.g. Much more flexibility/control over choices in sharpening, noise reduction, etc.

iridient developer 3.0

It's got several things I like (especially compared to SPP): I'm just downloading it now and will try it ASAP. I was pleased to see that version 2 of Raw Developer, now called Iridient Developer, supports the DP Merrills.

  • Sigma DP Merrills now supported by Iridient Raw Developer.












  • Iridient developer 3.0