Tag Archives: Lightroom

My Copy of Lightroom Got Sick

After a previous update to Lightroom (6.12), it became almost unusable. Importing would take forever and, once the images were in, it would grind to a halt. Keywording and editing became a nightmare. I was struggling to work out what was wrong. A check on performance showed the processor wasn’t busy but the RAM was maxed out. I couldn’t understand why. The first thing I do when Lightroom behaves strangely is to delete the Preferences file. This file can get corrupted and mess with the performance badly. Just delete it and restart and things are often fixed. That didn’t work in this case. When the new version of Lightroom was released, I hoped this would fix everything but sadly not. (Meanwhile Photoshop itself is working just fine on this system.)

I had a long session with the Adobe tech support people which got me nowhere. After telling me this was normal, they realized it was not when our screen sharing crapped out as a result of the machine slowing to a virtual standstill. They tried a bunch of simple stuff and got no further than I had on my own. They suggested a second session would be needed and then promptly sent me an email telling me that the issue had been successfully resolved. Not sure how they concluded that. Meanwhile, I wondered whether there was an issue with my Windows installation so decided to do a completely clean install. This had some slight benefits but basically the problem still remained.

I have done a bunch of scanning of similar issues and I found out a technique the support team can use to tweak performance. There is a config.lua file that can be created in the presets folder to influence the system. I have added this file and it has certainly made a few things work better. It has also slowed some things down as well which isn’t ideal. This was not a solution though. All it did was make the program slightly more usable.

Another session with Adobe ensued. This time we got into the permissions for some of the folders that contained the catalogs. Lots of time to reset these to give greater authority. I was told this is sometimes an issue with large catalog files. Lots of time later, I found that nothing had really changed. The whole thing would still get bogged down very quickly.

Then I read about Lightroom 7.2. This was a new update that was supposed to address a lot of performance issues. It was supposed to make better use of multi-core processors as well as larger RAM configs. I had seen a sequence of updates not improve things – my issues were clearly not the normal performance problems although I had previously experienced some of them too – but I was hoping that, if they had changed the architecture of the software, maybe whatever was causing my machine to have problems might have been tweaked/replaced. If not, I was seriously considering the need to buy a new system since this was so horribly inefficient.

I waited for the release date to come around when I knew the update was on its way. Then I got an update to the iPad version and it said the new version of Camera Raw was included. This must mean it was close. A day later, the update dropped. I downloaded it immediately and opened up. Hurrah!!! Everything run fast, the RAM levels were moderate and stable, everything was happening as it should. My system lives! Let’s hope this isn’t a false dawn.

My Approach to Shooting and Processing on Crappy Weather Days

Leave a reply

This is the finished image. This is pretty much what it looked like to the naked eye (through the viewfinder) when I took the shot given how dark the sky was.

A rare arrival was due on a day that was not good from a weather perspective. It was dull and rainy and so not what you would hope for. Conditions like this mean I try to exploit some of the features of the camera and the processing options available. First, how to set up the camera? With the light being bad and variable, I went to a pretty high ISO level. I shot in aperture priority mode and added a lot of exposure compensation.

In my experience, the metering is pretty good when shooting against the sky in clear weather but, when there is a lot of cloud, the camera tends to treat the clouds as too bright and it underexposes the subject too much. I use a lot of exposure compensation in this case with a setting of +2.0 being used on this day. The reason I do this is that, aside from the exposure question mark, there is a lot more information available in the lighter end of the exposure curve. Shooting in RAW gives you options.

This is how the camera recorded the image. This is the in camera JPEG that I extracted from the RAW file using Instant Raw From JPEG.

If you were to look at the aircraft at the time, you would see a dark and menacing sky but you would see plenty of detail on the plane. The camera does not see that for the original shot. The aircraft would be very dark. When processing, this dark area would give you something to work with but the variation in data would be more limited. Shoot overexposed and you get more to work with.

This approach will only work well if you are shooting RAW. If you are using JPEG, too much of the usable data will be discarded during the processing in the camera. To show you what I mean, here are two images. These are both from the same shot. One is the RAW file as it showed up when imported in to Lightroom and the other is the embedded JPEG that you can extract from the RAW file and which can be seen when the file is first imported before the rendering is undertaken. As you can see, the JPEG is over exposed but the RAW rendering seems even more so.

There is way more data in the RAW file though. Immediately, as I bring the exposure slider back down, the clouds go from being white to quite dark – just as they appeared on the day. Meanwhile, the fuselage of the aircraft has a lot of the data intact and maintains a lot of the brightness that you could see at the time. Very little needs to be done with the blacks and they are almost in the right spot by the time the exposure is good for the clouds. The fuselage might be a bit too dark though. A small tweak of the blacks and a little boost in the shadows to compensate for too much darkening with the exposure slider and suddenly the shot is looking a lot more like it did when I saw it develop.

My RAW processing baseline always results in a slightly more overexposed shot the embedded JPEG includes. When you first open the image, the embedded image you see in the previous shot initially shows up and then it renders the RAW file. This was the initial RAW rendering prior to any adjustments.

One advantage of shooting on such a crummy day is that the sky is a giant softbox – in this case a very soft one! The result is that the light is a lot more even than on a sunny day. The darker look can actually make the colors look a bit more intense than if they were losing out to the whites when the sun is right on them. While there was only one plane I was specifically there for, playing around with these other shots and working on the technique was a nice extra benefit.

Stitching a Moving Ship

Leave a reply

This is less of a technique post and more about the capabilities of modern software. In a previous post I discussed a visit to Vancouver to meet up with family members that had come off a cruise ship. We were down on the waterfront when the ship that they had come in on departed. As it got further away, I shot a few frames with the longer lens to try and stitch together in a panorama. The problem with this type of shot is that the ship is moving so the background is not consistent between the frames, even if you try and do them quickly. However, I handed them over the Lightroom and it did its stitching thing and the attached shot resulted. I think you would struggle to know that there was an issue based on the output. Quite impressive software performance!

Adobe Fixed the Time Zone Issue for Video

Leave a reply

In this previous post, I noted that there was a problem with the way in which Lightroom identified the time of video files. I was having to manually adjust the capture time after importing them. When I contacted Adobe, they said it was a problem with Canon and vice versa. Not helpful. However, I notice that, with a recent update (I won’t say upgrade because some aspects of it seem to have really screwed up Lightroom performance), the video files now come in with the correct time associated. I only found this out because I was about to adjust them when I realized they were already correct. One little annoyance has now gone away. Hurrah!

Another Go at Stitching iPhone Raw Shots

Leave a reply

As I posted a while ago, I have been experimenting with stitching shots from my phone. Since I am shooting in raw on the phone, I have some latitude to play with the shots in post that wasn’t there before. This time, though, I thought about it a bit more and put the camera into manual mode to fix the exposure. This should make the stitching and blending easier than when it changed between shots (although, to give the Lightroom team credit, it did a pretty good job anyway). I allowed plenty of overlap and the merge seemed to go pretty well. Since it outputs a dng file, you still have the chance to edit more aggressively than would be possible with a jpeg. Meanwhile, you get a higher resolution shot than with the internal pano mode. This may be my go to method from now on.

Sacramento Roundhouse

Leave a reply

One end of the railroad museum in Sacramento is a roundhouse. It is accessible still from the line outside and I was there for a modern locomotive that was being unveiled. Access comes via a turntable which sits right next to the path along the river. I figured I would put together a panorama of the scene. However, I only had my phone (albeit able to shoot raw). I had never tried shooting a pano sequence with it before having only used its internal pano function.

I wasn’t controlling the exposure (although there is a manual function in the app I use) but I had noticed that the Lightroom pano function seemed quite adept at dealing with small exposure variation. I took the sequence and there was not a big difference across them. When I got home, I added them to Lightroom and had a go at the stitching function. It worked better than I had expected. Some small distortions were there but it actually was rather good. I had not been happy about the reduced size of the pano function of the phone so this has provided a better option to use in the future.

My Revised Workflow

Leave a reply

My approach to processing images after a shoot is something that constantly evolves. I have written about how I do this in the past but a few things have changed since I wrote that so I thought I would write up the latest approach in case it is of any use/interest to any other shooters out there. I should say at the start that my workflow is based around the use of Lightroom. If you don’t use Lightroom, this might not be of any use to you although I imagine that a similar process could be achieved with other software.

One thing to highlight at the start is that, when shooting aviation (and that is the majority of my photography), I aim to slightly overexpose my shots. I have found that going a slight bit over and then bringing the exposure back down in post-production gives a better balance of exposure across the shots and also makes for more pleasing sky colors. This is something I do when shooting RAW. If you shoot in JPEG, this might still work but your latitude for adjustment afterwards is a bit reduced so you might not get the same effect. I don’t shoot in JPEG so I can’t state what happens.

All the shots are imported in to Lightroom and I will form a Collection Set for the shoot. I don’t have specific folders for shoots, nor do I have a renaming convention. I keyword all shoots and this is how I manage files and find things later. Keywording is a story for another day. Within the Collection Set, I shall create a series of Smart Collections. They vary depending on what I have shot. There will always be Not Rejects, Rejects and Picks. Then, depending on what else there is, there might be Videos, Time Lapse, Blend Stack, Pano Originals, Pano Edits, HDR Originals and HDR Edits. I keyword any of these types of shot with that term so the smart collections will pick them up. The Smart Collections may be looking for a date range or shoot specific keywords depending on what I have been shooting.

The aim for all of this is that I get a Smart Collection which is unrejected shots which doesn’t include and shots from HDRs, panos, time lapses or blend stacks. I don’t want to get rid of those shots by mistake and I want to be able to edit those shots at a convenient time. Then the Not Rejects folder becomes my focus. I am aiming to get all of them roughly corrected for exposure so I can make decisions about which shots to keep. I will be looking for sharpness/focus issues and exposure variation can really mess with how you perceive sharpness. I will open a shot up in the Develop module and I will have the Grid view on the second monitor. I can now select shots with the same exposure and choose Auto Sync. Then a change to one shot will be reflected in all of them.

It used to be that I would select the shots by eye. Then it occurred to me that the Metadata filter is powerful here. I select the filter of shutter speed and then I can select each shutter speed in turn. Now it is easy to select the similar shots and edit together. This really speeds up the quick edit process. I know tweak whatever needs tweaking and get everything basically okay. I won’t bother with detailed editing unless a shot is going to be used for something further. Now I select all files and, in the Library module, select Render 1-1 Views. Then I head off to do something else for a while.

When the rendering is done (I don’t try and do anything else while it is underway because, while you can do other Lightroom tasks, everything gets pretty sluggish. It is easier to wait. I may even shut Lightroom down and restart it after the rendering is done because it seems to like the chance to clean itself up. Then I go to the first of the Not Rejects shots. I have it full screen on the main screen and then zoom to 100% on the second screen. The Smart Collection is set up to show any file that is not marked as a reject (or all of the other stuff I mentioned earlier) so now I can click through the shots. If a shot is good, I Right Arrow to the next one. If it is bad, hit X and it disappears. Now I can run through the whole shoot and quickly get rid of all shots that are not good, be they unsharp, chopping off a bit of something or just clearly useless.

When this first pass is done, I am now left with a bunch of shots, many of which are very similar. Since I know they all are basically acceptable, I can now select all the ones that I won’t have a need for and hit X. Very quickly I am down to a far more manageable number of shots. Then I can pick which ones I want to do something with. Hit P for those and they will automatically appear in the Picks Smart Collection and I can come back to them at any time. If I have shots that will be used for a specific piece, I may create a Collection specifically for that publication and just drag the shots in so I can deal with them at any time.

That pretty much sums up how I handle a shoot. Some will have pano shots, some will have HDR, occasionally there will be time lapses and often videos. Sadly, the integration of video between Lightroom and Photoshop is non-existent so I have yet to have a good process for video editing. Maybe one day Adobe will fix that. They tempted us by having video in Lightroom but they never took it any further despite the fact that the opening in layers option for stills would be ideal for video editing. One day…

Enfuse for HDR

Leave a reply

I am a little late to discovering the Enfuse plugin for working with HDR images. I started out many years ago using Photomatix. At the time, it was the go to software for creating HDR images. Then Adobe got a lot better with their HDR software within Photoshop and I started to use that. Even more recently, Adobe built HDR processing in to Lightroom and I didn’t need to go to Photoshop at all. The HDR software worked reasonably well so I stuck with it. I sometimes felt that it didn’t do as good a job of using the full range of the exposures but it was okay.

I wasn’t entirely satisfied though so have kept an eye on other options. Someone mentioned Enfuse to me so I decided to give it a go. It is a plugin for Lightroom and, in the free download, you can try it out but with a limitation on the output image size of 500 pixels. Obviously this isn’t useful for anything other than testing but that is the point.

The first thing I tried it on was a shot I made at Half Moon Bay looking up at a P-51 Mustang prop and directly into the sun. This is certainly as much of a range of exposures as you are likely to get. The perfect thing for an HDR trial. The results in the small scale file seemed pretty impressive so I decided to buy the package. There is no fixed price. You make a donation via PayPal and get a registration code. I am impressed by the quality of some of the work people put out so I am happy to donate for what they do. With the software activated, I reran the P-51 shots. Below is the version I got from Lightroom’s own HDR and following it the version from Enfuse.

I did have some issues initially. Lightroom was not reimporting the image after it was created. This turned out to be an issue with the way I named the file in the dialog and a tweak to that seemed to fix things. Strangely, it had been fine on the trial so I have no idea why it became an issue but it is done. I also played with a slightly less extreme case with an F-22 and, as above, the Lightroom version is first and the Enfuse version is second. I was really pleased with the result on this one with a very natural look to things. So far, I see Enfuse being a useful tool for my HDR going forward.

How Low Can You Go?

Leave a reply

The high ISO capabilities of modern cameras are a constant source of discussion whenever a new camera comes out. It was quite funny to see everyone get so excited about the multi-million ISO range on the Nikon D5 when it was announced, only to see that the high ranges were nothing more than moose with a bit of an image overlaid on them. Not a big surprise but still funny to see how much everyone was going nuts about it before the reality set in.

Consequently, I was interested to see what the new bodies I bought were really capable of. I have already posted a little about some of the shots I took as the light faded at SFO. I was shooting with a tripod and a gimbal mount to make things easier but I was also working within the ISO range of the camera. I went with auto ISO and exposure compensation while shooting in aperture priory and wide open to get what I could. However, I really wanted to see what was possible so I changed to manual mode, exposure compensation and auto ISO to see what could be done. Auto ISO is not going to use the extended ranges of ISO.

I don’t know about the Nikon cameras but the Canon cameras tend to have three extended range ISO settings at the high end. There is the highest ISO setting that it recognizes and then there are H1, H2 and H3. They don’t name them with the actual ISO settings but you know what they are based on what you see on the camera. The manufacturer does not label them as normal ISO settings because they do not stand behind them as a capability. There is a good reason for that. They are just like the highest Nikon settings. Useful if you have no option but not very good otherwise.

The same was true with my older bodies. They had a very high ISO range that was not great but it would do in a pinch. At the Albuquerque Balloon Fiesta I shot an Aero Commander in the pitch black that flew over and I saw stuff in the shot I couldn’t see with the naked eye. This is with a camera that is ancient by modern standards. I expected a bit more with the latest generation. Certainly, there is more to be achieved with what we have now. However, post processing becomes a part of the story.

My first experience with these shots was in Lightroom. The shots did not look good at all. However, there was a clue in all of this. The first view in Lightroom is based on the JPEG that is baked into the raw file. It looked okay until it was rendering by Adobe at which point it looked a lot worse. This piqued my interest. Sure enough, at the extended ISO ranges, the shots looked pretty awful. Lots of purple backgrounds. These were not going to be any good. However, the initial preview had looked good., is this a case of Lightroom not being able to render the shots well? I figured I should try going to the source.

At various ISAP symposiums, the Canon guys have talked about how their software is the one that you should use since only Canon know how to decode their shots properly. They have the recipe for the secret sauce. Since Digital Photo Professional (DPP), Canon’s own software for decoding raw files, is so terrible to use, I never bother with it. The raw processing in Lightroom (and ACR since they are the same) is so much easier to use normally and works really well. DPP is just awful in comparison. However, we are now dealing with the extremes of capabilities of the camera. The embedded previews seemed better so maybe it is possible that DPP will be able to do a better job.

You can now be the judge. Here are some pairs of shots. They are the same shot in each case. The first is processed in Adobe Lightroom and the second is processed in DPP. I think it is clear that DPP is better able to work with the raw files when it comes to extreme ISO settings. The shots certainly have a more normal look to them. The Lightroom shots look really messed up by comparison. It doesn’t mean I will be using the extended ISO ranges on a regular basis. Jumping to DPP for processing is not helpful on a regular basis. However, if the need arises, I know that I can push the camera a lot further and use DPP to get something that is okay if not great. This could be handy at some point.

Lightroom, Video and Capture Times

Leave a reply

Getting the new camera has resulted in discovering a new quirk in the way that files are handled. I have been capturing video on the camera and, when it is imported to Lightroom, the video is showing a different capture time to the stills around it. The offset is eight hours which is the difference between the US West Coast and UTC. I was wondering whether this was an issue with Lightroom so checked in with some forums on that topic. I got feedback about the way that files record capture time for files and the suggestion that it was down to the way Canon write the capture time in a format different from that in the standards.

I then starting communicating with Canon and they said there was nothing wrong with their format and that the software I was using, i.e. Lightroom, was the one at fault. It seems everyone considers this someone else’s fault. Not much help to me of course. In the meantime, I have to remember to go to the edit capture time function in Lightroom when I import the files if there is any video included. I usually remember but not always. If anyone has a good suggestion, please let me know.