Lightroom Classic CC Update 7.5 – August 22nd 2018
This morning I updated Lightroom Classic CC to the latest version 7.5.
And likewise I suggest you all do the same thing.
It’s not very often you hear or see me being very positive about Lightroom, but this latest iteration has me impressed for sure.
There has been the usual added camera support, together with some fangled update to the book module with some new Blurb templates – but that’s all inconsequential in my eyes and just so much froofroo.
No, the big improvement on all 3 of my machines here is one of SPEED.
And in particular, large catalogue load-speed.
I have one particular catalogue that sits on a raided pair of hard drives, and it contains just under 70,000 images.
This catalogue normally takes quite some time to open fully and it’s something of a torture-test for Lightroom.
But as of this mornings update not any more it would seem – the catalogue opened and all 69,865 previews were in place in under 10 seconds.
So would I recommend you install this latest update?
You betcha I would….always bearing in mind that Lightroom is notorious for varied performance on different individual systems – so I accept ZERO, NIL, NADA, нуль responsibility!
One negative thing that DID occur twice, but I couldn’t replicate in the video nor since – the infamous PANEL BLACKOUT.
They usually occur in the Develop module and your left and right panels just ‘black out’, and all you can see is your image.
If you do suffer a panel blackout though, don’t panic!
Just hit the G key to take you back to the Library Grid View then hit the D key to go back to the Develop module – you should get your panels back immediately.
I’ll keep you updated if I find any problems over the next few days and weeks, and if you have any problems just let me know.
When we shoot ETTR (expose to the right) in bright, harsh light, Lightroom can sometimes get the wrong idea and make a real ‘hash’ of rendering the raw file.
Sometimes it can be so bad that the less experienced photographer can get the wrong impression of their raw file exposure – and in some extreme cases they may even ‘bin’ the image thinking it irretrievably over exposed.
I’ve just uploaded a video to my YouTube channel which shows you exactly what I’m talking about:
The image was shot by my client and patron Paul Smith when he visited the Mara back in October last year, and it’s a superb demo image of just how badly Lightroom can demosaic a straight forward +1.6 Ev ETTR shot.
Importing the raw file directly into Lightroom gives us this:
But importing the raw file directly into RawTherapee with no adjustments gives us this:
Just look at the two histogram versions – Lightroom is doing some crazy stuff to the image ‘in the background’ as there are ZERO develop settings applied.
But if you watch the video you’ll see that it’s quite straight forward to regain all that apparent ‘blown detail’.
And here’s the important bit – we do so WITHOUT the use of the shadow or highlight recovery sliders. Anyone who has purchased my sharpening videos HERE knows that those two sliders can VERY EASILY cause undesirable ‘pseudo-sharpening’ halos, and they should only be used with caution.
The way I process this +1.6 stop ETTR exposure inside Lightroom has revealed all the superb mid tone detail and given us a really good image that we could take into Photoshop and improve with some precision localized adjustments.
So don’t let Lightroom control you – you need to control IT!
If you feel this article and video has been beneficial to you and would like to see more per week, then supporting my Patreon page for as little as $1 per month would be a massive help. Thanks everyone!
We’ve just had a new update for Lightroom Classic CC which upgrades us to Lightroom 7.4
I’ve just made a short video about how we can make use of one of the updates main features to tidy up those Profiles in the profile browser of the Develop module.
You can see the video here:
My Thoughts:
Being able to manage the visibility of those profile groups in the develop module is a real bonus, because if nothing else, it frees up screen real-estate.
We still can’t stop the ‘hover preview’ of any profile – a LOT of people on the Adobe forums have found this very annoying over the last 2 months since the issue of v7.3
You CAN turn it off under the Lightroom Preferences>Performance tab – but this is for presets only – it doesn’t turn the hover preview off for profiles.
We can also add color labels to folders, and search folders. Some people might find this useful, especially those who work in one master catalogue, and some like me find this update ‘window dressing Fru-Fru’ – a new technical term there folks!
Lightroom 7.4 now supports HEVC and HEIF images and video from the latest Apple iOS systems and devices.
And the forth ‘improvement’ applies to Photomerge HDR and Pano where the end merge result can be stacked on top of the component images. As I say in the video, this is possibly the answer to a question no one was asking – I’ve not seen a single request for this on any of the the Lightroom forums in the last 2 months.
So watch the video and explore the update on your own machine – you might be more impressed than I am! But at least Adobe haven’t broken Lightroom 7.4 anymore than it was already, so let’s be thankful for small mercies ehh!
Well, I’d like to say the past week has been a blast, but Adobe screwed any chance of that happening by releasing version 7.3 of Lightroom on the 3rd/4th.
The week actually started off quite well with me uploading a Raw Therapee basic “get you started’ video:
I’d planned to get out and do some photography, and do some serious SEO work on my YouTube channel.
But when I turned my machines on at 6.15am on the 4th I was greeted with some queries from clients and blog/channel viewers about some new fangled update for Lightroom.
Then the CC update panel told me I had application updates for Photoshop and Lightroom, so we clicked update on both.
I’m a bit of a Photoshop junkie, and I always look forward to any update if I’m honest, just so I can go and have a play with it!
But I’ve been a bit ‘meh..’ over Lightroom for quite a while now, for a few reasons.
Firstly, it’s trying to become some sort of pathetic 1 stop shop image processor, catering to the ‘instant gratification brigade’ INSTEAD OF what it’s meant to be – a superb digital asset management program and a raw processor designed to work in conjunction with the KING of image processors – PHOTOSHOP.
Secondly, it’s unique demosaicing algorithm is ludicrously outdated in comparison to C1, Iridient and RT, and its capture/input sharpening controls leave a lot to be desired. Anyone who has been sensible and bought my massive sharpening training knows exactly what I’m talking about here, as I demonstrate these facts more than a few times!
In point of fact, on the demosaicing front, it’s not as clever as that found in either Canon DPP or Nikon Capture.
But, with a bit of patience and effort, you can strip all the crap background adjustments away, and get back to a relatively neutral starting point; as I’ve discussed many times previously on this blog.
So, once the updates were done, and I’d had a quick look at Photoshop, I fired up the new Lightroom v7.3 – and immediately wished I hadn’t!
Heading over to the Adobe Lightroom Forum I see A LOT of very upset users.
Strangely enough though, heading over to YouTube I see the exact opposite!
But, positive or negative, all the buzz is about the new profiles.
Lightroom v7.3 Profiles
There are tens of thousands of Lightroom v7.3 fan boys out there, plus even more users with a low level knowledge base, who do NOT understand what a ‘profile’ is – and Adobe are using this as a massive marketing tool.
Lightroom v7.3 profiles are simply Lightroom v7.2 PRESETS, re-bundled into something called a profile, and shoved into a different location in the Lightroom GUI.
The subtle difference is this – if you have a preset that gives a ‘certain look’ to an image, when you apply it, the relevant sliders in the dev module move.
But if you have a ‘profile’ that gives the same visual appearance, when you apply it the relevant sliders DON”T move.
A PRESET is a visible, front GUI adjustment, and a PROFILE is a buried, background adjustment.
You’ll see this corroborated by an Adobe Forum Moderator a little later on..
A preset shows up in the control sliders, and you can easily tweak these after applying the preset.
Application of a PROFILE however, gives you no control indication of what it’s done, so you can’t tweak its adjustments because you can’t see them.
Profiles just pander to people who basically want Adobe to process their images for them – harsh, but true.
Presets – for me, the few that I make are simply to save time in applying settings to remove Adobes processing of my images.
But for years there has been a third party after-market revenue stream in preset bundles from certain photography trainers – buy these and your images will look like mine! So presets too steered their purchasers away from actually processing their own images, but at least those presets were designed by photographers!
Anyway, for those that haven’t seen the two videos I upload to YouTube about Lightroom v7.3 they are embedded below:
I was expecting a mixed response to those videos, from the sane and sensible:
Click me – good old Franky!
Click me
to the plain stupid:
Click me – I’m worth a read!
but I wasn’t expecting the raft of these, this is the tamest:
You have to have a thick skin if you stick videos on YouTube, but what the f**k does a comment like that achieve?
Anyway, F**K all that. At the end of the first video I do say that if I find anything out about the new default sharpening amount in Lightroom v7.3 I would let you know in a blog article.
So I headed over to the Adobe Lightroom Forum to beg the question – it only took 10 minutes and an Adobe moderator addressed the question, and a bit more besides.
I’ve screen-grabbed it so please click the image below to read it:
I’m interesting so CLICK ME!
So, the important take-aways are:
nothing has changed
and
part of an effort by Adobe to offer a more pleasing “out-of-the-box” rendering
and
At the ‘base’ level nothing has changed. The demosaicing algorithm is unchanged, MelissRGB is still the default colour space within the UI, and the Adobe Standard profile (DCP) for each supported camera is also unchanged. Likewise, the Camera Matching profiles are unchanged.
and
All of the new Adobe Raw and Creative profiles are built on top of Adobe Standard (i.e. Adobe Standard remains the base profile for all supported cameras). As such, these XMP based profiles apply settings under-the-hood.
Conclusion.
So basically the whole version update is geared SOLELY towards people with a camera who want instant gratification by allowing Adobe techs to process their images for them.
As someone who’s understood the photography process, and watched it evolve over the last 40 years, I count myself as something slightly more than just a fat bloke with a camera.
Forget about all this “I care about my images” garbage – I KNOW what constitutes a technically sound image, and ever since the inception of PV2012, Lightroom has been on a slippery slope towards losing it’s full professional image maker credibility.
Like many others, I still use Lightroom, and I always will. As I said before, it excels in Digital Asset Management, and it’s Soft Proofing and Print facilities are really without equal.
Have they improved any of those features? In a nutshell, NO.
My monthly subscription has gone up by £25 a year, and for my money I’ve now got even more work to do inside the dev module to make sense of my raw files. If you’ve lost the understanding of what I mean, go and watch the 2nd video again!
Am I even remotely thinking about dropping my subs and using another application?
I might look like a cabbage, but I’m not one! My £120+ buys me access to a constantly updated installation of the finest image processor on the face of Gods Earth – the mighty Photoshop.
And for those without the required level of prior knowledge, that privilege used to cost in excess of £800+ plus serious upgrade fees every couple of years. That’s why there was such ripping ‘trade’ in torrenting and cracked copies!
So overall, I’m quids-in, and I can think of Lightroom as something of a freebie, which makes even Lightroom v7.3 good VFM.
Added to that, I can always open a raw file in RT and get a 16bit ProPhotoRGB tiff file into Photoshop that’ll kick Lightrooms version into the last millennium.
But I can’t help it, I do resent deeply the road down which the Adobe bosses are taking Lightroom.
What they should have done is make CC into an idiots version, and re-worked the Classic CC into a proper raw editor with multiple choices for demosaicing, a totally re-worked input sharpening module, and interface the result with the existing Print, Soft-Proof and DAM.
But of course, that would cost them money and reduce their profit margin – so there’s no chance of my idea ever coming to fruition.
I take my hat off to the guys in the C1 dev team, but C1 is far too hostile an environment for any of those thousands of idiots who love the new Lightroom profiles – because that would mean they’d need to do some actual processing work!
And if C1 is hostile, then RT is total Armageddon – hell, it even sends me into a cold sweat!
But photography has always been hard work that demanded knowledge before you started, and a lot of hard learning to acquire said knowledge.
Hard work never hurt anyone, and when does the path of least resistance EVER result in the best possible outcome?
Never – the result is always an average compromise.
And good image processing is all about the BEST IMAGE POSSIBLE from a raw file.
Which brings me nicely back to my sharpening training – get it bought you freebie-hunting misers! GO ON – DO IT NOW – BEFORE YOU FORGET and before I die of starvation!
DO 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.
A lot of people imagine that there is some sort of ‘magic bullet’ method for sharpening images.
Well, here’s the bad news – there isn’t !
Even if you shoot the same camera and lens combo at the same settings all the time, your images will exhibit an array of various properties.
And those properties, and the ratio/mix thereof, can, and will, effect the efficacy of various sharpening methods and techniques.
And, those properties will rarely be the same from shoot to shoot.
Add interchangeable lenses, varied lighting conditions, and assorted scene brightness and contrast ranges to the mix – now the range of image properties has increased exponentially.
What are the properties of an image that can determine your approach to sharpening?
I’m not even going to attempt to list them all here, because that would be truly frightening for you.
But sharpening is all about pixels, edges and contrast. And our first ‘port of call’ with regard to all three of those items is ‘demosaicing’ and raw file conversion.
“But Andy, surely the first item should be the lens” I here you say.
No, it isn’t.
And if that were the case, then we would go one step further than that, and say that it’s the operators ability to focus the lens!
So we will take it as a given, that the lens is sharp, and the operator isn’t quite so daft as they look!
Now we have a raw file, taken with a sharp lens and focused to perfection.
Let’s hand that file to two raw converters, Lightroom and Raw Therapee:
I am Lightroom – Click me!
I am Raw Therapee – Click me!
In both raw converters there is ZERO SHARPENING being applied. (and yes, I know the horizon is ‘wonky’!).
Now check out the 800% magnification shots:
Lightroom at 800% – Click me!
Raw Therapee at 800% – Click me!
What do we see on the Lightroom shot at 800%?
A sharpening halo, but hang on, there is NO sharpening being applied.
But in Raw Therapee there is NO halo.
The halo in Lightroom is not a sharpening halo, but a demosaicing artifact that LOOKS like a sharpening halo.
It is a direct result of the demosaicing algorithm that Lightroom uses.
Raw Therapee on the other hand, has a selection of demosaicing algorithms to choose from. In this instance, it’s using its default AMaZE (Alias Minimization & Zipper Elimination) algorithm. All told, there are 10 different demosaic options in RT, though some of them are a bit ‘old hat’ now.
There is no way of altering the base demosaic in Lightroom – it is something of a fixed quantity. And while it works in an acceptable manner for the majority of shots from an ever burgeoning mass of digital camera sensors, there will ALWAYS be exceptions.
Let’s call a spade a bloody shovel and be honest – Lightrooms demosaicing algorithm is in need of an overhaul. And why something we have to pay for uses a methodology worse than something we get for free, God only knows.
It’s a common problem in Lightroom, and it’s the single biggest reason why, for example, landscape exposure blends using luminosity masks fail to work quite as smoothly as you see demonstrated on the old Tube of You.
If truth be told – and this is only my opinion – Lightroom is by no means the best raw file processor in existence today.
I say that with a degree of reservation though, because:
It’s very user friendly
It’s an excellent DAM (digital asset management) tool, possibly the best.
On the surface, it only shows its problems with very high contrast edges.
As a side note, my Top 4 raw converters/processors are:
Iridient Developer
Raw Therapee
Capture One Pro
Lightroom
Iridient is expensive and complex – but if you shoot Fuji X-Trans you are crazy if you don’t use it.
Raw Therapee is very complex (and slightly ‘clunky’ on Mac OSX) but it is very good once you know your way around it. And it’s FREEEEEEEEE!!!!!!!
Iridient and RT have zero DAM capability that’s worth talking about.
Capture One Pro is a better raw converter on the whole than Lightroom, but it’s more complex, and its DAM structure looks like it was created by crack-smoking monkeys when you compare it to the effective simplicity of Lightroom.
If we look at Lightroom as a raw processor (as opposed to raw converter) it encourages the user to employ ‘recovery’ in shadow and highlight areas.
Using BOTH can cause halos along high contrast edges, and edges where high frequency detail sits next to very low frequency detail of a contrasting colour – birds in flight against a blue sky spring to mind.
Why do I keep ‘banging on’ about edges?
Because edges are critical – and most of you guys ‘n gals hardly ever look at them close up.
All images contain areas of high and low frequency detail, and these areas require different process treatments, if you want to obtain the very best results AND want to preserve the ability to print.
Cleanly defined edges between these areas allow us to use layer masks to separate these areas in an image, and obtain the selective control.
Clean inter-tonal boundaries also allow us to separate shadows, various mid tone ranges, and highlights for yet more finite control.
Working on 16 bit images (well, 15 bit plus 1 level if truth be told) means we can control our adjustments in Photoshop within a range of 32,768 tones. And there is no way in hell that localised adjustments in Lightroom can be carried out to that degree of accuracy – fact.
I’ll let you in to a secret here! You all watch the wrong stuff on YouTube! You sit and watch a video by God knows what idiot, and then wonder why what you’ve just seen them do does NOT work for you.
That’s because you’ve not noticed one small detail – 95% of the time they are working on jpegs! And jpegs only have a tonal range of 256. It’s really easy to make luminosity selections etc on such a small tonal range work flawlessly. You try the same settings on a 16 bit image and they don’t work.
So you end up thinking it’s your fault – your image isn’t as ‘perfect’ as theirs – wrong!
It’s a tale I hear hundreds of times every year when I have folk on workshops and 1to1 tuition days. And without fail, they all wish they’d paid for the training instead of trying to follow the free stuff.
You NEVER see me on a video working with anything but raw files and full resolution 16 bit images.
My only problem is that I don’t ‘fit into’ today’s modern ‘cult of personality’!
Most adjustments in Lightroom have a global effect. Yes, we have range masks and eraser brushes. But they are very poor relations of the pixel-precise control you can have in Photoshop.
Lightroom is – in my opinion of course – becoming polluted by the ‘one stop shop, instant gratification ideology’ that seems to pervade photography today.
Someone said to me the other day that I had not done a YouTube video on the new range masking option in Lightroom. And they are quite correct.
Why?
Because it’s a gimmick – and real crappy one at that, when compared to what you can do in Photoshop.
Photoshop is the KING of image manipulation and processing. And that is a hard core, irrefutable fact. It has NO equal.
But Photoshop is a raster image editor, which means it needs to be fed a diet of real pixels. Raw converters like Lightroom use ‘virtual pixels’ – in a manner of speaking.
And of course, Lightroom and the CameraRaw plug in for Photoshop amount to the same thing. So folk who use either Lightroom or Photoshop EXCLUSIVELY are both suffering from the same problems – if they can be bothered to look for them.
It Depends on the Shot
The landscape image is by virtue, a low ISO, high resolution shot with huge depth of field, and bags of high frequency inter-tonal detail that needs sharpening correctly to its very maximum. We don’t want to sharpen the sky, as it’s sharp enough through depth of field, as is the water, and we require ZERO sharpening artifacts, and no noise amplification.
If we utilise the same sharpening workflow on the center image, then we’ll all get our heads kicked in! No woman likes to see their skin texture sharpened – in point of fact we have to make it even more unsharp, smooth and diffuse in order to avoid a trip to our local A&E department.
The cheeky Red Squirrel requires a different approach again. For starters, it’s been taken on a conventional ‘wildlife camera’ – a Nikon D4. This camera sensor has a much lower resolution than either of the camera sensors used for the previous two shots.
It is also shot from a greater distance than the foreground subjects in either of the preceding images. And most importantly, it’s at a far higher ISO value, so it has more noise in it.
All three images require SELECTIVE sharpening. But most photographers think that global sharpening is a good idea, or at least something they can ‘get away with’.
If you are a photographer who wants to do nothing else but post to Facebook and Flickr then you might as well stop reading this post. Good luck to you and enjoy your photography, but everything you read in this post, or anywhere on this blog, is not for you.
But if you want to maximize the potential of your thousands of pounds worth of camera gear, and print or sell your images, then I hate to tell you, but you are going to have to LEARN STUFF.
Photoshop is where the magic happens.
As I said earlier, Photoshop is a raster image processor. As such, it needs to be fed an original image that is of THE UTMOST QUALITY. By this I mean a starting raw file that has been demosaiced and normalized to:
Contain ZERO demosaic artifacts of any kind.
Have the correct white and black points – in other words ZERO blown highlights or blocked shadows. In other words, getting contrast under control.
Maximize the midtones to tease out the highest amount of those inter-tonal details, because this is where your sharpening is going to take place.
Contain no more sharpening than you can get away with, and certainly NOT the amount of sharpening you require in the finished image.
With points 1 thru 3 the benefits should be fairly obvious to you, but if you think about it for a second, the image described is rather ‘flattish – looking’.
But point 4 is somewhat ambiguous. What Adobe-philes like to call capture or input sharpening is very dependent on three variables:
Sensor megapixels
Demosaic effeciency
Sharpening method – namely Unsharp Mask or Deconvolution
The three are inextricably intertwined – so basically it’s a balancing act.
To learn this requires practice!
And to that end I’m embarking on the production of a set of videos that will help you get to grips with the variety of sharpening techniques that I use, and why I use them.
I’ll give you fair warning now – when finished it will be neither CHEAP nor SHORT, but it will be very instructive!
I want to get it to you as soon as possible, but you wouldn’t believe how long tuition videos take to produce. So right now I’m going to say it should be ready at the end of February or early March.
UPDATE: The new course is ready and on sale now, over on my digital download site.
A few days ago I uploaded a video to my YouTube channel explaining PPI and DPI – you can see that HERE .
But there is way more to pixel per inch (PPI) resolution values than just the general coverage I gave it in that video.
And this post is about a major impact of PPI resolution that seems to have evaded the understanding and comprehension of perhaps 95% of Photoshop users – and Lightroom users too for that matter.
I am talking about image view magnification, and the connection this has to your monitor.
Let’s make a new document in Photoshop:
We’ll make the new document 5 inches by 4 inches, 300ppi:
I want you to do this yourself, then get a plastic ruler – not a steel tape like I’ve used…..
Make sure you are viewing the new image at 100% magnification, and that you can see your Photoshop rulers along the top and down the left side of the workspace – and right click on one of the rulers and make sure the units are INCHES.
Take your plastic ruler and place it along the upper edge of your lower monitor bezel – not quite like I’ve done in the crappy GoPro still below:
Yes, my 5″ long image is in reality 13.5 inches long on the display!
The minute you do this, you may well get very confused!
Now then, the length of your 5×4 image, in “plastic ruler inches” will vary depending on the size and pixel pitch of your monitor.
Doing this on a 13″ MacBook Pro Retina the 5″ edge is actually 6.875″ giving us a magnification factor of 1.375:1
On a 24″ 1920×1200 HP monitor the 5″ edge is pretty much 16″ long giving us a magnification factor of 3.2:1
And on a 27″ Eizo ColorEdge the 5″ side is 13.75″ or there abouts, giving a magnification factor of 2.75:1
The 24″ HP monitor has a long edge of not quite 20.5 inches containing 1920 pixels, giving it a pixel pitch of around 94ppi.
The 27″ Eizo has a long edge of 23.49 inches containing 2560 pixels, giving it a pixel pitch of 109ppi – this is why its magnification factor is less then the 24″ HP.
And the 13″ MacBook Pro Retina has a pixel pitch of 227ppi – hence the magnification factor is so low.
So WTF Gives with 1:1 or 100% View Magnification Andy?
Well, it’s simple.
The greatest majority of Ps users ‘think’ that a view magnification of 100% or 1:1 gives them a view of the image at full physical size, and some think it’s a full ppi resolution view, and they are looking at the image at 300ppi.
WRONG – on BOTH counts !!
A 100% or 1:1 view magnification gives you a view of your image using ONE MONITOR or display PIXEL to RENDER ONE IMAGE PIXEL In other words the image to display pixel ratio is now 1:1
So at a 100% or 1:1 view magnification you are viewing your image at exactly the same resolution as your monitor/display – which for the majority of desk top users means sub-100ppi.
Why do I say that? Because the majority of desk top machine users run a 24″, sub 100ppi monitor – Hell, this time last year even I did!
When I view a 300ppi image at 100% view magnification on my 27″ Eizo, I’m looking at it in a lowly resolution of 109ppi. With regard to its properties such as sharpness and inter-tonal detail, in essence, it looks only 1/3rd as good as it is in reality.
Hands up those who think this is a BAD THING.
Did you put your hand up? If you did, then see me after school….
It’s a good thing, because if I can process it to look good at 109ppi, then it will look even better at 300ppi.
This also means that if I deliberately sharpen certain areas (not the whole image!) of high frequency detail until they are visually right on the ragged edge of being over-sharp, then the minuscule halos I might have generated will actually be 3 times less obvious in reality.
Then when I print the image at 1440, 2880 or even 5760 DOTS per inch (that’s Epson stuff), that print is going to look so sharp it’ll make your eyeballs fall to bits.
And that dpi print resolution, coupled with sensible noise control at monitor ppi and 100% view magnification, is why noise doesn’t print to anywhere near the degree folk imagine it will.
This brings me to a point where I’d like to draw your attention to my latest YouTube video:
Did you like that – cheeky little trick isn’t it!
Anyway, back to the topic at hand.
If I process on a Retina display at over 200ppi resolution, I have a two-fold problem:
1. I don’t have as big a margin or ‘fudge factor’ to play with when it comes to things like sharpening.
2. Images actually look sharper than they are in reality – my 13″ MacBook Pro is horrible to process on, because of its excessive ppi and its small dimensions.
Seriously, if you are a stills photographer with a hankering for the latest 4 or 5k monitor, then grow up and learn to understand things for goodness sake!
Ultra-high resolution monitors are valid tools for video editors and, to a degree, stills photographers using large capacity medium format cameras. But for us mere mortals on 35mm format cameras, they can actually ‘get in the way’ when it comes to image evaluation and processing.
Working on a monitor will a ppi resolution between the mid 90’s and low 100’s at 100% view magnification, will always give you the most flexible and easy processing workflow.
Just remember, Photoshop linear physical dimensions always ‘appear’ to be larger than ‘real inches’ !
And remember, at 100% view magnification, 1 IMAGE pixel is displayed by 1 SCREEN pixel. At 50% view magnification 1 SCREEN pixel is actually displaying the dithered average of 2 IMAGE pixels. At 25% magnification each monitor pixel is displaying the average of 4 image pixels.
Anyway, that’s about it from me until the New Year folks, though I am the worlds biggest Grinch, so I might well do another video or two on YouTube over the ‘festive period’ so don’t forget to subscribe over there.
Thanks for reading, thanks for watching my videos, and Have a Good One!
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.
My YouTube Channel Latest Photography Video Training.
I’ve been busy this week adding more content to the old YouTube channel.
Adding content is really time-consuming, with recording times taking around twice the length of the final video.
Then there’s the editing, which usually takes around the same time, or a bit longer. Then encoding and compression and uploading takes around the same again.
So yes, a 25 minute video takes A LOT more than 25 minutes to make and make live for the world to view.
This weeks video training uploads are:
This video deals with the badly overlooked topic of raw file demosaicing.
Next up is:
This video is a refreshed version of getting contrast under control in Lightroom – particularly Lightroom Classic CC.
Then we have:
This video is something of a follow-up to the previous one, where I explain the essential differences between contrast and clarity.
And finally, one from yesterday – which is me, restraining myself from embarking on a full blown ‘rant’, all about the differences between DPI (dots per inch) and PPI (pixels per inch):
Important Note
Viewing these videos is essential for the betterment of your understanding – yes it is! And all I ask for in terms of repayment from yourselves is that you:
Give the video a ‘like’ by clicking the thumbs up!
YouTube is a funny old thing, but a substantial subscriber base and like videos will bring me closer to laying my hands on latest gear for me to review for you!
If all my blog subscribers would subscribe to my YouTube channel then my subs would more than treble – so go on, what are you waiting for.
I do like creating YouTube free content, but I do have to put food on the table, so I have to do ‘money making stuff’ as well, so I can’t afford to become a full-time YouTuber yet! But wow, would I like to be in that position.
So that’s that – appeal over.
Watch the videos, and if you have any particular topic you would like me to do a video on, then please just let me know. Either email me, or you can post in the comments below – no comment goes live here unless I approve it, so if you have a request but don’t want anyone else to see it, then just say.
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.
Okay, so I’ve been ‘banging on’ about the problem that quite a few people have been suffering from with the new Lightroom Classic CC and GPU acceleration since Adobe launched the new application.
I must stress that this problem does NOT seem to effect anyone using MBP or iMac, or indeed any Mac Pro that runs a factory-fitted GPU. But if you can remember, I fitted my Mac Pro with an nVidia GTX 970 4Gb GPU a while back – mainly to help Photoshop CC with the heavy lifting in ‘Refine Edge’ and other masking/channel masking procedures.
But I’m now pleased to report that the problem is FIXED – and, as I suspected, the fix is simple, and the ‘fix’ is a tiny 28 byte file. Yes, that’s right, 28 BYTES!
It’s an API Thing
Now I’m totally rubbish with computer jargon, but API is the acronym for Application Programming Interface, and with regard to GPU/Graphics Cards there a 4 main APIs:
OpenGL
Direct Ex – in other words Microsoft
Metal – in other words Apple
Vulcan – don’t ask/no idea
For some reason, on certain Mac systems, Lightroom Classic CC is not finding OpenGL, and is instead being forced into trying to use the OSX API ‘metal’.
The forums have been rife with Lightroom Classic CC problems for the last few days – this one included. On one of these forums, Adobes Simon Chen, had been attempting to field questions over this problem.
I asked Simon if there was any way to ‘force’ Lightroom Classic CC to ignore the OSX API and default to OpenGL – which was obviously there on the system, because the previous iteration of Lightroom had been using it quite happily.
Simon suggested the installation of this tiny 28 byte ‘config.lua’ file into Lightrooms’ Application Support root folder – and would you believe it, it works!
Below is a short video I’ve made this morning on how to download and install this tiny file which will re-instate Lightroom Classic CCs ability to use the OpenGL API.
So now I’m a happy bunny; and if you have the problem then just follow the video instructions and you’ll be a happy bunny too!
Big thanks to Simon Chen, Principle Scientist at Adobe for helping sort this irritating niggle out.
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.
Adobe Lightroom Classic and Photoshop CC 2018 tips – part 1
So, you’ve either upgraded to Lightroom Classic CC and Photoshop CC 2018, or you are thinking doing so.
Well, here are a couple of things I’ve found – I’ve called this part1, because I’m sure there will be other problems/irritations!
Lightroom Classic CC GPU Acceleration problem
If you are having problems with shadow areas appearing too dark and somewhat ‘chocked’ in the develop module – but things look fine in the Library module – then just follow the simple steps in the video above and TURN OFF GPU Acceleration in the Lightroom preferences panel under the performance tab.
Turn OFF GPU Acceleration
UPDATE: I have subsequently done another video on this topic that illustrates the fact that the problem did not exist in Lr CC 2015 v.12/Camera Raw v.9.12
In the new Photoshop CC 2018 there is an irritation/annoyance with the brush tool, and something called the ‘brush leash’.
Now why on earth you need your brush on a leash God ONLY KNOWS!
But the brush leash manifests itself as a purple/magenta line that follows your brush tool everywhere.
You have a smoothness slider for your brush – it’s default setting is 10%. If we increase that value then the leash line gets even longer, and even more bloody irritating.
And why we would need an indicator (which is what the leash is) of smoothness amount and direction for our brush strokes is a bit beyond me – because we can see it anyway.
So, if you want to change the leash length, use the smoothing slider.
If you want to change the leash colour just go to Photoshop>Preferences>Cursors
Here, you can change the colour, or better still, get rid of it completely by unticking the “show brush leash while smoothing” option.
So there are a couple of tips from my first 24 hours with the latest 2018 ransom ware versions from Adobe!
But I’m sure there will be more, so stay tuned, and consider heading over to my YouTube channel and hitting the subscribe button, and hit the ‘notifications bell’ while you’re at 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.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.