Tag Archives: software

Focus Stack Animation

Leave a Reply

In some previous posts I showed the results of experimenting with focus stacking.  In those posts, I would combine one of the individual shots with the finished effort to show how shallow the depth of field could be on individual shots and how deep the focus was on the final image.  I was pondering whether this was an effective way of communicating the concept to someone when it occurred to me that animation might be a better way.  I created a new stack of images for a different subject but this time I used Photoshop to animate the movement of the point of focus through the shot and then show the final image.  This can then be an animated GIF.  I wonder, does this provide a better demonstration?

Learning a Better Way to Blend in Photoshop

Leave a Reply

I occasionally use the Statistics function in Photoshop to blend multiple images in order to get rid of the distractions that I don’t want like people or vehicles.  Up until now, this has been a real pain to do.  I would identify the images in Lightroom but would have to open Photoshop, go into the Statistics function, use the browse function in there to select the images and then it would run everything in one go.  This was not a convenient way to go and the output image then needed to be manually added to Lightroom which is not handy.

It turns out that there is a better way.  This may have been in Photoshop all along and I never knew or it could have been a recent addition.  Either way, it is there and I shall now use it for future projects.  I have even created a Photoshop action to cover the process and assigned a function key so it will now do the heavy lifting without my intervention.  It all starts out in Lightroom.  Select all the images that will be used for the blend.  Then use Edit>Open As Layers and a new document will open in Photoshop with all shots as layers.

If everything has been shot on a tripod, things will be properly aligned by default but I often do these things on the spur of the moment so they are hand held.  Consequently, while my efforts to keep pointing in the same direction are not bad, the first task is to select all layers and Auto Align layers to tidy things up.  Next, go into the Layer tab and, under Smart Object, convert to a Smart Object.  This may take a little while.

Next step is to go back into Layers>Smart Objects>Stack Mode.  This brings up the same options as you get through the Statistics function.  Select Mean and send it on its way and you end up with a shot that, depending on the number of shots taken and the clear space in enough of them, results in a clear shot.  Usually I find that I haven’t got enough shots of the right type to get everything to disappear so some ghostly elements may remain but they are certainly less distracting than the figures in the original shots.  I have no idea what the other modes will achieve and the descriptions Adobe provides in their help files are so obscure as to be virtually useless. Instead I shall have to experiment with them to see what happens.  Thankfully, now I have this new method, I can undo the last step easily to try each option which would not have been possible using the Statistics dialog.  Another win!

WordPress Editor Has Been Broken

Leave a Reply

You’ll often hear the phrase “If it isn’t broken, why fix it?”. In the case of WordPress, this definitely seems to be relevant. I have been using WordPress since the blog started and with good reason. It is a simple and straightforward editing tool that allows new posts to be created easily and quickly. I prepare the images in Lightroom and export them directly to the blog and text is generally – including this – created in Word and then pasted into the blog editor.

WordPress rolled out a new editor form with blocks for elements of each post. I don’t doubt that the intent of this was to create a more flexible editing environment and one that probably achieves things that previously required plugins. However, the result does not seem to have been very well tested or not be a wide enough group of users with differing requirements. Here are some of the shortcomings I have experienced.

The biggest issue is speed. The new format is unbelievably sluggish. When I am making edits, sections of the page seem to be really slow and when it decides to auto save the latest work, it seems to be stuck doing so forever. Then, there are some familiar sections now in new formats at the side. Collections is still there but clicking on it seems to require tons of time to think about stuff before it shows up – if it does!

Collections might be slow but tagging is now horrible. I create my tags in Word and paste them into the field but this no longer can be relied on to work. Sometimes they just vanish. Other times they disappear and then reappear. I can write some in to the box directly and then they vanish in front of my eyes. I often ignore this section and add the tags later in the Quick Edit view of the post lists.

Adding media is no longer so simple, While the new blocks for images and galleries have some nice elements they are slow to create. Now you have to select the source each time rather than defaulting to the media gallery. This extra click each time gets annoying fast. Also, in the old editor, if you scrolled down the media page to get to the shots you wanted, adding another image would bring you back to the same spot so you didn’t have to scroll again. That is gone. Media is added as a new block. There is no obvious way to add a block at the bottom of your post. Instead you add one and see where it shows up and then move it down as required. Meanwhile, at the bottom of the page there is a Sharing box which seems to do little other than get in the way.

Even editing the publishing date is a pain. They have moved that around a bit in keeping with the other changes but now, when you tab between fields, your cursor is at the end o the current data. Previously, tabbing would move you to the next box and select it. This facilitated rapid changes to the entries. Now you have to manually delete each entry and then type a new one. One more step for each entry which is not a big deal initially but soon becomes a nuisance.

The legacy editor is still available. However, it isn’t hard to imagine that, over time, this will become obsolete and won’t provide functionality until it is deleted so I am working with the new format to see what I can do to get to grips with it. However, it is testing my patience. It has significantly slowed down my process and made post creation more difficult than it used to be. I have got the hang of bits of it but getting used to something does not make it useful. Pull your finger out WordPress and sort this out. There are so many users of the system, it is important that it works or they will soon migrate to another platform.

Lightroom Issues Update

Leave a Reply

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!

 

My First Attempt at Focus Stacking

Leave a Reply

I first read about focus stacking a long time ago and I have been meaning to try it for ages.  The premise is to take a series of shots with the focus set in different positions throughout the scene and then to use software to blend the images together to create on image with focus all the way through the shot.  This seemed like a simple thing to have a try with but I never got around to having a go.  Then I came across a situation that looked like it might be a good example to try.

I was visiting a model show at the Museum of Flight.  I was taking a few photos of some of the more expertly crafted models on display.  I was shooting with a longer lens and using a relatively small aperture to try and minimize the shallow depth of field that you get when shooting small objects close up.  I decided to shoot a model of a Fairey Gannet and the shallow depth of field triggered something in the deep recesses of my brain about focus stacking.  Of course, I had not planned for this so no tripod and just an effort to get focus on different parts of the model without moving the camera too much.

I took the shots and got on with my visit.  When I got home, I almost forgot about the stacking experiment but, fortunately, I did remember.  I exported the images to Photoshop as layers of the same shot.  Then, since they were hand held, I did an Auto-Align action to get them in place.  After that, Auto-Blend was selected.  It seemed to realize that they were a blend stack rather than a panorama – quite clever – and the software quickly did its thing.  Despite not taking too many shots and do it all hand held, the result came out pretty well.  The top shot is the finished product while the lower two show the extremes of the focus range for the original shots.  If I had managed a shot focused right on the back of the fin, the result may have been a bit better still.

My Copy of Lightroom Got Sick

Leave a Reply

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.

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!

Creating Lens Profiles for Adobe Software

1 Reply

UPDATE:  It turns out, the upload process for the profile sends to an address that doesn’t work.  While I try to fix this, if you want the profiles to use, you can download them by clicking here.

Within Adobe processing software, there is lens correction functionality built in to the Lightroom Develop module (or Adobe Camera Raw in Photoshop) that compensates for distortion and vignetting in the lens the image was taken with.  Adobe has created a large number of lens profiles but they never created one for the Canon 500mm in its initial version.  Adobe also has an online tool for sharing profiles but this does not include one for this lens either.  The 600mm had a profile and it was supposedly close so I had been using that for a while.  Recently, though, I was shooting with the 1.4x teleconverter fitted and this introduced some new effects which required some manual tweaking to offset.

I still wasn’t happy with the result so I decided it was time to bite the bullet and create some profiles from scratch.  Adobe has a tool for creating a lens profile.  It involves printing out some grid targets which you then shoot a number of times to cover the whole of the frame.  It then calculates the profile.  I was shooting at both 500mm and 700mm so I needed a few targets.  To make a complete profile it is a good idea to shoot at a variety of focusing distances and with a range of apertures.  The tool comes with many targets.  Some I could print at home but some of the larger ones I got printed at FedEx and mounted on foam core to make them more rigid.  Then it was time to shoot a bunch of very boring shots.

The software is not the most intuitive I have ever worked with but it eventually was clear what I had to do.  (Why do some manual writers seem like they have never used the process they are writing about?)  I found out how to run the analysis for different charts and distances separately and append the data to the profile as I go.  I did need to quit the program periodically because it would run out of memory which seems like an odd bug these days.  After much processing and some dropped frames as a result of poor shooting on my part (even on the tripod I got some blur occasionally with very slow shutter speeds) it got a profile out.  The proof of the pudding is in the eating of course (that is what the actual phrase is for those of you that never get past the pudding part) so I tried the profile out on some recent shots.  It works!  I was rather delighted.  I may shoot a few more samples in good conditions to finish things off but this was a rather happy outcome.  Once I have tweaked the profiles sufficiently, I shall upload them to Adobe and anyone can use them.