Tag Archives: Lightroom

HDR 32 Bit and Lightroom

This post is a plea for help. Anyone who is a regular user of Lightroom and Photoshop may be in a position to educate me a little. I use Photoshop to process my HDR shots. I start out in Lightroom, select the shots and use the Edit Photo>HDR Pro method to open them up in Photoshop. I then use the 32 bit version of the HDR Pro processor to create the file. I then take the Edit Using Adobe Camera Raw option for opening the file to undertake the final mapping. This works pretty well and I can usually get something I am happy with.

I then close the file and save it which automatically reimports the finished file back into Lightroom. This is when things go wrong. The view of the file in Lightroom doesn’t appear to make use of any of the edits I had done in ACR. The highlights are too bright and the shadows too dark. I can then use the Lightroom Develop settings to get something close to what I want but surely that should not be necessary. I might make further tweaks but shouldn’t it look the same when I close out of Photoshop.

Below is a sequence of screen captures to show you the unprocessed shot in ACR, the finished version, what it looks like in Lightroom and then what I can tweak it to. Any suggestions are gratefully received. (Note, I didn’t make this exactly match the two edited versions. It is aimed to illustrate the disconnect and the recovery process.)

Original HDR merge pre tone mapping

HDR with ACR tone mapping applied

How the saved image appears when imported to Lightroom

Using Lightroom to get back to something like I had in Photoshop

Funky Cloud Processing

Leave a Reply

Part of a run back into Oakland recently came across the bay but it was unfortunately covered in cloud. However, the cloud was sitting in very distinct locations with a clear edge as you headed down the bay and a similar edge near the shoreline on the Oakland side. Since we were not high above it, this looked pretty interesting. Even as I photographed it, I figured the shots would need something a bit different when I got around to processing them. Having a more contrasty look seemed the best bet and a black and white conversion also seemed likely. That is what I went with and I was quite pleased with how it turned out. See what you think.

HDR Panoramas

Leave a Reply

Another one of my processing technique posts today. For those of you interested in pictures of places, today will probably be one you pass on. You have been warned. This is about my first venture into the realm of HDR panoramas. I know at least one of you who knows exactly how to do this sort of thing and does it on a regular basis. You also will probably skip the rest of the post. However, you have some specialized tools for doing the job and I am playing with Lightroom and Photoshop so here is how it goes.

My initial thought having taken the shots was which order to carry out the processing. HDR first or pano first. I concluded that it had to be pano first. All of the pano exposures were consistent and would stitch properly while I wasn’t convinced that each of the pano frames would be consistent if I had done the HDR blending first. However, this left me with a second concern. Would the pano merge produce images that would align for the HDR merge. I use the pano tools built into Photoshop and, while I select the algorithm it uses, I did not have confidence that it would produce an identical alignment for each set of exposures. However, this was the route I tried.

Stitching the panos was straightforward enough. I created each of them from Lightroom and ended up with five panos with differing exposures. At this point I could have taken them directly to HDR Pro within Photoshop but, since I wanted everything to end up in the Lightroom catalog, I decided to save the files and go to HDR Pro from there.

Here I encountered my first hiccup. As expected, the panos produced were not identical. There were very close but not identical. HDR Pro only works on files that are the same dimensions. I imagine some more specialized HDR applications might be able to handle this but I was stuck with Photoshop. Since the panos were thousands of pixels across and only a few pixels different, I opened them back up in Photoshop and changed the canvas size to be identical in each case. HDR Pro is able to manage alignment of slightly misaligned shots anyway so I wanted worried about the positioning. Also, with such small changes in dimensions, I didn’t fear that I would have distortion.

With this change made, Photoshop went to work and created the HDR file. Amazingly, it worked just fine. I didn’t have any problems with the files being distorted relative to each other and it did a great job of blending them. All that was left was to crop everything in to clear up the empty corners from the pano creation (I didn’t get rid of those in the first instance since I was trying to keep the pano files identical in size and alignment) and then a few tweaks back in Lightroom had the job finished. I was pretty pleased with how it worked and, with the experience of this time, should be able to turn them around quite quickly next time.

Updated Approach to Lightroom Catalogs

Leave a Reply

I have been a user of Lightroom since Adobe release version 1 quite a few years ago. It has been a very useful tool for me and something that dominates my workflow. In the early days, there were issues with the number of images that a catalog could have before it started to respond sluggishly. Consequently, I created a series of different catalogs for different subject areas. Military aircraft were in one, civil in another, wildlife in a third, sports in a fourth and so on. This system was fine to use although it had a few minor drawbacks in that some images would be in more the one catalog. I would import them to one and then export them to the other. However, as I edited one version, the other one did not always keep up despite saving the sidecar files to disc.

At some point, Adobe updated the functionality of the application and it was no longer so constrained by the number of files in a catalog. However, I had a series of catalogs that I was familiar with so I didn’t pay much attention to this change. However, over time, it occurred to me that I was making my life more complex than it needed to be. I could probably cut down the number of catalogs dramatically and make the workflow a bit simpler.

I decided to have one catalog for all of my aviation related imagery and the other for everything else. To do so, I created a new catalog for each of these and started importing from the other catalogs. This was not as smooth a process as you might have imagined. There were duplicate images as I knew and you could set the system up to make these virtual copies so nothing got lost along the way. However, sometimes the import did not go well. They were large catalogs coming into an even larger catalog and this caused some struggles. I had to delete and start again at some points but ultimately I got it to work. I did have to recreate some of the collections which did not transfer so easily in some cases but it is now done.

Did it make life easier? Yes, it did. Having just two catalogs is now a lot more straightforward. Do they run just as well? No. The aviation catalog does seem to be a bit sluggish sometimes. Usually it works fine but it is definitely not as responsive as the individual ones were. I shall see how this develops over time. A new machine is in the works so whether that will make a difference or not, we shall see.

LRTimelapse

Leave a Reply

I have previously written about some time-lapse software that I use based on a recommendation from my friend Jo Hunter. I used this software for a while before the creator, Gunther Wegner, updated it to a new version and deactivated the version I had. I was a bit miffed by this but I was able to continue using the export settings from his application within Lightroom but with me having to manually manage the file cropping. All transition and smoothing capability was lost but I could still make a basic time-lapse.

Sadly, the latest versions of Lightroom have done away with that as well and now I couldn’t even render the video. Therefore, I decided to take a look at the latest version of his software. It is now on version 3 so I have skipped a version en route to this place. I had shot a few sequences recently and wanted to be able to manage them properly so decided to come back and have another go with his application.

There have been some improvements in tidying up the software so the workflow is a bit better. There is still a certain amount of effort as you switch back and forth with Lightroom. You have to put all of the images into a single folder while working on them. This means a modification to my storage strategy but it isn’t difficult to manage in Lightroom and, when you are done, you can revert the images to their original locations and still render the video output. It might be nicer if he gave you a more flexible approach to selecting files but this is not a hardship.

It has changed a little from what I am used to since now it starts out analyzing the files before you have created keyframes. Once this is done, you save the xmp files out and reload them in Lightroom. Define your keyframes and make any edits to them that you want and save xmp again. Back to LRTimelpase to load the changes and now it does its smoothing very quickly. Save xmp again and back to Lightroom and now there is an Export setting along with all of the other export options. No going to the Slideshow module any more.

The results are pretty good. The new export functionality actually generates a sequence of still images which it stores. You then head back into LRTimelapse where you have a series of options for rendering a video sequence from those stills. You can have it automatically delete the stills when it is done or keep them and render again using different output options. This is pretty flexible although it means you have to pay attention to what you have used so you don’t end up with a ton of stored intermediate images. The video output looks good. I am not using the product commercially so do not have the full commercial license. That will allow output in 4K formats. I only wanted 1080p HD format for my purposes. It is a little interesting that 4K is automatically assumed to be commercial use. With people able to record 4K on GoPros these days and 4K TVs showing up, I suspect this is going to be a more mainstream format before too long. Maybe it will be in the personal use license of future versions of LRTimelapse. We shall see.

Was it worth the upgrade? Yes. Not least because I wanted to have the capability back that I had lost when Lightroom changed its output but, even so, I have found the new version to be quite a bit more friendly to work with. I think it will encourage me to work on a few more projects.

Night Shoot at SFO

Leave a Reply

One idea that Paul had was for us to have a go at shooting some light trails at SFO after it got dark. This sounded like a good plan. Unfortunately, we didn’t have any tripods or cable releases with us. No matter. Target was around the corner so we popped in there and bought a couple of $15 specials. Hmm, these were quality items indeed. Given how much a good tripod costs, can you imagine what a $15 tripod is like?

However, we made the best of it. Getting perfect alignment was tricky so some post processing cropping to level stuff up would be required. The camera wobbled a lot on the tripod when touched so I chose to trigger it with the shutter button on a 2 second delay. This allowed some wobbling to stop and, on a long exposure, any lingering wobble would be lost.

We got some stuff but it wasn’t brilliant. However, a short while later, I had to go to SFO to pick up some family members arriving on an evening flight so I decided to go a little earlier and try again, this time with some more appropriate kit in the form of a decent tripod and a cable release. This time, I was able to control things a bit better and get a few shots of interest. There wasn’t a huge amount of traffic so I didn’t get too many trails but I did get a slowly taxiing British Airways 747 which left an interesting smear across the frame.

The alignment with the moving planes is not fantastic from where I was but it was okay. Coyote Point looks like it might be better but I think it closes at sunset so I’m not sure whether that will be possible or not. We shall see.

Playing with Blending Layers

Leave a Reply

I have been making some shots with multiple exposures to overlay. This is something I have posted about before and the shots here are similar to those from before. However, this post is less about the shots and more about the post processing I used. Previously I opened up all of the shots as layers in a single file and then auto-aligned them. Once done, I then used the Auto Blend functionality to show each shot o the aircraft in place.

This was a lot quicker than my previous approach and was something I picked up from posts on photographing star trails. However, recently, I have not been as happy with the results as I should have been. Some of the planes, particularly those near to the edges, had some odd artifacts appearing. Also, if there were any overlaps, the blending masks could give some weird effects. Therefore, I have taken a different approach for a while. This is slower, I admit, but I think it gives a better result.

Once the alignment of the images is done, I hide them all except the bottom layer by Alt clicking on the eye beside the last layer. Then I add the next layer up back in but mask it out completely. A white brush on the mask then allows me to paint back in the new aircraft positions. This is a bit laborious but it does allow you to decide exactly what you want in and what you don’t. if one file is not helpful to the composition, you can easily ignore it.

If the layers are not all exactly aligned from shooting on a tripod, you will also get gaps at the edges on different layers. You can also fill these in by brushing in the layers that provide the right coverage and get a complete image. Once you are happy, flatten the whole thing and you are done.

Changing My Approach to Panoramas

Leave a Reply

Ever since Adobe got their act together with the Photomerge function in Photoshop, it has been my default for creating panoramas. Previous versions were a little unreliable but they cracked it a few versions back and I have not changed my approach since. However, a recent bit of YouTube exploring has changed that again. Russell Brown had a series of videos on making panoramas from aerial shots and, while I was watching them because they were aerials, the stuff he came up with on stitching panos was actually more useful to me.

Instead of using Photomerge, he uses the same functionality of Photoshop but in individual steps. The technique involves opening all of the shots as layers in a single file (something you can do straight from Lightroom which maintains the re-import linkage that I like about Photomerge). Then you select all layers and use Edit>Auto Align Layers. This gives you the same options as Photomerge. Apparently, according to Russell, if you have a series of shots where you have rotated position but are looking horizontally, Spherical works best. If you are looking up or down, use Circular.

The result can be quite distorted if you use Circular but it will all get better soon. If you aren’t happy, you can undo the step which is a lot easier than starting from scratch which is what you would have to do in Photomerge. Once the alignment is done, Edit>Auto Blend Layers while take care of the rest of the stitching and blend everything together nicely. It defaults to a Panorama blending option.

With the blend done, flatten the layers and open Filters>Adaptive Wide Angle. This will default to a panorama setting and, if you have the distorted output from the Circular settings, now you will suddenly see everything come back to what it should be. You can tweak this filter to get verticals and horizontals aligned as you wish and then you end up with a good pano output. Some cropping and filling of blank areas with Content-Aware fill and the job is done. I shall be taking this approach for all my panos from now on. If you don’t use this approach already, you might want to give it a try.

Also, you can go to the original source on this and check out Russell’s videos on YouTube.

RescuePro Deluxe

3 Replies

Today we have something of a product review combined with a workflow experiment. None of this was something that I wanted to do but circumstances dictated it was time. I had been out for the day shooting some wildlife including some sea otters – that will show up in a future post – and, one returning home and downloading my images, a few of the shots showed up strangely with no preview in Lightroom when I started to import them and were apparently corrupted on the card. Not sure what the cause of this was. The body had just come back from an annual service at Canon and the card was a new one. However, they both worked fine for the majority of the day with just some minor problems with a couple of dozen shots. I shall try and sort that out later.

So, to the problem at hand. I use Sandisk Extreme cards and have had virtually no problems to date. Therefore, I was in new territory. One thing that I do have as a result of using these cards is a bunch of coupons for RescuePro Deluxe. This is software for retrieving lost files from cards. I had used it once many years ago when recovering some shots that had been deleted on the card but not formatted and it had worked well. That was my issue then. Now I needed it due to a problem I hadn’t created.

My first minor problem was that the software defaults to recovering the images to a folder on the C: drive. Since my desktop has an SSD running the OS and everything else on other drives, it isn’t overloaded with space so dumping 32Gb of images on to it caused a minor hiccup. A kicked out of the program, restarted it and found how to change the output directory and then we were off and running. However, now I came across my next issue. It found all of the files on the card, not just the ones that were lost. This is where the brain had a small “doh” moment. I figured if I opened up the card in Explorer and deleted the good shots, it would mean the search would be a lot quicker. Of course, if you are using software designed to find files that have been deleted, it still finds them all. Why didn’t I think of that at the time? Oh well, no big deal since this was all running in the background.

The result of the scan is that all files on the card are now stored in a folder. Unfortunately, they are named sequentially File001, File002 etc. This makes working out which are the missing files a bit more tricky. So, two things were needed for the next step. First, find out the filename for the first file on the card. Then import all of the files into Lightroom by adding them where they are rather than copying them to a new location. With them in Lightroom, it is a simple task to rename them all to their original names using the rename function and making sure you start with the filename of the first file that we found a moment ago. Now all the files have the right name and are still in the recovery folder.

The next step might seem counterintuitive. I delete them all from Lightroom. I don’t delete the master files; just remove them from the catalog. Next – trust me, I haven’t gone mad – I them re-import them all. At this point, Lightroom sees the files with the right names and details and so automatically recognizes which ones are already in the catalog. It then will pick out the ones which were the original missing files and you can import them properly to wherever you want them. Now the recovery folder can be deleted (subject to your normal backup protocols). It sounds a bit complex but, if you work through the process, the longest part of it is the scan of the card for the files in the first place. After that, it all happens pretty quickly.

While RescuePro Deluxe is not the most user friendly piece of software, it did do what was required and I got it free with the cards I have. You don’t own the software. You get a one year subscription with the coupon. Hopefully I won’t need it again this year but it is there if required. I have a bunch of these coupons from various card purchases so I imagine I will be in good shape as long as required. If you have gone through something similar and have a better way of dealing with it, please do let me know. It is always good to learn from the experiences of others.

Updates to the Workflow

Leave a Reply

A while back I wrote a piece about how I manage my workflow when bringing in new pictures from a shoot. If you are so inclined, you can read the original post here. I thought it might be appropriate to bring the topic up to date since I have tweaked the workflow a bit since then. As I mentioned before, this is not all original thinking from me. I have picked up suggestions from a number of places and then adapted them to my own needs. If they are useful to you, that is great. All of this is based on using Lightroom as an image management tool.

The basic process involves creating a series of Smart Collections for a given shoot. I have adapted these collections a little and have a basic set, not all of which are required for every shoot. However, what I have done is exported these collections to a folder on my computer so I can re-import them for each shoot and tweak them rather than start from scratch each time. For example, they all have the keywords section blank so that I can paste in the required keywords for the shoot easily.

I will initially create a Collection Set for the topic and, if this is an event that occurs more than once, a Collection Set within that for the specific date. Then, within that, I shall import the Smart Collections from my templates. In the first instance, these will have lots of files in them since the criteria have not been narrowed down but I shall then edit each one to have the appropriate keywords and, if required, the specific dates. Date Taken is the criterion I will use then, either with a specific date or a range. Of course, this does require me to have put the appropriate keywords on all of the images first including whether they are HDR, panorama or time lapse images.

The following are the smart collections and a description of what they contain. To avoid repetition, it can be assumed that they will all fit the keyword and date range criteria.

Not Rejects – All images that have not been rejected, are not marked as HDR or panoramas and are not video clips
Picks – All images that have been marked as a Pick and are not video clips
HDR Originals – All marked as HDR that are RAW files
HDR Edits – All marked as HDR that are not RAW files
Pano Originals – All marked as panoramas that are RAW files
Pano Edits – All marked as panoramas that are not RAW files
Time lapse – All marked as Time Lapse (Duh!)
Not Geotagged – All files that do not have GPS coordinates associated with them
Videos – All video files not marked as rejects
Rejects – All files marked as rejects (again, duh!)

The reasons for some of these are obvious but others are less so. The not rejects file specifically excludes any shots I have marked as HDR or panorama since, when running through the edits, it is easy to see a shot that makes up one of those processes and think it is boring and delete it. Keeping them separate from the start is important. I keep the originals and the edits apart since, when I come back to them later, it is a lot simpler to look through the finished versions without having to find them amongst the originals. Previously, they ended up in the same smart collection and, after getting bored trying to find the finished one, it occurred to me that they could be kept apart easily.

I now try to geotag all of my images. Having the folder that shows that they haven’t been done reminds me to do this if I have not done it straightaway. I have found that Lightroom has a bug (I have found more than one!) that, when you have imported a bunch of stuff, if you go to the map page, it gets a little lost and keeps the map view looking like the grid view. You can get back out without any problem but have to restart to get back to map view. If you go to map view before doing all of the importing, it seems fine then. However, this folder makes sure I don’t forget to do it at some point.

With all of this set up, it is then easy enough to get into the process I have outlined before. I go to the Not Rejects folder and render 1:1 previews of all of the files. This can take a while so I will often start it off and then go and do something else for a while. I can then come back and run through the images. I will have a full screen version on one screen and the zoomed 1:1 image on the other. This allows me to easily see which shots are not sharp or have an obvious flaw like a pole through the foreground or someone’s head in the way. A quick “X” and that shot disappears from the smart collection and I am on to the next. If it is okay, right arrow and I am moving on. This kills a lot of shots quite quickly.

Then it is a simple case of looking at the shots in Grid view, usually quite large, to see the ones that are duplicate or just plain crap. I can select which to get rid of and “X” again has them consigned to the trash. Once all of this is done, I will run a BluRay backup of all of the shots including the XMP files after which I shall delete all rejects. Hopefully that leaves me with a lot less shots to play with. I can then pick the ones I think are the best and mark them as Picks. It then leaves me with a smaller smart collection which I can go in and pay some attention to making more detailed edits.

This process continues to evolve. Maybe I shall write another update in a couple of years. In the meantime, I hope it might be helpful to someone for me to have shared it. Happy shooting!