The curve I’ve produced here is correct for a Canon 1DX at the shot ISO which was 1000 or 800 if my memory serves correctly. It’s very important that you wrap your head around this fact. In simple terms the same numeric value of adjustment to any control slider can have differing effects depending on the sensor it was made by and the ISO at which it was shot. The majority of adjustments in Lightroom are specific to camera sensor and ISO. However, there is a caveat (isn’t there always!) and it’s this: Saving the curve is useful as it makes for a very quick adjustment of further images. xmp file, and to the user/Library/Application Support/Adobe/CameraRaw/Curves file path (Mac). I save the curve with the name 2010to2012 – by default it saves as an. Let me demonstrate the “case to answer” by using the same image I used the other day when giving Canon an indirect slagging off over lossless compression: Out there in photography land there are two RAW file handlers that are notorious for being “neutral” in their initial raw render – Raw Digger, and Iridient Developer. So believe me, if your raws look “nice ‘n punchy” from the get-go then something is wrong somewhere! If that’s the case then NEWS FLASH – RAW files should look as flat as dish-water pre-process, and you have do some work to make them look good. The Case To Answerįirstly, a lot of you might be wondering WTF I’m ranting on about – your RAW image previews look great before you start doing anything to them – mmmmm….
#Iridient developer how to#
Only by learning how to Neutralise Hidden Exposure Compensation can we actually arrive at a suitable starting point for the development process. In other words Lightroom adds hidden adjustments which we cannot see because they are not registered on the adjustment sliders under process version 2012.īut when I take into account the support Lightroom currently offers for mobile phone cameras, cloud synch etc, I can’t help thinking that Adobe are trying to give Lightroom some sort of mass-market appeal by adding what the designers and coders think is some sort of WOW-factor to image previews – though I might be wrong!īut whatever Adobes reasoning, the fact remains that SOME OF US want to see our raw files for what they are – straight gamma 2.2 encoded versions of what the sensor recorded. It uses a variety of ‘behind the scenes’ algorithms to add what it thinks are good adjustments in terms of exposure brightness and contrast. The problem lies in the fact that Lightroom, for a long time, ceased to be a “neutral” RAW handler. We all know how good Lightroom is – but it’s also a total pain in the arse!Īges ago, I did a post about Lightroom 5 and accurate colour HERE and, according to this blogs page-view stats, that post still gets a large global viewing figure every month – so it’s something of an on-going problem for a lot of users.īut things have moved on a bit since then, and we are now working with the v5 release of Lightroom 6/CC 2015 – and things haven’t got any better, sadly, from the perspective of actually “seeing what you captured”. Lightroom – Neutralise Hidden Exposure Compensation.
0 kommentar(er)
