Monitor Brightness.

Monitor Brightness & Room Lighting Levels.

I had promised myself I was going to do a video review of my latest purchase – the Lee SW150Mk2 system and Big and Little Stopper filters I’ve just spent a Kings ransom on for my Nikon 14-24mm and D800E:

Lee SW150 mk2,Lee Big Stopper,Lee Little Stopper,Lee Filters, Nikon 14-24, Nikon, Nikon D800E, landscape photography,Andy Astbury,Wildlife in Pixels

PURE SEX – and I’ve bloody well paid for this! My new Lee SW150 MkII filter system for the Nikon 14-24. Just look at those flashy red anodised parts – bound to make me a better photographer!

But I think that’ll have to wait while I address a question that keeps cropping up lately.  What’s the question?

Well, that’s the tricky bit because it comes in many guises. But they all boil down to “what monitor brightness or luminance level should I calibrate to?”

Monitor brightness is as critical as monitor colour when it comes to calibration.  If you look at previous articles on this blog you’ll see that I always quote the same calibration values, those being:

White Point: D65 – that figure takes care of colour.

Gamma: 2.2 – that value covers monitor contrast.

Luminance: 120 cdm2 (candelas per square meter) – that takes care of brightness.

Simple in’it….?!

However, when you’ve been around all this photography nonsense as long as I have you can overlook the possibility that people might not see things as being quite so blindingly obvious as you do.

And one of those ‘omissions on my part’ has been to do with monitor brightness settings COMBINED with working lighting levels in ‘the digital darkroom’.  So I suppose I’d better correct that failing on my part now.

What does a Monitor Profile Do for your image processing?

A correctly calibrated monitor and its .icc profile do a really simple but very mission-critical job.

If we open a new document in Photoshop and fill it with flat 255 white we need to see that it’s white.  If we hold an ND filter in front of our eye then the image won’t look white, it’ll look grey.

If we hold a blue filter in front of our eye the image will not look white – it’ll look blue.

That white image doesn’t exist ‘inside the monitor’ – it’s on our computer!  It only gets displayed on the monitor because of the graphics output device in our machine.

So, if you like, we’re on the outside looking in; and we are looking through a window on to our white image.  The colour and brightness level in our white image are correct on the inside of the system – our computer – but the viewing window or monitor might be too bright or too dark, and/or might be exhibiting a colour tint or cast.

Unless our monitor is a totally ‘clean window’ in terms of colour neutrality, then our image colour will not be displayed correctly.

And if the monitor is not running at the correct brightness then the colours and tones in our images will appear to be either too dark or too bright.  Please note the word ‘appear’…

Let’s get a bit fancy and make a greyscale in Photoshop:

monitor brightness,monitor calibration,monitor luminance,ColorMunki,i1 Display,spectrophotometer,colourimeter,ambient light,work space,photography,digital darkroom,Andy Astbury,Wildlife in Pixels,gamma,colour correction,image processing

The dots represent Lab 50 to Lab 95 – the most valuable tonal range between midtone and highlight detail.

Look at the distance between Lab 50 & Lab 95 on the three greyscales above – the biggest ‘span’ is the correctly calibrated monitor.  In both the ‘too bright & contrasty’ and the ‘too dark low contrast’ calibration, that valuable tonal range is compressed.

In reality the colours and tones in, say an unprocessed RAW file on one of our hard drives, are what they are.  But if our monitor isn’t calibrated correctly, what we ‘see’ on our monitor IS NOT REALITY.

Reality is what we need – the colours and tones in our images need to be faithfully reproduced on our monitor.

And so basically a monitor profile ensures that we see our images correctly in terms of colour and brightness; it ensures that we look at our images through a clean window that displays 100% of the luminance being sent to it – not 95% and not 120% – and that all our primary colours are being displayed with 100% fidelity.

In a nutshell, on an uncalibrated monitor, an image might look like crap, when in reality it isn’t.  The shit really starts to fly when you start making adjustments in an uncalibrated workspace – what you see becomes even further removed from reality.

“My prints come out too dark Andy – why?”

Because your monitor is too bright – CALIBRATE it!

“My pics look great on my screen, but everyone on Nature Photographers Network keeps telling me they’ve got too much contrast and they need a levels adjustment.  One guy even reprocessed one – everyone thought his version was better, but frankly it looked like crap to me – why is this happening Andy?

“Because your monitor brightness is too low but your gamma is too high – CALIBRATE it!  If you want your images to look like mine then you’ve got to do ALL the things I do, not just some of ’em – do you think I do all this shit for fun??????????……………grrrrrrr….

But there’s a potential problem;  just because your monitor is calibrated to perfection, that does NOT mean that everything will be golden from this point on

Monitor Viewing Conditions

So we’re outside taking a picture on a bright sunny day, but we can’t see the image on the back of the camera because there’s too much daylight, and we have to dive under a coat with our camera to see what’s going on.

But if we review that same image on the camera in the dark then it looks epic.

Now you have all experienced that…….

The monitor on the back of your camera has a set brightness level – if we view the screen in a high level of ambient light the image looks pale, washed out and in a general state of ultra low contrast.  Turn the ambient light down and the image on the camera screen becomes more vivid and the contrast increases.

But the image hasn’t changed, and neither has the camera monitor.

What HAS changed is your PERCEPTION of the colour and luminance values contained within the image itself.

Now come on kids – join the dots will you!

It does not matter how well your monitor is calibrated, if your monitor viewing conditions are not within specification.

Just like with your camera monitor, if there is too much ambient light in your working environment then your precisely calibrated monitor brightness and gamma will fail to give you a correct visualization or ‘perception’ of your image.

And the problems don’t end there either; coloured walls and ceilings reflect that colour onto the surface of your monitor, as does that stupid luminous green shirt you’re wearing – yes, I can see you!  And if you are processing on an iMac then THAT problem just got 10 times worse because of the glossy screen!

Nope – bead-blasting your 27 inches of Apple goodness is not the answer!

Right, now comes the serious stuff, so READ, INGEST and ACT.

ISO Standard 3664:2009 is the puppy we need to work to (sort of) – you can actually go and purchase this publication HERE should you feel inclined to dump 138 CHF on 34 pages of light bedtime reading.

There are actually two ISO standards that are relevant to us as image makers; ISO 12646:2015(draft) being the other.

12646 pertains to digital image processing where screens are to be compared to prints side by side (that does not necessarily refer to ‘desktop printer prints from your Epson 3000’).

3664:2009 applies to digital image processing where screen output is INDEPENDENT of print output.

We work to this standard (for the most part) because we want to process for the web as well as for print.

If we employ a print work flow involving modern soft-proofing and otherwise keep within the bounds of 3664 then we’re pretty much on the dance-floor.

ISO 3664 sets out one or two interesting and highly critical working parameters:

Ambient Light White Point: D50 – that means that the colour temperature of the light in your editing/working environment should be 5000Kelvin (not your monitor) – and in particular this means the light FALLING ON TO YOUR MONITOR from within your room. So room décor has to be colour neutral as well as the light source.

Ambient Light Value in your Editing Area: 32 to 64 Lux or lower.  Now this is what shocks so many of you guys – lower than 32 lux is basically processing in the dark!

Ambient Light Glare Permissible: 0 – this means NO REFLECTIONS on your monitor and NO light from windows or other light sources falling directly on the monitor.

Monitor White Point – D65 (under 3664) and D50 (under 12646) – we go with D65.

Monitor Luminance – 75 to 100 cdm2 (under 3664) and 80 to 120 cdm2 (under 12646 – here we begin to deviate from 3664.

We appear to be dealing with mixed reference units, but 1 Lux = 1 cdm2 or 1 candela per square metre.

The way Monitor Brightness or Luminance relates to ambient light levels is perhaps a little counter-intuitive for some folk.  Basically the LOWER your editing area Lux value the LOWER your Monitor Brightness or luminance needs to be.

Now comes the point in the story where common sense gets mixed with experience, and the outcome can be proved by looking at displayed images and prints; aesthetics as opposed numbers.

Like all serious photographers I process my own images on a wide-gamut monitor, and I print on a wide-gamut printer.

Wide gamut monitors display pretty much 90% to100% of the AdobeRGB1998 colour space.

What we might refer to as Standard Gamut monitors display something a little larger than the sRGB colour space, which as we know is considerably smaller than AdobeRGB1998.

monitor brightness,monitor calibration,monitor luminance,ColorMunki,i1 Display,spectrophotometer,colourimeter,ambient light,work space,photography,digital darkroom,Andy Astbury,Wildlife in Pixels,gamma,colour correction,image processing

Left is a standard gamut/sRGB monitor and right is a typical wide gamut/AdobeRGB1998 monitor – if you can call any NEC ‘typical’!

Find all the gory details about monitors on this great resource site – TFT Central.

At workshops I process on a 27 inch non-Retina iMac – this is to all intents and purposes a ‘standard gamut’ monitor.

I calibrate my monitors with a ColorMunki Photo – which is a spectrophotometer.  Spectro’s have a tendency to be slow, and slightly problematic in the very darkest tones and exhibit something of a low contrast reaction to ‘blacks’ below around Lab 6.3 (RGB 20,20,20).

If you own a ColorMunki Display or i1Dispaly you do NOT own a spectro, you own a colorimeter!  A very different beast in the way it works, but from a colour point of view they give the same results as a spectro of the same standard – plus, for the most part, they work faster.

However, from a monitor brightness standpoint, they differ from spectros in their slightly better response to those ultra-dark tones.

So from a spectrophotometer standpoint I prefer to calibrate to ISO 12646 standard of 120cdm2 and control my room lighting to around 35-40 Lux.

Just so that you understand just how ‘nit-picking’ these standards are, the difference between 80cdm2 and 120 cdm2 is just 1/2 or 1/3rd of a stop Ev in camera exposure terms, depending on which way you look at it!

However, to put this monitor brightness standard into context, my 27 inch iMac came from Apple running at 290 cdm2 – and cranked up fully it’ll thump out 340 cdm2.

Most stand-alone monitors you buy, especially those that fall under the ‘standard gamut’ banner, will all be running at massively high monitor brightness levels and will require some severe turning down in the calibration process.

You will find that most monitor tests and reviews are done with calibration to the same figures that I have quoted – D65, 120cdm2 and Gamma 2.2 – in fact this non-standard set up has become so damn common it is now ‘standard’ – despite what the ISO chaps may think.

Using these values, printing out of Lightroom for example, becomes a breeze when using printer profiles created to the ICC v2 standard as long as you ‘soft proof’ the image in a fit and proper manner – that means CAREFULLY, take your time.  The one slight shortcoming of the set up is that side by side print/monitor comparisons may look ever so slightly out of kilter because of the D65 monitor white point – 6,500K transmitted white point as opposed to a 5,000K reflective white point.  But a shielded print-viewer should bring all that back into balance if such a thing floats your boat.

But the BIG THING you need to take away from the rather long article is the LOW LUX VALUE of you editing/working area ambient illumination.

Both the ColorMunki Photo and i1Pro2 spectrophotometers will measure your ambient light, as will the ColorMunki Display and i1 Display colorimeters, to name but a few.

But if you measure your ambient light and find the device gives you a reading of more than 50-60 lux then DO NOT ask the device to profile for your ambient light; in fact I would not recommend doing this AT ALL, here’s why.

I have a main office light that is colour corrected to 5000K and it chucks out 127 Lux at the monitor.  If I select the ‘measure and calibrate to ambient’ option on the ColorMunki Photo it eventually tells me I need a monitor brightness or luminance of 80 cdm2 – the only problem is that it gives me the same figure if I drop the ambient lux value to 100.

Now that smells a tad fishy to me……..

So my advice to anyone is to remove the variables, calibrate to 120 cdm2 and work in a very subdued ambient condition of 35 to 40 Lux. I find it easier to control my low lux working ambient light levels than bugger about with over-complex calibration.

To put a final perspective on this figure there is an interesting page on the Apollo Energytech website which quotes lux levels that comply with the law for different work environments – don’t go to B&Q or Walmart to do a spot of processing, and we’re all going to end up doing hard time at Her Madges Pleasure –  law breakers that we are!

Please consider supporting this blog.

Become a patron from as little as $1 per month, and help me produce more free content.

Patrons gain access to a variety of FREE rewards, discounts and bonuses.

Photoshop Save for Web

Save for Web in Photoshop CC – where the Chuff has it gone?

“Who’s moved my freakin’ cheese?”

Adobe have moved it……..

For years Photoshop has always offered the same ‘Save for Web’ or ‘Save for Web & Devices’ option and dialogue box:

save for web,Photoshop CC 2015,colour management,save for web and devices,export,quick export as JPG,export as,export prferences,Andy Astbury,Wildlife in Pixels,Adobe,

The traditional route to the ‘Save for Web’ dialogue in all versions of Photoshop prior to CC 2015.

But Adobe have embarked on a cheese-moving exercise with CC 2015 and moved ‘save for web’ out of the traditional navigation pathway:

save for web,Photoshop CC 2015,colour management,save for web and devices,export,quick export as JPG,export as,export prferences,Andy Astbury,Wildlife in Pixels,Adobe

Adobe have ‘moved your cheese’ to here, though the dialogue and options are the same.

If we take a closer look at that new pathway:

save for web,Photoshop CC 2015,colour management,save for web and devices,export,quick export as JPG,export as,export prferences,Andy Astbury,Wildlife in Pixels,Adobe

…we see that wonderful Adobe term ‘Legacy’ – which secretly means crap, shite, old fashioned, out dated, sub standard and scheduled for abandonment and/or termination.

‘THEY’ don’t want you to use it!

I have no idea why they have done this, though there are plenty of excuses being posted by Adobe on the net.  But what is interesting is this page HERE and more to the point this small ‘after thought’:

save for web,Photoshop CC 2015,colour management,save for web and devices,export,quick export as JPG,export as,export prferences,Andy Astbury,Wildlife in Pixels,Adobe

That sounds really clever – especially the bit about ‘may be’……. let’s chuck colour management out the freakin’ window and be done!

So if we don’t use the ‘legacy’ option of save for web, let’s see what happens.  Here’s our image, in the ProPhotoRGB colour space open in Photoshop CC 2015:

save for web,Photoshop CC 2015,colour management,save for web and devices,export,quick export as JPG,export as,export prferences,Andy Astbury,Wildlife in Pixels,Adobe

So let’s try the Export>Quick Export as JPG option and bring the result back into Photoshop:

save for web,Photoshop CC 2015,colour management,save for web and devices,export,quick export as JPG,export as,export prferences,Andy Astbury,Wildlife in Pixels,Adobe

Straight away we can see that the jpg is NOT tagged with a colour space, but it looks fine inside the Photoshop CC 2105 work space:

save for web,Photoshop CC 2015,colour management,save for web and devices,export,quick export as JPG,export as,export prferences,Andy Astbury,Wildlife in Pixels,Adobe

“Perfect” – yay!…………NOT!

Let’s open in with an internet browser……

save for web,Photoshop CC 2015,colour management,save for web and devices,export,quick export as JPG,export as,export prferences,Andy Astbury,Wildlife in Pixels,Adobe

Whoopsy – doopsy…!  Looks like a severe colour management problem is happening somewhere……..but Adobe did tell us:

SFW4

Might the Export Preferences help us:

save for web,Photoshop CC 2015,colour management,save for web and devices,export,quick export as JPG,export as,export prferences,Andy Astbury,Wildlife in Pixels,Adobe

In a word……..NO

Let’s try Export>Export As:

save for web,Photoshop CC 2015,colour management,save for web and devices,export,quick export as JPG,export as,export prferences,Andy Astbury,Wildlife in Pixels,Adobe

Oh Hell No!

If we open the original image in Photoshop CC 2015 in the ProPhotoRGB colour space and then go Edit>Convert to Profile and select sRGB; then select Export>Quick Export as JPG, the resulting image will look fine in a browser.  But it will still be ‘untagged’ with any colour space – which is never a good idea.

And if you’ve captioned and key worded the image then all that hard work is lost too.

So if you must make your web jpeg images via Photoshop you will only achieve a quick and accurate work flow by using the Save for Web (Legacy) option.  That way you’ll have a correctly ‘tagged’ and converted image complete with all your IPTC key words, caption and title.

Of course you could adopt the same work flow as me, and always export as jpeg out of Lightroom; thus avoiding this mess entirely.

I seriously don’t know what the devil Adobe are thinking of here, and doubtless there is or will be a work around for the problem, but whatever it is it’ll be more work for the photographer.

Adobe – if it ain’t broke then don’t fix it !!

Become a patron from as little as $1 per month, and help me produce more free content.

Patrons gain access to a variety of FREE rewards, discounts and bonuses.

Lightroom Dehaze – part 2

More Thoughts on The Lightroom Dehaze Control

With the dehaze adjustment in Lightroom (right) the sky and distant hills look good, but the foreground looks poor.

With the dehaze adjustment in Lightroom (right) the sky and distant hills look good, but the foreground looks poor.

In my previous post I did say I’d be uploading another video reflecting my thoughts on the Lightroom/ACR dehaze adjustment.

And I’ve just done that – AND I’ve made a concious effort to keep the ramblings down too..!

In the video I look at the effects of the dehaze adjustment on 4 very different images, and alternative ways of obtaining similar or better results without it.

You may see some ‘banding’ on the third image I work on – this is down to YouTube video compression.

In conclusion I have to say that I find the dehaze ‘tool’ something of an anti-climax if I’m honest. In fairly small positive amounts it can work exceptionally well in terms of a quick work flow on relatively short dynamic range images.  But I’m not a really big fan in general, and It’s possible to create pretty much the same adjustments using the existing Lightroom tools.

Become a patron from as little as $1 per month, and help me produce more free content.

Patrons gain access to a variety of FREE rewards, discounts and bonuses.

Image Retouching

 Image Retouching in Photoshop CC 2014

It’s very rare that we ever get a frame from our camera that doesn’t need retouching – that’s a FACT.

Imperfections in the frame can be both ‘behind the shutter’ and ‘in front of the lens’ – sensor dust and crud on the subject.  But you’ll take photographs where these imperfections are hard, if not impossible, to see under normal viewing.

But print that image BIG and those invisible faults will begin to be visually apparent; by which time it’s too bloomin’ late and they’ve cost you money; or worse still, a client.

The ‘visualise spots’ tool in Lightroom will show you a certain amount of ‘dust bunny’ type faults and errors, but the way Lightroom executes retouching repairs is not always ‘quite up to snuff’; and when it comes to dust, crap and other undesirables on the subject itself Lightroom will fail to recognise them in the first place.

Image retouching isn’t really all that difficult; but it can be an intensely tedious and time-consuming process.

To that end I’ve stuck these HD video lessons on my You Tube channel.

In these videos I illustrate how I deploy the Spot Healing brush, Healing Brush, Clone Tool, Patch Tool and Content Aware Fill command to carry out some basic image retouching on a shot of cutlery bright ware.

I demonstrate the addition of a ‘dust visibility’ curves adjustment layer – something that everyone should ‘get the hang’ of using – as a first step to effective image retouching.

When photographing glossy, high reflectivity subjects we need to remove the imperfections and smooth the surfaces of the subject without reducing the ‘glossiness’ and turning it matt!

Please note: a couple of these videos are in excess of 20 minutes duration and they will look better at full resolution HDV if you click the You Tube icon. Also, it takes a lot longer to do a job when you have to talk about at the same time!

I hope you get some idea as to how simple and straightforward my approach to image retouching is!

Become a patron from as little as $1 per month, and help me produce more free content.

Patrons gain access to a variety of FREE rewards, discounts and bonuses.

Lightroom CC 2015 Crash Fix.

***Attention – if you are looking for help with the problems associated with Lightroom CC 2015/Lightroom 6 version 2.0 – October 2015 – then please go to this latest post page HERE and scroll down the page for the Temporary FIX.  This Lightrom crash fix/rollback method applies to both Mac & PC users***

Lightroom CC 2015 Crash & Performance Issues – (first release).

Become a Patron!

There are a great many folk out there experiencing crash or freeze problems with the new Lightroom CC 2015.

The biggest problem, and the one that has effected me, is random crashing in the Develop Module, and a ‘jittery’ crop rotation tool.

If you have suffered from this then you will most likely have an ‘not too new’ nVidea GPU – or so it would appear.

Lightroom CC 2015 makes use of the graphics GPU acceleration on your computer, and this is ‘turned ON’ by default upon installation of the application.

But it seems that older nVidea chipsets are causing some quite considerable speed reduction problems, to the point where the application can run out of ram and basically crash.

Adobe are supposed to be creating a fix (according to the forums) but you can get around the problem really easily.

Open up Lightroom CC 2015 and go to your Lightroom preferences:

Lightroom CC 2015, crash fix, speed fix, slow down fix, clone tool,heal tool,crop tool fix, Andy Astbury,Wildlife in Pixels,Adobe,Creative Cloud,Photography Package,bug fix,Lightroom,Photoshop

On the preferences panel you’ll see a new tab called ‘Performance’

Lightroom CC 2015, crash fix, speed fix, slow down fix, clone tool,heal tool,crop tool fix, Andy Astbury,Wildlife in Pixels,Adobe,Creative Cloud,Photography Package,bug fix,Lightroom,Photoshop

You will see a checked ‘tick box’ for Use Graphics Processor – UNTICK IT, close the preferences panel and restart Lightroom CC 2015.

I’m on a mid-2009 Mac Pro running 10.10.3 Yosemite and a bog standard (for the day) nVidea Geforce GT120 512Mb graphics card.

Lightroom CC 2015 was slower than Lr5 on this machine, it would crash, the crop tool occasionally looked like it was a ‘motor neurone’ sufferer, and the heal/clone tool was harsh, pixelated and quite slow.

Turning OFF GPU acceleration has seemingly cured all my woes, and now it runs as smoothly as Lightroom 5 did but with the Photomerge options and other benefits of Lightroom CC 2015.

On that same performance tab there is a ‘system info’ button you can press that’ll give you the specifications of your machine and Lightroom installation:

Lightroom CC 2015, crash fix, speed fix, slow down fix, clone tool,heal tool,crop tool fix, Andy Astbury,Wildlife in Pixels,Adobe,Creative Cloud,Photography Package,bug fix,Lightroom,Photoshop

The word ‘Passed’ next to the Open GL support means nothing, and if you you click the ‘Learn More’ link on the performance tab of Lightroom preferences it’ll take you to THIS PAGE on the Adobe support website.

On that page you will see this:

Lightroom CC 2015, crash fix, speed fix, slow down fix, clone tool,heal tool,crop tool fix, Andy Astbury,Wildlife in Pixels,Adobe,Creative Cloud,Photography Package,bug fix,Lightroom,Photoshop

Now this explains A LOT!

Running a standard (sub 2K) 24″ monitor with sub 1Gb of VRAM, even with updated driver support for Open GL 3.3, means you are running at a resolution of 1920 pixels long edge and in effect you will not really benefit from Lightroom CC 2015 GPU acceleration in the first place.

I’m also running Lightroom CC 2015 on a mid 2011 27″ non-retina iMac with a horizontal resolution of 2560 pixels and an ATI Radion HD 6770M 512Mb graphics chipset.  This machine hasn’t crashed as such, but is certainly better run with the GPU acceleration turned OFF too.

Here is a very rough test you can do:

  1. Open a FULL RESOLUTION image in the Develop module.
  2. Pick up the Heal/Clone tool and set it to Heal with the opacity & feather controls to 100%
  3. Paint a random stroke on the image, and while painting, look carefully at the white edges of the stroke – are they smooth and feathered, or harsh and slightly granular?
  4. If they are the latter the go and turn OFF GPU acceleration and repeat the process – you will see the edges of the stroke look much better.
Lightroom CC 2015, crash fix, speed fix, slow down fix, clone tool,heal tool,crop tool fix, Andy Astbury,Wildlife in Pixels,Adobe,Creative Cloud,Photography Package,bug fix,Lightroom,Photoshop

Click to view LARGER

So, think of it this way; Adobe have put a facility into Lightroom 6/CC 2015 that makes use of very latest up to date computer graphics systems AND it’s ‘active’ by default.

If you run a new iMac 27″ Retina then you are running 5120 pixels on the long edge – that’s 5K graphics, and the new GPU acceleration will help you.

If your system fails to meet the operating criteria then having the acceleration active will cause you problems.  The severity of the problems you experience will be proportional to how ‘out of date’ your graphics are; so TURN IT OFF !

I can’t speak about installations of Lightroom CC 2015 under the Windows operating systems, but looking at the forums it seems that the same sort of problems exist for PC users.

A friend called this morning saying that the default installation ran smoothly and at warp-speed on his new retina macbook, but was noticeably slower than Lightroom 5 on his desktop PC – same problem, same fix.

Crash and slow-down problems with Lightroom CC 2015 are not OS problems – they are GPU VRAM/RAM problems, so don’t waste your time defraging hard drives and running system ‘junk checks’ if Lightroom 5 ran well.

 

Lightroom CC 2015 Launch Hang Problem?

Lightroom CC 2015, crash fix, speed fix, slow down fix, clone tool,heal tool,crop tool fix, Andy Astbury,Wildlife in Pixels,Adobe,Creative Cloud,Photography Package,bug fix,Lightroom,Photoshop

If you are experiencing launch hang, splash screen hang or crashing of the application on launch then GO HERE where you’ll see the instructions in the image above.

Kyle Bailey kindly sent me a solution/fix for a windows crash fix if you literally can’t uncheck the graphics acceleration check box:

Thanks for pointing me in the right direction, Andrew, but I couldn’t untick the graphics processor box –Lightroom would crash when I tried. I just spent a couple hours with tech support and thought I’d share our solution:

Close LR first. Open device manager, double click on display adapters, right-click your graphics card (mine was AMD Radeon), choose install drivers, browse system, pick from list. Make NOTE of which is currently active, then change it to standard VGA. It may prompt you to reboot, but don’t do it.

This will make the screen look crazy, but don’t worry! Now, open LR, untick the graphics box, and close LR.

Finally, go back into device manager and change it back to the original driver and viola. Next time you start LR, the box will remain unticked.

Cheers for that Kyle.

 

Become a patron from as little as $1 per month, and help me produce more free content.

Patrons gain access to a variety of FREE rewards, discounts and bonuses.

Please consider supporting this blog.

Become a Patron!
 

Lumenzia for Wildlife

The Lumenzia Photoshop extension

Yet more on the usefulness of the Lumenzia Photoshop extension, the short cut to great looking images of all types and styles.

I had an email from client and blog follower David Sparks after my last post about this useful mighty Photoshop tool.

He sent these before and after rail shots:

20141002-_D4S6303

Before adding Lumenzia. Click for larger view.

After adding Lumenzia

After adding Lumenzia. Click for larger view.

difference

Comparison overlay – see how the left side of the image has that extra presence – and that’s just with the click of a couple of buttons in the Lumenzia GUI. Click to view larger.

Here is what David had to say in his email:

Andy, here is a before and after.  Processing was much, much faster than usual, using Lumenzia.

Thanks for bringing it to my attention….I’m working my way through your Image Processing in LR4 & Photoshop + LR5 bundle and enjoying it very much.

And as my friend and blog follower Frank Etchells put it:

Excellent recommendation this Andy. Bought it first time from your previous posting… at just over £27 it’s marvellous :)

What gets me puzzled is the fact that these Lumenzia posts have had over 500 separate page views in the last few days but less then 3% of you have bought it – WTF are you guys waiting for…

Get it BOUGHT – NOW – HERE

UPDATE: Greg Benz (the plugin author) has launched a comprehensive Lumenzia training course – see my post here for more information.

Become a patron from as little as $1 per month, and help me produce more free content.

Patrons gain access to a variety of FREE rewards, discounts and bonuses.

Lumenzia – Not Just for Landscapes

Luminosity Masking is NOT just for landscape photographs – far from it.

But most folk miss the point of luminosity masking because they think it’s difficult and tedious.

The point, as I always see it, is that luminosity masking allows you to make dramatic but subtle changes and enhancements to your image with what are actually VERY fast and crude “adjustments”.

This in reality means that luminosity masking is FAST – and way faster than trying to do “localised” adjustments.  But the creation of the masks and choosing which one to use is what crippled the “ease factor” for most.

But with this new Lumenzia extension is so snappy and quick at showing you the different masks that, if you know what area of the image you want to adjust, the whole process takes SECONDS.

Let’s look at a White-tailed Eagle taken just 15 days ago:

Straight off the 1Dx it looks like this:

RAW unprocessed .CR2 file

RAW unprocessed .CR2 file (CLICK to view in new window)

Inside the Develop Module of Lightroom 5 it looks like:

camera

RAW unprocessed – (CLICK to view in new window)

A few tweaks later and it looks like:

Lr5adjust

Tweaks are what you can see in the Basics Panel + CamCal set to Neutral, and Chroma Noise removal in the Lens Corrections Panel is turned ON – (CLICK to view in new window)

Sending THIS adjusted image to Photoshop:

ps1

(CLICK to view in new window)

All I want to do is give a “lift” to the darker tones in the bird; under the wings, and around the side of head, legs and tail.

Using a BRUSH to do the job is all fine ‘n dandy BUT, you would be creating a localised adjustment that’s all-encompassing from a tonal perspective; all tones that fell under the brush get adjusted by the same amount.

A luminosity mask, or indeed ANY pixel-based mask is exactly what it says it is – a mask full of pixels. And those pixels are DERIVED from the real pixels in your image.  But the real beauty is that those pixels will be anywhere from 1% to 100% selected, or not selected at all.

Where they are 100% selected they are BLACK, and any adjustment you make BEHIND that mask will NOT be visible.

Pixels that are NOT selected will be WHITE, and your adjustment will show fully.

But where the pixels are between 1% and 99% selected they will appear as 1% GREY to 99% grey and so will show or hide variation of said adjustment by the same amounts…got it?

The Lumenzia D4 mask looks like it’ll do the job I want:

(CLICK to view in new window)

Lumenzia D4 mask (CLICK to view in new window)

Click the image to view larger – look at the subtle selections under those wings – try making that selection any other way in under 2 seconds – you’ve got no chance!

The “lift” I want to make in those WHITER areas of the mask is best done with a Curves Adjustment layer:

Select "Curve" in the Lumenzia GUI - (CLICK to view in new window)

Select “Curve” in the Lumenzia GUI – (CLICK to view in new window)

So hit the Curve button and voilà:

The Lumenzia D4 mask is now applied to Curves Adjustment Layer - (CLICK to view in new window)

The Lumenzia D4 mask is now applied to Curves Adjustment Layer – (CLICK to view in new window)

You can see in the image above that I’ve made a very rough upwards deflection of the curve to obtain an effective but subtle improvement to those under-wing areas etc. that I was looking to adjust.

The total time frame from opening the image in Photoshop to now is about 20 seconds!  Less time than the Lightroom 5 adjustments took…

And to illustrate the power of that Lumenzia D4 Luminosity mask, and the crudity of the adjustment I made, here’s the image WITHOUT THE MASK:

The effect of the luminosity mask is best illustrated by "hiding" it - bloody hell, turn it back on ! - (CLICK to view in new window).

The effect of the luminosity mask is best illustrated by “hiding” it – bloody hell, turn it back on ! – (CLICK to view in new window).

And at full resolution you can see the subtleties of the adjustment on the side of the head:

ll+lum

With Lumenzia (left) and just the Lightroom 5 processing (right) – (CLICK to view in new window).

If you want to get the best from your images AND you don’t want to spend hours trying to do so, then Lumenzia will seriously help you.

Clicking this link HERE to buy Lumenzia doesn’t mean it costs you any more than if you buy it direct from the developer.  But it does mean that I get a small remuneration from the developer as a commission which in turn supports my blog.  Buying Lumenzia is a total no-brainer so please help support this blog by buying it via these links – many thanks folks.

UPDATE June 2018: Greg Benz (the plugin author) has launched a comprehensive Lumenzia training course – see my post here for more information.

Become a patron from as little as $1 per month, and help me produce more free content.

Patrons gain access to a variety of FREE rewards, discounts and bonuses.

Lumenzia for Easy Luminosity Masking

Lumenzia for Easy Luminosity Masking..

I’m a really BIG user of luminosity masking techniques, and the ease by which you can use them to create really powerful adjustments to your image inside Photoshop – adjustments that are IMPOSSIBLE to make in Lightroom.

For a while now I’ve been selling a luminosity mask action set for Photoshop, and up until a week ago I had plans to upgrade said action set to produce even more custom masks.

That is until a good friend of mine, Mr. Omar Jabr, asked me if I’d come across this new product, LUMENZIA, that made the production and deployment of luminosity masks and their derivatives EVEN EASIER.

Lumenzia,luminosity masking,Andy Astbury,Wildlife in Pixels Blog

An original RAW file open in Lightroom (right) together with the final image (left) – 99% of the “heavy lifting” being done in Photoshop using the Lumenzia Extension and it’s luminosity masking functions.

In all honesty I am so excited about this amazing software extension that I’ve abandoned all plans to further develop my own action set for Photoshop – to do so would be a truly pointless exercise.

There is so much more to Lumenzia than the production of the standard 4 or 5 Darks,Lights and Midtone luminosity masks that mine and other available action sets produce.

To get an idea of just how powerful Lumenzia is just click HERE to visit the applications home page – and just buy it while you are there; purchase is a “no brainer” and one of those digital imaging JDI’s (just do it)!

The inclusion of a luminosity masking function based on the Zone System gives you instant recourse to masks based on Ansel Adams 11 zone system of scene brightness – a classic approach to the quantification of subject brightness range created by arguably the greatest landscape photographer the world has ever known – IMHO of course.

Lumenzia,luminosity masking,Andy Astbury,Wildlife in Pixels Blog

In order to instal Lumenzia you will need to install the correct Photoshop Extension Manager for which ever version of Photoshop you are running – CS6, CC, or CC2014 (it is not intended to be installed on CS5 or lower).

1. Buy Lumenzia

2. Follow the download link, and download the .Zip folder.

3. Extract the folder contents.

4. Locate the “com.lumenzia.zxp” file in the extracted contents, right click and choose Open with: Adobe Extension Manager v.xx

You should see:

Lumenzia,luminosity masking,Andy Astbury,Wildlife in Pixels Blog

Click Install, and you should see:

Lumenzia,luminosity masking,Andy Astbury,Wildlife in Pixels Blog

If you are running Mac OS 10.10x Yosemite you may have a slight problem with the CC2014 Extension Manager not being able to find the application pathway to Ps CC2014.  If you get a message from the Extension Manager waffling on about needing Photoshop v11 or higher don’t stress, the fix is a little brutal but really simple:

Go Applications>Utilities>Adobe Installers and UNINSTALL (that’s right!) BOTH Photoshop CC2014 and Extension Manager CC2014, then log back in to your CC account, go to the Apps tab and re-install Photoshop CC2014 AND Extension Manager CC2014 sequentially – that will cure the problem and only take about 5 or 6 minutes.

Open a RAW file in CameraRAW, or better still Lightroom. Get your camera calibration and contrast under control as I’ve banged on about so many times before, negate any chromatic aberration and do a bit of effective noise reduction if needed, then send the image to Photoshop:

Lumenzia,luminosity masking,Andy Astbury,Wildlife in Pixels Blog

Go Window>Extensions>Lumenzia

Go Window>Extensions>Lumenzia and the Lumenzia interface will appear – I like to drag it into the right hand tools palette so it’s not encroaching on the work area.

The first thing that amazed me about Lumenzia is the fact that you can create luminosity masks without creating 12 or 15 separate Alpha channels with the image – this makes a HUGE difference to the file size of the image, not just from the disc space PoV but it can also have file handling speed benefits in terms of tile rendering speed and scratch disc usage – if you don’t understand that just think of it as a GOOD thing!

For example:

5

The final adjusted image (prior to a couple of tweaks in Lightroom) on the left is 271Mb including all layers being intact; the image on the right, though not yet processed, has been prepared for processing by running a luminosity mask action set and developing a stack of Alpha channels; it is now over 458Mb:

Lumenzia,luminosity masking,Andy Astbury,Wildlife in Pixels Blog

…just because of the Alpha channels. And we have also got 50 steps of History that have to be retained by Photoshop; as you’ve now realised, the joke is that it’s double the size of the Lumenzia processed image and we haven’t begun to start making any adjustments yet!

There is lot’s more to Lumenzia, such as surface sharpening and easy dodge and burn layer creation – it’s going to take me a week to digest it all.

Prior to working with Lumenzia my one question was “how good are the masks” – well they are pixel-perfect.

Creating pixel-perfect luminosity masks is the most tedious of jobs if you do it the maual way – so much so that most folk take one look at the process and go “No thanks…..”

Photographers like myself couldn’t really help alleviate the tedium until the advent of CS6 which gave us the ability to write an ACTION that involved the operation of a PREVIOUSLY recorded action – so the luminosity mask action set was born.

But the developer of Lumenzia has topped it all by the proverbial country mile and given us a totally unique way of making the tedious and complex very easy and simple.

Once you have made your purchase you’d do well to go and watch the developer videos that are available online; you will get links to the training and support pages in your purchase receipt.

And to top it all off we can even generate Alpha channels and selections if we want or need to, and we can mask on the basis of Vibrancy and Saturation; yet another processing wheeze known by few, and used by fewer still.

The developer has given me permission to demonstrate and teach the deployment of Lumenzia, and to promote it as an affiliate.  I’ve been offered affiliate-ships before but have rejected them in the past because basically what was being peddled was either crap or too expensive; or BOTH.

But whatever you think the opinion of yours truly is worth, I can honestly say that Lumenzia is most definitely NEITHER of the above – it’s that good I’ll never use anything else ever again, and at under 40 bucks you’re going to make one hell of a difference to your images with so little effort it’s unreal.

Click HERE to buy and download

LUMENZIA – BUY IT – go on, get on with it!

Lumenzia,luminosity masking,Andy Astbury,Wildlife in Pixels Blog

Lumenzia GUI for Photoshop CC2014

UPDATE June 2018: Greg Benz (the plugin author) has launched a comprehensive Lumenzia training course – see my post here for more information.

Become a patron from as little as $1 per month, and help me produce more free content.

Patrons gain access to a variety of FREE rewards, discounts and bonuses.

Please consider supporting this blog.

Parallel Horizontals.

Quite often when shooting landscapes, or more commonly seascapes, you may run into a problem with parallel horizontals and distortion between far and near horizontal features such as in the image below.

Parallel horizontals that are not parallel - but should be!

Parallel horizontals that are not parallel – but should be!

This sort of error cannot be fully corrected in Lightroom alone; we have to send the image to Photoshop in order to make the corrections in the most efficient manner.

Here’s a video lesson on how to effectively do just that, using the simplest, easiest and quickest of methods:

You can watch the video at full size HERE – make sure you click the HD icon.

This is something which commonly happens when photographing water with a regular shaped man-made structure in the foreground and a foreshortened horizon line such as the receding opposite shore in this shot.  But with a little logical thought these problems with parallel horizontals being “out of kilter” can be easily cured.

Become a patron from as little as $1 per month, and help me produce more free content.

Patrons gain access to a variety of FREE rewards, discounts and bonuses.

Photoshop CC Update

Photoshop CC Update

Installing a new Photoshop CC update is supposed to be a simple matter of clicking a button and the job gets done.

This morning both my Mac systems were telling me to update from v14.1.2 to v14.2

I have two Macs, a late 2012 iMac and a mid 2009 Mac Pro.  The Mac Pro used to run Snow Leopard but was upgraded to Mountain Lion because of Lightroom 5 dropping Snow Leopard support.

Now I never have any problems with Cloud Updates from Adobe on the iMac, but sometimes the Mac Pro can do some strange things – and this morning was no exception!

The update installed on the iMac without a hitch, but when the update was complete on the Mac Pro I was greeted with a message telling me that some components had not installed correctly.  On opening Photoshop CC I was greeted with the fact that the version had rolled back to v14.0 and that hitting UPDATE in both the app and my CC control panel simply informed me that my software was up to date and no updates were available!

So I just thought I’d do a blog entry on what to do if this ever happens to you!

 

Remove Photoshop CC

The first thing to do is UNINSTALL  Photoshop CC with the supplied uninstaller.

You’ll find this in the main Photoshop CC root directory:

Photoshop CC Update

Locate the Photoshop CC Uninstaller.

Take my advice and put a tick in the check box to “Remove Preferences” – the Photoshop preferences file can be a royal pain in the ass sometimes, so dump it – a new one will get written as soon as your fire Photoshop up after the new install.

Click UNINSTALL.

Once this action is complete YOU MUST RESTART THE MACHINE.

 

After the restart wait for the Creative Cloud to connect then open your CC control panel.

Under the Apps tab you’ll see that Photoshop CC is no longer listed.

Scroll down past all the apps Adobe have listed and you’ll come to Photoshop CC;  it’ll have an INSTALL button next to it – click the install button:

Photoshop CC Update

Install Photoshop CC from the Cloud control panel.

If you are installing the 14.1.2 to 14.2 update (the current one as of today’s date) you might find a couple of long ‘stick bits’ during the installation process – notably between 1 and 20% and a long one at 90% – just let the machine do it’s thing.

When the update is complete I’d recommend you do a restart – it might not be necessary, but I do it anyway.

Once the machine has restarted fire up Photoshop, click on ‘About Photoshop’ and you should see:

Photoshop CC Update

Photoshop “about screen” showing version number.

Because we dumped the preferences file we need to go and change the defaults for best best working practice:

Photoshop CC Update

Preferences Interface tab.

If you want to change the BG colour then do it here.

Next, click File Handling:

Photoshop CC Update

File handling tab in Photoshop Preferences

Remove the tick from the SAVE IN BACKGROUND check box – like the person who put it there, you too might think background auto-save is a good idea – IT ISN’T – think about it!

Finally, go to Performance:

Photoshop CC Update

Photoshop preferences Performance tab

and change the Scratch Disc to somewhere other than your system drive if you have the internal drives fitted.  If you only have 1 internal drive then leave “as is”.  You ‘could’ use an external drive as a scratch disk, but to be honest it really does need to be a fast drive over a fast connection – USB 2 to an old 250Gb portable isn’t really going to cut it!

You can go and check your Colour Settings, though these should not have changed – assuming you had ’em set right in the first place!

Here’s what they SHOULD look like:

Photoshop CC Update

Photoshop PROPER COLOUR SETTINGS!

That’s it – you’re done!

Become a patron from as little as $1 per month, and help me produce more free content.

Patrons gain access to a variety of FREE rewards, discounts and bonuses.

Please consider supporting this blog.

This blog really does need your support. All the information I put on these pages I do freely, but it does involve costs in both time and money.

If you find this post useful and informative please could you help by making a small donation – it would really help me out a lot – whatever you can afford would be gratefully received.

Your donation will help offset the costs of running this blog and so help me to bring you lots more useful and informative content.

Many thanks in advance.