In quite a few previous posts, I have mentioned the troubles I have had with Lightroom recently. This was all triggered by an update a while back and subsequent updates have not solved any issues. The problems just continued and I was unable to get anything to address the sluggish behavior. The program would respond better when I was working in the Develop module but it was very difficult in Library and when importing.
I recently had a bit more success. I contacted someone who, while not working for Adobe, does have a business based around Lightroom and has good connections with the company. I was able to send this individual a copy of my catalog. They had a play with it and had similar issues with memory overuse so it wasn’t a hardware issue. They were able to pass on the catalog to an Adobe engineer to investigate further. I feared there was some corruption in the catalog and hoped they would find a solution.
It transpires that there is not any corruption. Instead, it is in the nature of the catalogs that I have created that the problem lies. A long time ago I posted about my approach to processing a shoot. I would use a Collection Set for each shoot in which I would use smart collections to take shots with the right combination of keywords and dates. They would split out rejects from non-rejects and put HDR, panorama shots and videos in separate smart collections. This made processing the shoot more efficient.
As a result of this approach, I have, over the years, accumulated a large number of these collection sets with smart collections in them. This is what is causing the trouble. The program is getting bogged down with all of them. This leaves two ways forward. In the short term, I am going to go through these smart collections and turn them into simple collections. Hopefully this will reduce the processing burden. I don’t need the smart functionality any longer so I can just take the selected images and make simple collections out of them.
The longer term action is that Adobe is now aware of this issue. Hopefully they can investigate a way to address this in a future update so that it isn’t constrained in the same way. It happened suddenly so there was something in the coding that changed to cause the issue so maybe it can be similarly quickly fixed. In the early days of Lightroom, it was limited in the number of images it could have before things got sluggish and that was resolved so hopefully this can be too. We shall see. If it is, you’re welcome!
Nearly a year ago I got the new model of the Canon 100-400 EF lens. I had it on back order when it first came out and it arrived just before Christmas so became an impromptu gift to me! Almost everything about the lens I liked. However, if you read my initial thoughts on the lens which I covered here, you will have seen I had a concern about softness in one part of the image. I have used the lens extensively since then and, while I have not always had an issue, I have continued to be concerned about the output in one area – particularly when compared the the excellent sharpness the rest of the image was displaying.
I sent the lens to Canon earlier this year for a service. I explained my concerns and they took a look and told me it was functioning properly and returned it. I took it on another shoot and got more shots which did not look right. This time I emailed CPS and provided them with some sample shots. They suggested it didn’t look right and told me to send the lens back in with a description of everything to date along with more sample images on a card.
I now have the lens on its way back to me. Here is what they found.
Your product has been examined and it was found that the optical assembly was broken causing the auto focus to operate improperly from time to time. The 6th group lens and 2nd group lens were replaced. Product functions were confirmed.
It is nice to know that I wasn’t imagining things but a little disappointing it took this long to get to the bottom of things. Of course, I could have done some of this sooner if I had been more certain of the problem. In future, I will be a bit more willing to trust my instincts. Now to get the repaired lens in my hands and test it!
Living in the city you can get a lot of things happening out of the window. They can spring up and catch your attention but can equally end before you know it. This can be a problem when you are trying to decide whether to go out and see what is happening. One such example happened recently. I was on the phone when I looked out of the window and saw that the Michigan Avenue bridge over the Chicago River was up and didn’t seem to be showing any sign of coming down. Finally it did lower but not completely. This is when the fun started!
One of the Chicago Fire Department’s boats came up to the bridge and then started spraying water on the bridge. It wasn’t clear at all what was going on. Some fire trucks also showed up spraying onto the bridge from each end. I grabbed some shots of this from our windows. This is the time when you have to make a decision. Do I grab my stuff and go down to get more shots and risk that it is all over before I get there or do I stay upstairs to see what happens and find out that it goes on for ages and I could easily have been out and shooting for a while? I have got this decision wrong both ways in the past. This time I decided to go out and see what I could see.
I didn’t find out what was happening since Chicago’s finest were happy to shout at you for stepping in the wrong place but certainly weren’t going to tell you anything. I later found out the bridges had expanded in the heat and needed to be cooled down. I managed to get to a few locations and get some shots before they opened the bridge up again and then lowered it. This time it went where it was supposed to go and a few cheers came from the crews.
Along with shooting some stills, I also grabbed a bit of video. While this won’t win any documentary awards, you can get a feel for what was going on.