I present my top 10 tips for capturing time-lapses of the moving sky.
If you can take one well-exposed image of a nightscape, you can take 300. There’s little extra work required, just your time. But if you have the patience, the result can be an impressive time-lapse movie of the night sky sweeping over a scenic landscape. It’s that simple.
Or is it?
Here are my tips for taking time-lapses, in a series of “Do’s” and “Don’ts” that I’ve found effective for ensuring great results.
But before you attempt a time-lapse, be sure you can first capture well-exposed and sharply focused still shots. Shooting hundreds of frames for a time-lapse will be a disappointing waste of your time if all the images are dark and blurry.
For that reason many of my tips apply equally well to shooting still images. But taking time-lapses does require some specialized gear, techniques, planning, and software. First, the equipment.
NOTE: This article appeared originally in Issue #9 of Dark Sky Travels e-magazine.
TIP 1 — DO: Use a solid tripod
A lightweight travel tripod that might suffice for still images on the road will likely be insufficient for time-lapses. Not only does the camera have to remain rock steady for the length of the exposure, it has to do so for the length of the entire shoot, which could be several hours. Wind can’t move it, nor any camera handling you might need to do mid-shoot, such as swapping out a battery.
The tripod needn’t be massive. For hiking into scenic sites you’ll want a lightweight but sturdy tripod. While a carbon fibre unit is costly, you’ll appreciate its low weight and good strength every night in the field. Similarly, don’t scrimp on the tripod head.
TIP 2 — DO: Use a fast lens
As with nightscape stills, the single best purchase you can make to improve your images of dark sky scenes is not buying a new camera (at least not at first), but buying a fast, wide-angle lens.
Ditch the slow kit zoom and go for at least an f/2.8, if not f/2, lens with 10mm to 24mm focal length. This becomes especially critical for time-lapses, as the fast aperture allows using short shutter speeds, which in turn allows capturing more frames in a given period of time. That makes for a smoother, slower time-lapse, and a shoot you can finish sooner if desired.
TIP 3 — DO: Use an intervalometer
Time-lapses demand the use of an intervalometer to automatically fire the shutter for at least 200 to 300 images for a typical time-lapse. Many cameras have an intervalometer function built into their firmware. The shutter speed is set by using the camera in Manual mode.
Just be aware that a camera’s 15-second exposure really lasts 16 seconds, while a 30-second shot set in Manual is really a 32-second exposure.
So in setting the interval to provide one second between shots, as I advise below, you have to set the camera’s internal intervalometer for an interval of 17 seconds (for a shutter speed of 15 seconds) or 33 seconds (for a shutter speed of 30 seconds). It’s an odd quirk I’ve found true of every brand of camera I use or have tested.
Alternatively, you can set the camera to Bulb and then use an outboard hardware intervalometer (they sell for $60 on up) to control the exposure and fire the shutter. Test your unit. Its interval might need to be set to only one second, or to the exposure time + one second.
How intervalometers define “Interval” varies annoyingly from brand to brand. Setting the interval incorrectly can result in every other frame being missed and a ruined sequence.
SETTING YOUR CAMERA
TIP 4 — DON’T: Underexpose
As with still images, the best way to beat noise is to give the camera signal. Use a wider aperture, a longer shutter speed, or a higher ISO (or all of the above) to ensure the image is well exposed with a histogram pushed to the right.
If you try to boost the image brightness later in processing you’ll introduce not only the very noise you were trying to avoid, but also odd artifacts in the shadows such as banding and purple discolouration.
With still images we have the option of taking shorter, untrailed images for the sky, and longer exposures for the dark ground to reveal details in the landscape, to composite later. With time-lapses we don’t have that luxury. Each and every frame has to capture the entire scene well.
At dark sky sites, expose for the dark ground as much as you can, even if that makes the sky overly bright. Unless you outright clip the highlights in the Milky Way or in light polluted horizon glows, you’ll be able to recover highlight details later in processing.
After poor focus, underexposure, resulting in overly noisy images, is the single biggest mistake I see beginners make.
TIP 5 — DON’T: Worry about 500 or “NPF” Exposure Rules
While still images might have to adhere to the “500 Rule” or the stricter “NPF Rule” to avoid star trailing, time-lapses are not so critical. Slight trailing of stars in each frame won’t be noticeable in the final movie when the stars are moving anyway.
So go for rule-breaking, longer exposures if needed, for example if the aperture needs to be stopped down for increased depth of field and foreground focus. Again, with time-lapses we can’t shoot separate exposures for focus stacking later.
Just be aware that the longer each exposure is, the longer it will take to shoot 300 of them.
Why 300? I find 300 frames is a good number to aim for. When assembled into a movie at 30 frames per second (a typical frame rate) your 300-frame clip will last 10 seconds, a decent length of time in a final movie.
You can use a slower frame rate (24 fps works fine), but below 24 the movie will look jerky unless you employ advanced frame blending techniques. I do that for auroras.
How long it will take to acquire the needed 300 frames will depend on how long each exposure is and the interval between them. An app such as PhotoPills (via its Time lapse function) is handy in the field for calculating exposure time vs. frame count vs. shoot length, and providing a timer to let you know when the shoot is done.
TIP 6 — DO: Use short intervals
At night, the interval between exposures should be no more than one or two seconds. By “interval,” I mean the time between when the shutter closes and when it opens again for the next frame.
Not all intervalometers define “Interval” that way. But it’s what you expect it means. If you use too long an interval then the stars will appear to jump across the sky, ruining the smooth motion you are after.
In practice, intervals of four to five seconds are sometimes needed to accommodate the movement of motorized “motion control” devices that turn or slide the camera between each shot. But I’m not covering the use of those advanced units here. I cover those options and much, much more in 400 pages of tips, techniques and tutorials in my Nightscapes ebook, linked to above.
However, during the day or in twilight, intervals can be, and indeed need to be, much longer than the exposures. It’s at night with stars in the sky that you want the shutter to be closed as little as possible.
TIP 7 — DO: Shoot Raw
This advice also applies to still images where shooting raw files is essential for professional results. But you likely knew that.
However, with time-lapses some cameras offer a mode that will shoot time-lapse frames and assemble them into a movie right in the camera. Don’t use it. It gives you a finished, pre-baked movie with no ability to process each frame later, an essential step for good night time-lapses. And raw files provide the most data to work with.
So even with time-lapses, shoot raw not JPGs.
If you are confident the frames will be used only for a time-lapse, you might choose to shoot in a smaller S-Raw or compressed C-Raw mode, for smaller files, in order to fit more frames onto a card.
But I prefer not to shrink or compress the original raw files in the camera, as some of them might make for an excellent stacked and layered still image where I want the best quality originals (such as for the ISS over Waterton Lakes example above).
To get you through a long field shoot away from your computer buy more and larger memory cards. You don’t need costly, superfast cards for most time-lapse work.
PLANNING AND COMPOSITION
TIP 8 — DO: Use planning apps to frame
All nightscape photography benefits from using one of the excellent apps we now have to assist us in planning a shoot. They are particularly useful for time-lapses.
Apps such as PhotoPills and The Photographer’s Ephemeris are great. I like the latter as it links to its companion TPE 3D app to preview what the sky and lighting will look like over the actual topographic horizon from your site. You can scrub through time to see the motion of the Milky Way over the scenery. The Augmented Reality “AR” modes of these apps are also useful, but only once you are on site during the day.
For planning a time-lapse at home I always turn to a “planetarium” program to simulate the motion of the sky (albeit over a generic landscape), with the ability to add in “field of view” indicators to show the view your lens will capture.
You can step ahead in time to see how the sky will move across your camera frame during the length of the shoot. Indeed, such simulations help you plan how long the shoot needs to last until, for example, the galactic core or Orion sets.
Planetarium software helps ensure you frame the scene properly, not only for the beginning of the shoot (that’s easy — you can see that!), but also for the end of the shoot, which you can only predict.
If your shoot will last as long as three hours, do plan to check the battery level and swap batteries before three hours is up. Most cameras, even new mirrorless models, will now last for three hours on a full battery, but likely not any longer. If it’s a cold winter night, expect only one or two hours of life from a single battery.
TIP 9 — DO: Develop one raw frame and apply settings to all
Processing the raw files takes the same steps and settings as you would use to process still images.
With time-lapses, however, you have to do all the processing required within your favourite raw developer software. You can’t count on bringing multiple exposures into a layer-based processor such as Photoshop to stack and blend images. That works for a single image, but not for 300.
I use Adobe Camera Raw out of Adobe Bridge to do all my time-lapse processing. But many photographers use Lightroom, which offers all the same settings and non-destructive functions as Adobe Camera Raw.
For those who wish to “avoid Adobe” there are other choices, but for time-lapse work an essential feature is the ability to develop one frame, then copy and paste its settings (or “sync” settings) to all the other frames in the set.
Not all programs allow that. Affinity Photo does not. Luminar doesn’t do it very well. DxO PhotoLab, ON1 Photo RAW, and the free Raw Therapee, among others, all work fine.
HOW TO ASSEMBLE A TIME-LAPSE
Once you have a set of raws all developed, the usual workflow is to export all those frames out as high-quality JPGs which is what movie assembly programs need. Your raw developing software has to allow batch exporting to JPGs — most do.
However, none of the programs above (except Photoshop and Adobe’s After Effects) will create the final movie, whether it be from those JPGs or from the raws.
So for assembling the intermediate JPGs into a movie, I often use a low-cost program called TLDF (TimeLapse DeFlicker) available for MacOS and Windows (timelapsedeflicker.com). It offers advanced functions such as deflickering (i.e. smoothing slight frame-to-frame brightness fluctuations) and frame blending (useful to smooth aurora motions or to purposely add star trails).
While there are many choices for time-lapse assembly, I suggest using a program dedicated to the task and not, as many do, a movie editing program. For most sequences, the latter makes assembly unnecessarily difficult and harder to set key parameters such as frame rates.
TIP 10 — DO: Try LRTimelapse for more advanced processing
Get serious about time-lapse shooting and you will want — indeed, you will need — the program LRTimelapse (LRTimelapse.com). A free but limited trial version is available.
This powerful program is for sequences where one setting will not work for all the frames. One size does not fit all.
Instead, LRTimelapse allows you to process a few keyframes throughout a sequence, say at the start, middle, and end. It then interpolates all the settings between those keyframes to automatically process the entire set of images to smooth (or “ramp”) and deflicker the transitions from frame to frame.
This is essential for sequences where the lighting changes during the shoot (say, the Moon rises or sets), and for so-called “holy grails.” Those are advanced sequences that track from daylight or twilight to darkness, or vice versa, over a wide range of camera settings.
However, LRTimelapse works only with Adobe Lightroom or the Adobe Camera Raw/Bridge combination. So for advanced time-lapse work Adobe software is essential.
A Final Bonus Tip
Keep it simple. You might aspire to emulate the advanced sequences you see on the web, where the camera pans and dollies during the movie. I suggest avoiding complex motion control gear at first to concentrate on getting well-exposed time-lapses with just a static camera. That alone is a rewarding achievement.
But before that, first learn to shoot still images successfully. All the settings and skills you need for a great looking still image are needed for a time-lapse. Then move onto capturing the moving sky.
I end with a link to an example music video, shot using the techniques I’ve outlined. Thanks for reading and watching. Clear skies!
The Beauty of the Milky Way from Alan Dyer on Vimeo.
Panoramas featuring the arch of the Milky Way have become the icons of dark sky locations. “Panos” can be easy to shoot, but stitching them together can present challenges. Here are my tips and techniques.
My tutorial complements the much more extensive information I provide in my eBook, at right. Here, I’ll step through techniques for simple to more complex panoramas, dealing first with essential shooting methods, then reviewing the workflows I use for processing and stitching panoramas.
What software works best depends on the number of segments in your panorama, or even on the focal length of the lens you used.
PART 1 — SHOOTING
What Equipment Do You Need?
Nightscape panoramas don’t require any more equipment than what you likely already own for shooting the night sky. For Milky Way scenes you need a fast lens and a solid tripod, but any good DSLR or mirrorless camera will suffice.
The tripod head can be either a ball head or a three-axis head, but it should have a horizontal axis marked with a degree scale. This allows you to move the camera at a correct and consistent angle from segment to segment. I think that’s essential.
What you don’t need is a special, and often costly, panorama head. These rotate the camera around the so-called “nodal point” inside the lens, avoiding parallax shifts that can make it difficult to align and stitch adjacent frames. Parallax shift is certainly a concern when shooting interiors or any scenes with prominent content close to the camera. However, in most nightscapes our scene content is far enough away that parallax simply isn’t an issue.
Though not a necessity, I find a levelling base a huge convenience. As I show above, this specialized ball head goes under the usual tripod head and makes it easy to level the main head. It eliminates all the fussing with trial-and-error adjustments of the length of each tripod leg.
Then to level the camera itself, I use the electronic level now in most cameras. Or, if your camera lacks that feature, an accessory bubble level clipped into the camera’s hot shoe will work.
Having the camera level is critical. It can be tipped up, of course, but not tilted left-right. If it isn’t level the whole panorama will be off kilter, requiring excessive straightening and cropping in processing, or the horizon will wave up and down in the final stitch, perhaps causing parts of the scene to go missing.
NOTE: Click or tap on the panorama images to open a high-res version for closer inspection.
Shooting Horizon Panoramas
While panoramas spanning the entire sky might be what you are after, I suggest starting simpler, with panos that take in just a portion of the 360° horizon and only a part of the 180° of the sky. These “partial panos” are great for auroras (above) or noctilucent clouds, (below), or for capturing just the core of the Milky Way over a landscape.
The key to all panorama success is overlap. Segments should overlap by 30 to 50 percent, enabling the stitching software to align the segments using the content common to adjacent frames. Contrary to some users, I’ve never found an issue with having too much overlap, where the same content is present on several frames.
For a practical example, let’s say you shoot with a 24mm lens on a full-frame camera, or a 16mm lens on a cropped-frame camera. Both combinations yield a field of view across the long dimension of the frame of roughly 80°, and across the short dimension of the frame of about 55°.
That means if you shoot with the camera in “landscape” orientation, panning the camera by 40° between segments would provide a generous 50 percent overlap. The left half of each segment will contain the same content as the right half of the previous segment, if you take your panos by turning from left to right.
TIP: My habit is to always shoot from left to right, as that puts the segments in the correct order adjacent to each other when I view them in browser programs such as Lightroom or Adobe Bridge, with images sorted in chronological order (from first to last images in a set) as I typically prefer. But the stitching will work no matter which direction you rotate the camera.
In the example of a 24mm lens and a camera in landscape orientation you could turn at a 45° or 50° spacing and yield enough overlap. However, turning the camera at multiples of 15° is usually the most convenient, as tripod heads are often graduated with markings at 5° increments, and labeled every 15° or 30°.
Some will have coarser and perhaps unlabeled markings. If so, determine what each increment represents, then take care to move the camera consistently by the amount that will provide adequate overlap.
To maximize the coverage of the sky while still framing a good amount of foreground, a common practice is to shoot panoramas with the camera in portrait orientation. That provides more vertical but less horizontal coverage for each frame. In that case, for adequate overlap with a 24mm lens and full-frame camera shoot at 30° spacings.
TIP: When shooting a partial panorama, for example just to the south for the Milky Way, or to the north for the aurora borealis, my practice is to always shoot a segment farther to the left and another to the right of the main scene. Shoot more than you need. Those end segments can get distorted when stitching, but if they don’t contain essential content, they can be cropped out with no loss, leaving your main scene clean and undistorted.
Shooting with a longer lens, such as a 50mm (or 35mm on a cropped frame camera), will yield higher resolution in the final panorama, but you will have much less sky coverage, unless you shoot multiple tiers, as I describe below. You would also have to shoot more segments, at 15° to 20° spacings, taking longer to complete the shoot.
As the number of segments goes up shooting fast becomes more important, to minimize how much the sky moves from segment to segment, and during each exposure itself, to aid in stitching. Remember, the sky appears to be turning from east to west, but the ground isn’t. So a prolonged shoot can cause problems later as the stitching software tries to align on either the fixed ground or the moving stars.
Panoramas on moonlit nights, as I show above, are relatively easy because exposures are short.
Milky Way panoramas taken on dark, moonless nights are tougher. They require fast apertures (f/2 to f/2.8) and high ISOs (ISO 3200 to 6400), to keep individual exposures no more than 30 to 40 seconds long.
Noise lives in the dark foregrounds, so I find it best to err on the side of overexposure, to ensure adequate exposure for the ground, even if it means the sky is bright and the stars slightly trailed. It’s the “Expose to the Right” philosophy I espouse at length in my eBook.
Advanced users can try shooting in two passes: one at a low ISO and with a long exposure for the fixed ground, and another pass at a higher ISO and a shorter exposure for the moving sky. But assembling such a set will take some deft work in Photoshop to align and mask the two stitched panos. None of the examples here are “double exposures.”
Shooting 360° Panoramas
More demanding than partial panoramas are full 360° panoramas, as above. Here I find it is best to start the sequence with the camera aimed toward the celestial pole (to the north in the northern hemisphere, or to the south in the southern hemisphere). That places the area of sky that moves the least over time at the two ends of the panorama, again making it easier for software to align segments, with the two ends taken farthest apart in time meeting up in space.
In our 24mm lens example, to cover the entire 360° scene shooting with a 45° spacing would require at least eight images (8 x 45 = 360). I used 10 above. Using that same lens with the camera in portrait orientation will require at least 12 segments to cover the entire 360° landscape.
Shooting 360° by 180° Panoramas
More demanding still are 360° panoramas that encompass the entire sky, from the ground below the horizon to the zenith overhead. Above is an example.
To do that with a single row of images requires shooting in portrait orientation with a very wide 14mm rectilinear lens on a full-frame camera. That combination has a field of view of about 100° across the long dimension of the sensor.
That sounds generous, but reaching up to the zenith at an altitude of 90° means only a small portion of the landscape will be included along the bottom of the frame.
To provide an even wider field of view to take in more ground, I use full-frame fish-eye lenses on my full-frame cameras, such as Canon’s old 15mm lens (as shown at top) or Rokinon’s 12mm. Even a circular-format fish-eye will work, such as an 8mm on a full-frame camera or 4.5mm on a cropped-frame camera.
All such fish-eye lenses produce curved horizons, but they take in a wide swath of sky, making it possible to include lots of foreground while reaching well past the zenith. Conventional panorama assembly programs won’t work with such wide and distorted segments, but the specialized programs described below will.
Shooting Multi-Tier Panoramas
The alternative technique for “all-sky” panos is to shoot multiple tiers of images: first, a lower row covering the ground and partway up the sky, followed by an upper row completing the coverage of just the sky at top.
The trick is to ensure adequate overlap both horizontally and vertically. With the camera in landscape orientation that will require a 20mm lens for full-frame cameras, or a 14mm lens for cropped-frame cameras. Either combination can cover the entire sky plus lots of foreground in two tiers, though I usually shoot three, just to be sure!.
Shooting with longer lenses provides incredible resolution for billboard-sized “gigapan” blow-ups, but will require shooting three, if not more, tiers, each with many segments. That starts to become a chore to do manually. Some motorized assistance really helps when shooting multi-tier panoramas.
Automating the Pan Shooting
The dedicated pano shooter might want to look at a device such as the GigaPan Epic models or the iOptron iPano, (shown below), all about $800 to $1000.
I’ve tested the latter and it works great. You program in the lens, overlap, and angular sweep desired. The iPano works out how many segments and tiers will be required, and automates the shooting, firing the shutter for the duration you program, then moving to the new position, firing again, and so on. I’ve shot four-tier panos effortlessly and with great success.
However, these devices are generally bigger and heavier than I care to heft around in the field.
Instead, I use the original Genie Mini from SYRP, (below), a $250 device primarily for shooting motion control time-lapses. But the wireless app that programs the Genie also has a panorama function that automatically slews the camera horizontally between exposures, again based on the lens, overlap, and angular sweep you enter. The just-introduced Genie Mini II is similar, but with even more capabilities for camera control.
While combining two Genie Minis allows programming in a vertical motion as well, I’ve been using just a regular tripod head atop the Mini to manually move the camera vertically between each of the horizontal tiers. I don’t feel the one or two moves needed to go from tier to tier too arduous to do manually, and I like to keep my field gear compact and easy to use.
The Genie Mini (now replaced by the Mini II) works great and I highly recommend it, even if panoramas are your only interest. But it is also one of the best, yet most affordable, single-axis motion control devices on the market for time-lapse work.
When to Shoot the Milky Way
While the right gear and techniques are important, go out on the wrong night and you won’t be able to capture the Milky Way as the great sweeping arch you might have hoped for.
In the northern hemisphere the Milky Way arches directly overhead from late July to October for most of the night. That’s fine for spherical fish-eye panoramas, but in rectangular images when the Milky Way is overhead it gets stretched and distorted across the top of the final panorama. For example, in the Bow Lake by Night panorama above, I cropped out most of this distorted content.
The prime season for Milky Way arches is therefore before the Milky Way climbs overhead, while it is still across the eastern sky, as above. That’s on moonless nights from March to early July, with May and June best for catching it in the evening, and not having to wait up until dawn, as is the case in early spring.
TIP: The best way to figure out when and where the Milky Way will appear is to use a desktop planetarium program such as Starry Night or Sky Safari or the free Stellarium. All can realistically depict the Milky Way for your location and date. You can then step through time to see how the Milky Way will move through the night, and how it will frame with your camera and lens combination using the “field of view” indicators the programs provide.
When shooting in the southern hemisphere I like the April to June period for catching the sweep of the southern Milky Way and the galactic core rising in late evening. By contrast, during mid austral winter in July and August the galactic centre shines directly overhead in the evening, a spectacular sight to be sure, but tough to capture in a panorama except in a spherical or fish-eye scene.
That said, I always like to put in a good word for the often sadly neglected winter Milky Way (the summer Milky Way for those “down under”). While lacking the spectacle of the galactic core in Sagittarius, the “other” Milky Way has its attractions such as Orion and Taurus. The best months for a panorama with that Milky Way in an arch across a rectangular frame are January to March. The Zodiacal Light can be a bonus at that season, as it was above.
TIP: Always shoot raw files for the widest dynamic range and flexibility in recovering details in the highlights and shadows. Even so, each segment has to be well exposed and focused out in the field.
And unless you are doing a “two-pass” double exposure, always shoot each segment with identical exposure settings. This is especially critical for bright sky scenes such twilights or moonlit scenes. Vary the exposure and you might get unsightly banding at the seams.
There’s nothing worse than getting home only to find one or more segments was missed, or was out of focus or badly exposed, spoiling the set.
PART 2 — STITCHING
Developing Panorama Segments
Once you have your panorama segments, the next step is to develop and assemble them. For my workflow, the process of assembling a panorama from its constituent segments begins with developing each of those segments identically.
NOTE: Click or tap on the software screen shots to open a high-res version for closer inspection.
I like to develop each segment’s raw file as fully as possible at this first stage in the workflow, applying noise reduction, colour correction, contrast adjustments, shadow and highlight recovery, and any special settings such as dehaze and clarity that can make the Milky Way pop.
I also apply lens corrections to each raw image. While some feel doing so produces problems with stitching later on, I’ve never found that. I prefer to have each frame with minimal vignetting and distortion when going into stitching. I use Adobe Camera Raw out of Adobe Bridge, but Lightroom Classic has identical functions.
There are several other raw developers that can work well at this stage. In other tests I’ve conducted, Capture One and DxO PhotoLab stand out as producing good results on nightscapes. See my blog from 2017 for more on software choices.
The key is developing each raw file identically, usually by working on one segment, then copying and pasting its settings to all the others in a set. Not all raw developers have this “Copy Settings” function. For example, Affinity Photo does not. It works very well as a layer-based editor to replace Photoshop, but is crude in its raw developing “Persona” functions.
While panorama stitching software will apply corrections to smooth out image-to-image variations, I find it is best to ensure all the segments look as similar as possible at the raw stage for brightness, contrast, and colour correction.
Do be aware that among social media groups and chat rooms devoted to nightscape imaging a lot of myth and misinformation abounds about how to process and stitch panoramas, and why some don’t work. Someone having a problem with a particular pano will ask why, and get ten different answers from well-meaning helpers, most of them wrong!
Stitching Simple Panoramas
For example, if your segments don’t join well it likely isn’t because you needed to use a panorama head (one oft-heard bit of advice). I never do. The issue is usually a lack of sufficient overlap. Or perhaps the image content moved too much from frame to frame as the photographer took too long to shoot the set.
Or, even when quickly-shot segments do have lots of overlap, stitching software can still get confused if adjoining segments contain featureless content or content that changes, such as segments over rippling water with no identifiable “landmarks” for the software to latch onto.
The primary problems, however, arise from using software that just isn’t up to the task. Programs that work great on simple panoramas (as the next three examples show) will fail when trying to stitch a more demanding set of segments.
For example, for partial horizon panos shot with 20mm to 50mm lenses, I’ll use the panorama function now built into Adobe Camera Raw (ACR) and Adobe Lightroom Classic, and also in the mobile-friendly Lightroom app. As I show above, ACR can do a wonderful job, yielding a raw DNG file that can continue to be edited non-destructively. It’s by far the easiest and fastest option, and is my first choice.
Another choice, not shown here, is the Photomerge function from within Photoshop, which yields a layered and masked master file, and provides the option for “content-aware” filling of missing areas. It can sometimes work on panos that ACR balks at.
Two programs popular as Adobe alternatives, ON1 PhotoRAW (above) and the aforementioned Affinity Photo (below), also have very capable panorama stitching functions.
However, in testing both programs with the demanding Bow Lake multi-tier panorama I used below with other programs, ON1 2019.5 did an acceptable job, while Affinity 1.7 failed. It works best on simpler panoramas, like this partial scene with a 24mm lens.
Even if they succeed when stitching 360° panoramas, such general-purpose editing programs, Adobe’s included, provide no option for choosing how the final scene gets framed. You have no control over where the program puts the ends of the scene.
Or the program just fails, producing a result like this.
Far worse is that multi-tier panoramas or, as I show above, even single-tier panos shot with very wide lenses, will often completely befuddle your favourite editing software, with it either refusing to perform the stitch or producing bizarre results.
Some photographers attempt to correct such wild distortions with lots of ad hoc adjustments with image-warping filters. But that’s completely unnecessary if you use the right software to begin with.
Stitching Complex Panoramas
When conventional software fails, I turn to the dedicated stitching program PTGui, $150 for MacOS or Windows. The name comes from “Panorama Tools – Graphical User Interface.”
While PTGui can read raw files from most cameras, it will not read any of the development adjustments you made to those files using Lightroom, Camera Raw, or any other raw developers.
So, my workflow is to develop all the raw segments, export them out as 16-bit TIFFs, then import those into PTGui. It can detect what lens was used to take the images, information PTGui needs to stitch accurately. If you used a manual lens you can enter the lens focal length and type (rectilinear or fish-eye) yourself.
I include a full tutorial on using PTGui in my eBook linked to above, but suffice to say that the program usually does a superb job first time and very quickly. You can drag the panorama around to frame the scene as you like, and change the projection at will to create rectangular or spherical format images, as above, and even so-called “little planet” projections that appear as if you were looking down at the scene from space.
Occasionally PTGui complains about some frames, requiring you to manually intervene to pick the same stars or horizon features in adjacent frames to provide enough matching alignment points until it is happy. Its interface also leaves something to be desired, with essential floating windows disappearing behind other mostly blank panels.
When exporting the finished panorama I usually choose to export it as a layered 16-bit Photoshop .PSD or, with big panos, as a Photoshop .PSB “big” document.
The reason is that in aligning the moving stars PTGui (indeed, all programs) can produce a few “fault lines” along the horizon, requiring a manual touch up to the masks to clean up mismatched horizon content, as I show above. Having a layered and masked master makes this easy to do non-destructively, though that’s best done in Photoshop.
However, Affinity Photo (above) can also read layered .PSD and .PSB Photoshop files, preserving the layers. By comparison, ON1 PhotoRAW flattens layered Photoshop files when it imports them, one deficiency that prevents this program from being a true Photoshop alternative.
Once a 360° panorama is in a program like Photoshop, some photographers like to “squish” the panorama horizontally to make it more square, for ease of printing and publication. I prefer not to do that, as it makes the Milky Way look overly tall, distorted, and in my opinion, ugly. But each to their own style.
You can test out a limited trial version of PTGui for free, but I think it is worth the cost as an essential tool for panorama devotees.
Other Stitching Options
However, Windows users can also try Image Composite Editor (ICE), free from Microsoft Research. As shown above in my test 3-tier pano, ICE works very well on complex panoramas, has a clean, user-friendly interface, offers a choice of geometric projections, and can export a master file with each segment on its own layer, if desired, for later editing.
The free, open source program HugIn is based on the same Panorama Tools root software that PTGui uses. However, I find HugIn’s operation clunky and overly technical. Its export process is arcane yet renders out only a flattened image.
In testing it with the same three-tier 21-segment pano that PTGui and ICE handled perfectly, HugIn failed to properly include one segment. However, it is free for MacOS and Windows, and so the price is right and is well worth a try.
With the superb tools now at our disposal, it is possible to create detailed panoramas of the night sky that convey the majesty of the Milky Way – and the night sky – as no single image can. Have fun!
To Adobe or not to Adobe. That is the question many photographers are asking with the spate of new image processing programs vying to “kill Photoshop.”
I tested more than ten contenders as alternatives to Adobe’s image processing software, evaluating them ONLY for the specialized task of editing demanding nightscape images taken under the Milky Way, both for single still images and for time-lapses of the moving sky. I did not test these programs for other more “normal” types of images.
Also, please keep in mind, I am a Mac user and tested only programs available for MacOS, though many are also available for Windows. I’ve indicated these.
But I did not test any Windows-only programs. So sorry, fans of Paintshop Pro (though see my note at the end), Photoline, Picture Window Pro, or Xara Photo & Graphic Designer. They’re not here. Even so, I think you will find there’s plenty to pick from!
If you are hoping there’s a clear winner in the battle against Adobe, one program I can say does it all and for less cost and commitment, I didn’t find one.
However, a number of contenders offer excellent features and might replace at least one member of Adobe’s image processing suite.
For example, only four of these programs can truly serve as a layer-based editing program replacing Photoshop.
The others are better described as Adobe Lightroom competitors – programs that can catalog image libraries and develop raw image files, with some offering adjustment layers for correcting color, contrast, etc. But as with Lightroom, layering of images – to stack, composite, and mask them – is beyond their ability.
For processing time-lapse sequences, however, we don’t need, nor can we use, the ability to layer and mask several images into one composite.
What we need for time-lapses is to:
Develop a single key raw file, then …
Copy its settings to the hundreds of other raw files in the time-lapse set, then …
Export that folder of raw images to “intermediate JPGs” for assembly into a movie.
Even so, not all these contenders are up to the task.
Here are the image processing programs I looked at. Costs are in U.S. dollars. Most have free trial copies available.
The Champion from Adobe
Adobe Camera Raw (ACR), Photoshop, Bridge, and Lightroom, the standards to measure others by
Cost: $10 a month by subscription, includes ACR, Photoshop, Bridge, and Lightroom
Adobe Camera Raw (ACR) is the raw development plug-in that comes with Photoshop and Adobe Bridge, Adobe’s image browsing application that accompanies Photoshop. Camera Raw is equivalent to the Develop module in Lightroom, Adobe’s cataloguing and raw processing software. Camera Raw and Lightroom have identical processing functions and can produce identical results.
Photoshop and Lightroom complement each other and are now available together, but only by monthly subscription through Adobe’s Creative Cloud service, at $10/month. Though $120 for a year is not far off the cost of purchasing many of these other programs and perhaps upgrading them annually, many photographers prefer to purchase their software and not subscribe to it.
Thus the popularity of these alternative programs. Most offered major updates in late 2017.
My question is, how well do they work? Are any serious contenders to replace Photoshop or Lightroom?
Lightroom Contenders: Five Raw Developers
ACDSee Photo Studio (current as of late 2017)
Cost: $60 to $100, depending on version, upgrades $40 to $60.
I tested the single MacOS version. Windows users have a choice of either a Standard or Professional version. Only the Pro version offers the full suite of raw development features, in addition to cataloging functions. The MacOS version resembles the Windows Pro version.
Capture One v11 (late 2017 release)
Cost: $299, and $120 for major upgrades, or by subscription for $180/year
As of version 11 this powerful raw developer and cataloguing program offers “Layers.” But these are only for applying local adjustments to masked areas of an image. You cannot layer different images. So Capture One cannot be used like Photoshop, to stack and composite images. It is a Lightroom replacement only, but a very good one indeed.
The ELITE version of what DxO now calls “PhotoLab” offers DxO’s superb PRIME noise reduction and excellent ClearView contrast enhancement feature. While it has an image browser, PhotoLab does not create a catalog, so this isn’t a full Lightroom replacement, but it is a superb raw developer. DxO also recently acquired the excellent Nik Collection of image processing plug-ins, so we can expect some interesting additions and features.
This free open source program has been created and is supported by a loyal community of programmers. It offers a bewildering blizzard of panels and controls, among them the ability to apply dark frames and flat field images, features unique among any raw developer and aimed specifically at astrophotographers. Yes, it’s free, but the learning curve is precipitous.
Photoshop Contenders: Four Raw Developers with Layering/Compositing
These programs can not only develop at least single raw images, if not many, but also offer some degree of image layering, compositing, and masking like Photoshop.
However, only ON1 Photo RAW can do that and also catalog/browse images as Lightroom can. Neither Affinity, Luminar, or Pixelmator offer a library catalog like Lightroom, nor even a file browsing function such as Adobe Bridge, serious deficiencies I feel.
This is the lowest cost raw developer and layer-based program on offer here, and has some impressive features, such as stacking images, HDR blending, and panorama stitching. However, it lacks any library or cataloguing function, so this is not a Lightroom replacement, but it could replace Photoshop.
Macphun has changed their name to Skylum and now makes their fine Luminar program for both Mac and Windows. While adding special effects is its forte, Luminar does work well both as a raw developer and layer-based editor. But like Affinity, it has no cataloguing feature. It cannot replace Lightroom.
Of all the contenders tested here, this is the only program that can truly replace both Lightroom and Photoshop, in that ON1 has cataloguing, raw developing, and image layering and masking abilities. In fact, ON1 allows you to migrate your Lightroom catalog into its format. However, ON1’s cost to buy and maintain is similar to Adobe’s Creative Cloud Photo subscription plan. It’s just that ON1’s license is “perpetual.”
NOTE: Windows users might find Corel’s Paintshop Pro 2018 a good “do-it-all” solution – I tested only Corel’s raw developer program Aftershot Pro, which Paintshop Pro uses.
The “Pro” version of Pixelmator was introduced in November 2017. It has an innovative interface and many fine features, and it allows layering and masking of multiple images. However, it lacks some of the key functions (listed below) needed for nightscape and time-lapse work. Touted as a Photoshop replacement, it isn’t there yet.
This is the image I threw at all the programs, a 2-minute exposure of the Milky Way taken at Writing-on-Stone Provincial Park in southern Alberta in late July 2017.
NOTE: Click/tap on any of the screen shots to bring them up full screen so you can inspect and save them.
The lens was the Sigma 20mm Art lens at f/2 and the camera the Nikon D750 at ISO 1600.
Thus the ground is blurred. Keep that in mind, as it will always look fuzzy in the comparison images. But it does show up noise well, including hot pixels. This image of the sky is designed to be composited with one taken without the tracker turning, to keep the ground sharp.
Above is the image after development in Adobe Camera Raw (ACR), using sliders under its Basic, Tone Curve, Detail, HSL, Lens Corrections, and Effects tabs. Plus I added a “local adjustment” gradient to darken the sky at the top of the frame. I judged programs on how well they could match or beat this result.
Above is the same image developed in Adobe Lightroom, to demonstrate how it can achieve identical results to Camera Raw, because at heart it is Camera Raw.
I have assumed a workflow that starts with raw image files from the camera, not JPGs, for high-quality results.
And I have assumed the goal of making that raw image look as good as possible at the raw stage, before it goes to Photoshop or some other bit-mapped editor. That’s an essential workflow for time-lapse shooting, if not still-image nightscapes.
However, I made no attempt to evaluate all these programs for a wide range of photo applications. That would be a monumental task!
Nor, in the few programs capable of the task, did I test image layering. My focus was on developing a raw image. As such, I did not test the popular free program GIMP, as it does not open raw files. GIMP users must turn to one of the raw developers here as a first stage.
If you are curious how a program might perform for your purposes and on your photos, then why not test drive a trial copy?
Instead, my focus was on these programs’ abilities to produce great looking results when processing one type of image: my typical Milky Way nightscape, below.
Such an image is a challenge because…
The subject is inherently low in contrast, with the sky often much brighter than the ground. The sky needs much more contrast applied, but without blocking up the shadows in the ground.
The sky is often plagued by off-color tints from artificial and natural sky glows.
The ground is dark, perhaps lit only by starlight. Bringing out landscape details requires excellent shadow recovery.
Key to success is superb noise reduction. Images are shot at high ISOs and are rife with noise in the shadows. We need to reduce noise without losing stars or sharpness in the landscape.
I focused on being able to make one image look as good as possible as a raw file, before bringing it into Photoshop or a layer-based editor – though that’s where it will usually end up, for stacking and compositing, as per the final result shown at the end.
I then looked at each program’s ability to transfer that one key image’s settings over to what could be hundreds of other images taken that night, either for stacking into star trails or for assembling into a time-lapse movie.
None of the programs I tested ticked all the boxes in providing all the functions and image quality of the Adobe products.
But here’s a summary of my recommendations:
For Advanced Time-Lapse
None of the non-Adobe programs will work with the third-party software LRTimelapse (www.lrtimelapse.com). It is an essential tool for advanced time-lapse processing. LRTimelapse works with Lightroom or ACR/Bridge to gradually shift processing settings over a sequence, and smooth annoying image flickering.
If serious and professional time-lapse shooting is your goal, none of the Adobe contenders will work. Period. Subscribe to Creative Cloud. And buy LRTimelapse.
For Basic Time-Lapse
However, for less-demanding time-lapse shooting, when the same settings can be applied to all the images in a sequence, then I feel the best non-Adobe choices are, in alphabetical order:
Corel Aftershot Pro
ON1 Photo RAW
… With, in my opinion, DxO and Capture One having the edge for image quality and features. But all five have a Library or Browser mode with easy-to-use Copy & Paste and Batch Export functions needed for time-lapse preparation.
Also worth a try is PhotoDirector9 (MacOS and Windows), a good Lightroom replacement. Scroll to the end for more details and a link.
For Still Image Nightscapes
If you are processing just individual still images, perhaps needing only to stack or composite a few exposures, and want to do all the raw development and subsequent layering of images within one non-Adobe program, then look at (again alphabetically):
ON1 Photo RAW 2018
… With Affinity Photo having the edge in offering a readily-available function off its File menu for stacking images, either for noise smoothing (Mean) or creating star trails (Maximum).
However, I found its raw development module did not produce as good a result as most competitors due to Affinity’s poorer noise reduction and less effective shadow and highlight controls. Using Affinity’s “Develop Persona” module, I could not make my test image look as good as with other programs.
Luminar 2018 has better noise reduction but it demands more manual work to stack and blend images.
While ON1 Photo Raw has some fine features and good masking tools, it exhibits odd de-Bayering artifacts, giving images a cross-hatched appearance at the pixel-peeping level. Sky backgrounds just aren’t smooth, even after noise reduction.
To go into more detail, these are the key factors I used to compare programs.
Absolutely essential is effective noise reduction, of luminance noise and chrominance color speckles and splotches.
Ideally, programs should also have a function for suppressing bright “hot” pixels and dark “dead” pixels.
Here’s what I consider to be the “gold standard” for noise reduction, Adobe Camera Raw’s result using the latest processing engine in ACR v10/Photoshop CC 2018.
I judged other programs on their ability to produce results as good as this, if not better, using their noise reduction sliders. Some programs did better than others in providing smooth, noiseless skies and ground, while retaining detail.
For example, one of the best was DxO PhotoLab, above. It has excellent options for reducing noise without being overwhelming in its choices, the case with a couple of other programs. For example, DxO has a mostly effective dead/hot pixel removal slider.
ACR does apply such a hot pixel removal “under the hood” as a default, but often still leaves many glaring hot specks that must be fixed later in Photoshop.
Comparing Noise Reduction
Above are 8 of the contender programs compared to Camera Raw for noise reduction.
Missing from this group is the brand new Pixelmator Pro, for MacOS only. It does not yet have any noise reduction in its v1 release, a serious deficiency in imaging software marketed as “Pro.” For that reason alone, I cannot recommend it. I describe its other deficiencies below.
The wide-angle lenses we typically use in nightscape and time-lapse imaging suffer from vignetting and lens distortions. Having software that can automatically detect the lens used and apply bespoke corrections is wonderful.
Only a few programs, such as Capture One (above), have a library of camera and lens data to draw upon to apply accurate corrections with one click. With others you have to dial in corrections manually by eye, which is crude and inaccurate.
Shadows and Highlights
All programs have exposure and contrast adjustments, but the key to making a Milky Way nightscape look good is being able to boost the shadows (the dark ground) while preventing the sky from becoming overly bright, yet while still applying good contrast to the sky.
Of the contenders, I liked DxO PhotoLab best (shown above), not only for its good shadow and highlight recovery, but also excellent “Smart Lighting” and “ClearView” functions which served as effective clarity and dehaze controls to snap up the otherwise low-contrast sky. With most other programs it was tough to boost the shadows without also flattening the contrast.
On the other hand, Capture One’s excellent layering and local adjustments did make it easier to brush in adjustments just to the sky or ground.
However, any local adjustments like those will be feasible only for still images or time-lapses where the camera does not move. In any motion control sequences the horizon will be shifting from frame to frame, making precise masking impractical over a sequence of hundreds of images.
Therefore, I didn’t place too much weight on the presence of good local adjustments. But they are nice to have. Capture One, DxO PhotoLab, and ON1 win here.
Selective Color Adjustments
All programs allow tweaking the white balance and overall tint.
But it’s beneficial to also adjust individual colors selectively, to enhance red nebulas, enhance or suppress green airglow, bring out green grass, or suppress yellow or orange light pollution.
Some programs have an HSL panel (Hue, Saturation, Lightness) or an equalizer-style control for boosting or dialing back specific colors.
Capture One (above) has the most control over color correction, with an impressive array of color wheels and sliders that can be set to tweak a broad or narrow range of colors.
And yet, despite this, I was still unable to make my test image look quite the way I wanted for color balance. ACR and DxO PhotoLab still won out for the best looking final result.
Copy and Paste Settings
Even when shooting nightscape stills we often take several images to stack later. It’s desirable to be able to process just one image, then copy and paste its settings to all the others in one fell swoop. And then to be able to inspect those images in thumbnails to be sure they all look good.
Some programs (Affinity Photo, Luminar, Pixelmator Pro) lack any library function for viewing or browsing a folder of thumbnail images. Yes, you can export a bunch of images with your settings applied as a user preset, but that’s not nearly as good as actually seeing those images displayed in a Browser mode.
What’s ideal is a function such as ON1 Photo RAW displays here, and that some other programs have: the ability to inspect a folder of images, work on one, then copy and paste its settings to all the others in the set.
This is absolutely essential for time-lapse work, and nice to have even when working on a small set to be stacked into a still image.
Once you develop a folder of raw images with “Copy and Paste,” you now have to export them with all those settings “baked into” the exported files.
This step is to create an intermediate set of JPGs to assemble into a movie. Or perhaps to stack into a star trail composite using third party software such as StarStaX, or to work on the images in another layer-based program of your choice.
As ON1 Photo RAW shows above, this is best done using a Library or Browser mode to visually select the images, then call up an Export panel or menu to choose the image size, format, quality, and location for the exports.
Click Export and go for coffee – or a leisurely dinner – while the program works through your folder. All programs took an hour or more to export hundreds of images.
Those functions were the key features I looked for when evaluating the programs for nightscape and time-lapse work.
Every program had other attractive features, often ones I wished were in Adobe Camera Raw. But if the program lacked any of the above features, I judged it unsuitable.
Yes, the new contenders to the Photoshop crown have the benefit of starting from a blank slate for interface design.
Many, such as Luminar 2018 above, have a clean, attractive design, with less reliance on menus than Photoshop.
Photoshop has grown haphazardly over 25 years, resulting in complex menus. Just finding key functions can take many tutorial courses!
But Adobe dares to “improve” Photoshop’s design and menu structure at its peril, as Photoshop fans would scream if any menus they know and love were to be reorganized!
The new mobile-oriented Lightroom CC is Adobe’s chance to start afresh with a new interface.
Summary Table of Key Features
Fair = Feature is present but doesn’t work as easily or produce as good a result
Partial = Program has lens correction but failed to fully apply settings automatically / DxO has a Browse function but not Cataloging
Manual = Program has only a manually-applied lens correction
– = Program is missing that feature altogether
I could end the review here, but I feel it’s important to present the evidence, in the form of screen shots of all the programs, showing both the whole image, and a close-up to show the all-important noise reduction.
ACDSee Photo Studio
PROS: This capable cataloging program has good selective color and highlight/shadow recovery, and pretty smooth noise reduction. It can copy and paste settings and batch export images, for time-lapses. It is certainly affordable, making it a low-cost Lightroom contender.
CONS: It lacks any gradient or local adjustments, or even spot removal brushes. Lens corrections are just manual. There is no dehaze control, which can be useful for snapping up even clear night skies. You cannot layer images to create composites or image stacks. This is not a Photoshop replacement.
PROS: Affinity supports image layers, masking with precise selection tools, non-destructive “live” filters (like Photoshop’s Smart Filters), and many other Photoshop-like functions. It has a command for image stacking with a choice of stack modes for averaging and adding images.
It’s a very powerful but low cost alternative to Photoshop, but not Lightroom. It works fine when restricted to working on just a handful of images.
CONS: Affinity has no lens correction database, and I found it hard to snap up contrast in the sky and ground without washing them out, or having them block up. Raw noise reduction was acceptable but not up to the best for smoothness. It produced a blocky appearance. There are no selective color adjustments.
Nor is there any library or browse function. You can batch export images, but only through an unfriendly dialog box that lists images only by file name – you cannot see them. Nor can you copy and paste settings visually, but only apply a user-defined “macro” to develop images en masse upon export.
This is not a program for time-lapse work.
Capture One 11
PROS: With version 11 Capture One became one of the most powerful raw developers, using multiple layers to allow brushing in local adjustments, a far better method than Adobe Camera Raw’s local adjustment “pins.” It can create a catalog from imported images, or images can be opened directly for quick editing. Its noise reduction was good, with hot pixel removal lacking in Camera Raw.
Its color correction options were many!
It can batch export images. And it can export files in the raw DNG format, though in tests only Adobe Camera Raw was able to read the DNG file with settings more or less intact.
CONS: It’s costly to purchase, and more expensive than Creative Cloud to subscribe to. Despite all its options I could never quite get as good looking an image using Capture One, compared to DxO PhotoLab for example.
It is just a Lightroom replacement; it can’t layer images.
Corel Aftershot Pro 3
PROS: This low-cost option has good noise reduction using Athentech’s Perfectly Clear process, with good hot pixel or “impulse” noise removal. It has good selective color and offers adjustment layers for brushing in local corrections. And its library mode can be used to copy and paste settings and batch export images.
Again, it’s solely a Lightroom alternative.
CONS: While it has a database of lenses, and identified my lens, it failed to apply any automatic corrections. Its shadow and highlight recovery never produced a satisfactory image with good contrast. Its local adjustment brush is very basic, with no edge detection.
PROS: I found DxO produced the best looking image, better perhaps than Camera Raw, because of its DxO ClearView and Smart Lighting options. It has downloadable camera and lens modules for automatic lens corrections. Its noise reduction was excellent, with its PRIME option producing by far the best results of all the programs, better perhaps than Camera Raw, plus with hot pixel suppression.
DxO has good selective color adjustments, and its copy and paste and batch export work fine.
CONS: There are no adjustment layers as such. Local adjustments and repairing are done through the unique U-Point interface which works something like ACR’s “pins,” but isn’t as visually intuitive as masks and layers. Plus, DxO is just a raw developer; there is no image layering or compositing. Nor does it create a catalog as such.
So it is not a full replacement for either Lightroom or Photoshop. But it does produce great looking raw files for export (even as raw DNGs) to other programs.
PROS: Luminar has good selective color adjustments, a dehaze control, and good contrast adjustments for highlights, mid-tones, and shadows. Adjustments can be added in layers, making them easier to edit. Noise reduction was smooth and artifact-free, but adjustments were basic. Many filters can be painted on locally with a brush, or with a radial or gradient mask.
CONS: It has no lens correction database; all adjustments are manual. The preview was slow to refresh and display results when adjusting filters. The interface is clean but always requires adding filters to the filter panel to use them when creating new layers. Its batch export is crude, with only a dialog box and no visual browser to inspect or select images.
Settings are applied as a user preset on export, not through a visual copy-and-paste function. I don’t consider that method practical for time-lapses.
ON1 Photo RAW 2018
PROS: ON1 is the only program of the bunch that can: catalog images, develop raw files, and then layer and stack images, performing all that Lightroom and Photoshop can do. It is fast to render previews in its “Fast” mode, but in its “Accurate” mode ON1 is no faster than Lightroom. It has good layering and masking functions, both in its Develop mode and in its Photoshop-like Layers mode.
Selective color and contrast adjustments were good, as was noise reduction. Developing, then exporting a time-lapse set worked very well, but still took as long as with Lightroom or Photoshop.
CONS: Despite promising automatic lens detection and correction, ON1 failed to apply any vignetting correction for my 20mm Sigma lens. Stars exhibited dark haloes, even with no sharpening, dehaze, or noise reduction applied. Its de-Bayering algorithm produced a cross-hatched pattern at the pixel level, an effect not seen on other programs.
Noise reduction did not smooth this. Thus, image quality simply wasn’t as good.
PROS: It is low cost. And it has an attractive interface.
CONS: As of version 1 released in November 2017 Pixelmator Pro lacks: any noise reduction (it’s on their list to add!), any library mode or copy and paste function, nor even the ability to open several images at once displayed together.
It is simply not a contender for “Photoshop killer” for any photo application, despite what click-bait “reviews” promise, ones that only re-write press releases and don’t actually test the product.
Raw Therapee v5.3
PROS: It’s free! It offers an immense number of controls and sliders. You can even change the debayering method. It detects and applies lens corrections (though in my case only distortion, not vignetting). It has good selective color with equalizer-style sliders. It has acceptable (sort of!) noise reduction and sharpening with a choice of methods, and with hot and dead pixel removal.
It can load and apply dark frames and flat fields, the only raw developer software that can. This is immensely useful for deep-sky photography.
CONS: It offers an immense number of controls and sliders! Too many! It is open source software by committee, with no one in charge of design or user friendliness. Yes, there is documentation, but it, too, is a lot to wade through to understand, especially with its broken English translations. This is software for digital signal processing geeks.
But worst of all, as shown above, its noise reduction left lots of noisy patches in shadows, no matter what combination of settings I applied. Despite all its hundreds of sliders, results just didn’t look as good.
What About …? (updated December 28)
No matter how many programs I found to test, someone always asks, “What about …?” In some cases such comments pointed me to programs I wasn’t even aware of, but subsequently tried out. So here are even more to pick from…
Billed as having “everything you need in an image editor,” this low-cost ($30) MacOS-only program is anything but. Its raw developer module is crude and lacks any of the sophisticated range of adjustments offered by all the other programs on offer here. It might be useful as a layer-based editor of images developed by another program.
Available for Mac and Windows for $150, this Lightroom competitor offers a good browser function, with the ability to “copy-from-one and paste-to-many” images (unlike some of the programs below), and a good batch export function for time-lapse work. It has good selective color controls and very good noise reduction providing a smooth background without artifacts like blockiness or haloes. Local adjustments, either through brushed-on adjustments or through gradients, are applied via handy and easy to understand (I think!) layers.
While it has auto lens corrections, its database seemed limited — it did not have my Sigma 20mm lens despite it being on the market for 18 months. Manual vignetting correction produced a poor result with just a washed out look.
The main issue was that its shadow, highlight, and clarity adjustments just did not produce the snap and contrast I was looking for, but that other programs could add to raw files. Still, it looks promising, and is worth a try with the trial copy. You might find you like it. I did not. For similar cost, other programs did a better job, notably DxO PhotoLab.
In the same ilk as Raw Therapee, I also tested out another free, open-source raw developer, one simply called “darktable,” with v2.2.5 shown below. While it has some nice functions and produced a decent result, it took a lot of time and work to use.
The MacOS version I tried (on a brand new 5K iMac) ran so sluggishly, taking so long to re-render screen previews, that I judged it impractical to use. Sliders were slow to move and when I made any adjustments often many seconds would pass before I would see the result. Pretty frustrating, even for free.
A similar crowd-developed raw processing program, Iridient Developer (above), sells for $99 US. I tested a trial copy of v3.2. While it worked OK, I was never able to produce a great looking image with it. It had no redeeming features over the competition that made its price worthwhile.
Using Parallels running Windows 10 on my Mac, I did try out this popular Windows-only program from Corel. By itself, Paintshop Pro’s raw developer module (shown above) is basic, crude and hardly up to the tax of processing demanding raw files. You are prompted to purchase Corel’s Aftershot Pro for more capable raw development, and I would agree – Aftershot would be an essential addition. However …
As I showed above, I did test the MacOS version of Aftershot Pro on my raw sample image, and found it did the poorest job of making my raw test image look good. Keep in mind that it is the ability of all these programs to develop this typical raw nightscape image that I am primarily testing.
That said, given a well-developed raw file, Paintshop Pro can do much more with it, such as further layering of images and applying non-destructive and masked adjustment layers, as per Photoshop. Indeed, it is sold as a low-cost (~ $60) Photoshop replacement. As such, many Windows users find Paintshop’s features very attractive. However, Paintshop lacks the non-destructive “smart” filters, and the more advanced selection and masking options offered by Photoshop, Affinity Photo, and ON1 Photo Raw. If you have never used these, you likely don’t realize what you are missing.
If it’s an Adobe alternative you are after, I would suggest Windows users would be better served by other options. Why not test drive Affinity and ON1?
This was a surprising find. Little known, certainly to me, this Windows and MacOS program from the Taiwanese company Cyberlink, is best described as a Lightroom substitute, but it’s a good one. Its regular list price is $170. I bought it on sale for $60.
Like Lightroom, working on any images with PhotoDirector requires importing them into a catalog. You cannot just browse to the images. Fine. But one thing some people complain about with Lightroom is the need to always import images.
I was impressed with how good a job PhotoDirector did on my raw test image. PhotoDirector has excellent controls for shadow and highlight recovery, HSL selective color, copying-and-pasting settings, and batch exporting. So it will work well for basic time-lapse processing.
Noise reduction was very good and artifact-free. While it does have automatic lens corrections, its database did not include the 2-year old Sigma 20mm Art lens I used. So it appears its lens data is not updated frequently.
PhotoDirector has good local adjustments and gradients using “pins” rather than layers, similar to Camera Raw and Lightroom.
After performing raw image “Adjustments,” you can take an image into an Edit module (for adding special effects), then into a Layers module for further work. However, doing so destructively “flattens” the image to apply the raw adjustments you made. You cannot go back and tweak the raw settings in the Adjustment module, as you can when opening a raw file as a “smart object” in Adobe Photoshop.
While PhotoDirector does allow you to layer in other images to make basic composites (such as adding type or logos), there is no masking function nor any non-destructive adjustment layers. So this is most assuredly not a Photoshop substitute, despite what the advertising might suggest. But if it’s a Lightroom replacement you are after, do check it out in a trial copy.
This little-known MacOS-only program (only $40 on sale) for developing raw images looks very attractive, with good selective color, lots of local adjustments, and good masking tools, the features promoted on the website. It does have a browse function and can batch export a set of developed files.
However … its noise reduction was poor, introducing glowing haloes around stars when turned up to any useful level. Its shadows, highlights, and contrast adjustments were also poor – it was tough to make the test image look good without flattening contrast or blocking up shadows. Boosting clarity even a little added awful dark haloes to stars, making this a useless function. It has no lens correction, either automatic or manual. Like Topaz Studio, below, it cannot copy and paste settings to a batch of images, only to one image at a time, so it isn’t useful for time-lapse processing.
I cannot recommend this program, no matter how affordable it might be.
Popular among some camera manufacturers as their included raw developer, Silky Pix can be purchased separately ($80 list price for the standard version, $250 list price for the Pro version) with support for many cameras’ image files. It is available for MacOS and Windows. I tried the lower-cost “non-Pro” version 8. It did produce a good-looking end result, with good shadow and highlight recovery, and excellent color controls. Also on the plus side, Silky Pix has very good copy-and-paste functions for development settings, and good batch export functions, so it can be used to work on a folder of time-lapse frames.
On the down side, noise reduction, while acceptable, left an odd mottled pattern, hardly “silky.” The added “Neat” noise reduction option only smoothed out detail and was of little value except perhaps for very noisy images. Noise reduction did nothing to remove hot pixels, leaving lots of colored specks across the image. The program uses unorthodox controls whose purposes are not obvious. Instead of Highlights and Shadows you get Exposure Bias and HDR. Instead of Luminance and Color noise reduction, you get sliders labeled Smoothness and Color Distortion. You really need to read the extensive documentation to learn how to use this program.
I found sliders could be sticky and not easy to adjust precisely. The MacOS version was slow, often presenting long bouts of spinning beachballs while it performed some function. This is a program worth a try, and you might find you like it. But considering what the competition offers, I would not recommend it.
While Topaz Labs previously offered only plug-ins for Photoshop and other programs (their Topaz DeNoise 6 is very good), their Topaz Studio stand-alone program now offers full raw processing abilities.
It is for Mac and Windows. While it did a decent job developing my test Milky Way image (above), with good color and contrast adjustments, it cannot copy and paste settings from one image to a folder of images, only to one other image. Nor can it batch export a folder of images. Both deficiencies make it useless for time-lapse work.
In addition, while the base program is free, adding the “Pro Adjustments” modules I needed to process my test image (Noise Reduction, Dehaze, Precision Contrast, etc.) would cost $160 – each Adjustment is bought separately. Some users might like it, but I wouldn’t recommend it.
And … Adobe Photoshop Elements v18 (late 2017 release)
What about Adobe’s own Photoshop “Lite?” Elements is available for $99 as a boxed or downloadable one-time purchase, but with annual updates costing about $50. While it offers image and adjustment layers, it cannot do much with 16-bit images, and has very limited functions for developing raw files.
And its Lightroom-like Organizer module does not have any copy-and-paste settings or batch export functions, making it unsuitable for time-lapse production.
Elements is for processing photos for the snapshot family album. Like Apple’s Photos and other free photo apps, I don’t consider Elements to be a serious option for nightscape and time-lapse work. But it can be pressed into service for raw editing and layering single images, especially by beginners.
However, a Creative Cloud Photo subscription doesn’t cost much more than buying, then upgrading Elements outright, yet gets you far, far more in professional-level software.
And Yet More…!
In addition, for just developing raw files, you likely already have software to do the job – the program that came with your camera.
For Canon it’s Digital Photo Professional (shown above); for Nikon it’s Capture NX; for Pentax it’s Digital Camera Utility, etc.
These are all capable raw developers, but have no layering capabilities. And they read only the files from their camera brand. If theirs is the only software you have, try it. They are great for learning on.
But you’ll find that the programs from other companies offer more features and better image quality.
What Would I Buy?
Except for Capture One, which I tested as a trial copy, I did buy all the software in question, for testing for my Nightscapes eBook.
However, as I’ve described, none of the programs tick all the boxes. Each has strengths, but also weaknesses, if not outright deficiencies. I don’t feel any can fully replace Adobe products for features and image quality.
A possible non-Adobe combination for the best image quality might be DxO PhotoLab for raw developing and basic time-lapse processing, and Affinity Photo for stacking and compositing still images, from finished TIFF files exported out of DxO and opened and layered with Affinity.
But that combo lacks any cataloging option. For that you’d have to add ACDSee or Aftershot for a budget option. It’s hardly a convenient workflow I’d want to use.
I’d love to recommend ON1 Photo RAW more highly as a single solution, if only it had better raw processing results, and didn’t suffer from de-Bayering artifacts (shown in a 400% close-up above, compared to DxO PhotoLab). These add the star haloes and a subtle blocky pattern to the sky, most obvious at right.
To Adobe or Not to Adobe
I’m just not anxious, as others are, to “avoid Adobe.”
I’ve been a satisfied Creative Cloud subscriber for several years, and view the monthly fee as the cost of doing business. It’s much cheaper than the annual updates that boxed Photoshop versions used to cost. Nor am I worried about Adobe suddenly jacking up the fees or holding us hostage with demands.
For me, the need to use LRTimelapse (shown above) for about 80 percent of all the time-lapse sequences I shoot means the question is settled. LRTimelapse works only with Adobe software, and the combination works great. Sold.
I feel Camera Raw/Lightroom produces results that others can only just match, if that.
Only DxO PhotoLab beat Adobe for its excellent contrast enhancements and PRIME noise reduction.
Yes, other programs certainly have some fine features I wish Camera Raw or Lightroom had, such as:
Hot and dead pixel removal
Dark frame subtraction and flat field division
Better options for contrast enhancement
And adding local adjustments to raw files via layers, with more precise masking tools
But those aren’t “must haves.”
Using ACR or Lightroom makes it easy to export raw files for time-lapse assembly, or to open them into Photoshop for layering and compositing, usually as “smart objects” for non-destructive editing, as shown below.
Above is the final layered image, consisting of:
A stack of 4 tracked exposures for the sky (the test image is one of those exposures)
And 4 untracked exposures for the ground.
The mean stacking smooths noise even more. The masking reveals just the sky on the tracked set. Every adjustment layer, mask, and “smart filter” is non-destructive and can be adjusted later.
I’ll work on recreating this same image with the three non-Adobe programs capable of doing so – Affinity, Luminar, and ON1 Photo RAW – to see how well they do. But that’s the topic of a future blog.
Making the Switch?
The issue with switching from Adobe to any new program is compatibility.
While making a switch will be fine when working on all new images, reading the terabytes of old images I have processed with Adobe software (and being able to re-adjust their raw settings and layered adjustments) will always require that Adobe software.
If you let your Creative Cloud subscription lapse, as I understand it the only thing that will continue to work is Lightroom’s Library module, allowing you to review images only. You can’t do anything to them.
None of the contender programs will read Adobe’s XMP metadata files to display raw images with Adobe’s settings intact.
Conversely, nor can Adobe read the proprietary files and metadata other programs create.
With final layered Photoshop files, while some programs can read .PSD files, they usually open them just as flattened images, as ON1 warns it will do above. It flattened all of the non-destructive editing elements created in Photoshop. Luminar did the same.
Only Affinity Photo (above) successfully read a complex and very large Photoshop .PSB file correctly, honouring at least its adjustment and image layers. So, if backwards compatibility with your legacy Photoshop images is important, choose Affinity Photo.
However, Affinity flattened Photoshop’s smart object image layers and their smart filters. Even Adobe’s own Photoshop Elements doesn’t honor smart objects.
Lest you think that’s a “walled garden” created by “evil Adobe,” keep in mind that the same will be true of the image formats and catalogs that all the contender programs produce.
To read the adjustments, layers, and “live filters” you create using any another program, you will need to use that program.
Will Affinity, DxO, Luminar, ON1, etc. be around in ten years?
Yes, you can save out flattened TIFFs that any program can read in the future, but that rules out using those other programs to re-work any of the image’s original settings.
I can see using DxO PhotoLab (above) or Raw Therapee for some specific images that benefit from their unique features.
Or using ACDSee as a handy image browser.
And ON1 and Luminar have some lovely effects that can be applied by calling them up as plug-ins from within Photoshop, and applied as smart filters. Above, I show Luminar working as a plug-in, applying its “Soft & Airy” filter.
In the case of Capture One and DxO PhotoLab, their ability to save images back as raw DNG files (the only contender programs of the bunch that can), means that any raw processing program in the future should be able to read the raw image.
However, only Capture One’s Export to DNG option produced a raw file readable and editable by Adobe Camera Raw with its settings from Capture One (mostly) intact (as shown above).
Even so, I won’t be switching away from Adobe any time soon.
But I hope my survey has given you useful information to judge whether you should make the switch. And if so, to what program.
I’m pleased to announce that after a year in production, our video tutorial series, Nightscapes and Time-Lapses: From Field to Photoshop, is now available.
It’s been quite a project! Over the last few years I’ve presented annual astrophoto workshops in conjunction with our local telescope dealer All-Star Telescope to great success.
However, we always had requests for the workshops on video. Attempts to video the actual workshops never produced satisfactory results. So we spent a year shooting in the field and in the studio to produce a “purpose-built” series of programs.
They are available now as a set of three programs, totalling 4 hours of instruction, for purchase and download at Vimeo at
For those wanting “hard copies” we will also be selling the programs on mailed USB sticks. See All-Star Telescope for info and prices. The downloaded version can also be ordered from there.
This series deals with the basics of capturing, then processing nightscape still images and time-lapse movies of the night sky and landscapes lit by moonlight and starlight.
Here’s the content outline:
Program 1 – Choosing Equipment (1 Hour)
• Tips for Getting Started • Essential Gear • Choosing A Camera • Photo 101 – Exposure Triangle • Setting Exposure • Expose to the Right • Setting a Camera – File Types • Photo 101 – Noise Sources • Setting a Camera – Noise Reduction • Setting a Camera – Focusing • Setting a Camera – Other Menus • Choosing Lenses • Choosing an IntervalometerSummary and Tips
Program 2 – Shooting in the Field (1 hour)
• Climbing the Learning Curve • Twilights • Astronomy 101 – Conjunctions • Shooting Conjunctions • Moonrises • Shooting Auroras • Astronomy 101 – Auroras • Photo 101 – Composing • Moonlit Nightscapes • Astronomy 101 – Where is the Moon? • Choosing a Location • Shooting the Milky Way • Astronomy 101 – Where is the Milky Way? • Astronomy 101 – Daily Sky Motion • Tracking the Sky • Shooting Star Trails • Shooting Time-Lapses • Calculating Time-Lapses • A Pre-Flight Checklist • Summary and Tips
Program 3 – Processing Nightscapes and Time-Lapses (2 hours)
• Workflows • Using Adobe Bridge – Importing and Selecting • Photo 101 – File Formats • Using Adobe Lightroom – Importing and Selecting • Adobe Camera Raw – Essential Settings • Adobe Camera Raw – Developing Raw Images • Adobe Lightroom – Develop Module • Adobe Photoshop – Introduction • Photoshop – Setup • Photoshop – Smart Filters • Photoshop – Adjustment Layers • Photoshop – Masking • Photoshop – Processing Star Trails & Time-Lapses • Stacking Star Trails • Assembling Time-Lapse Movies • Archiving • Summary & Finale
If this first introductory series is successful we may produce follow-up programs on more advanced techniques.
It was a great night for shooting meteors as the annual Perseids put on a show.
For the Perseid meteor shower I went to one of the darkest sites in Canada, Grasslands National Park in southern Saskatchewan, a dark sky preserve and home to several rare species requiring dark nights to flourish – similar to astronomers!
This year a boost in activity was predicted and the predictions seemed to hold true. The lead image records 33 meteors in a series of stacked 30-second exposures taken over an hour.
It shows only one area of sky, looking east toward the radiant point in the constellation Perseus – thus the name of the shower.
Extrapolating the count to the whole sky, I think it’s safe to say there would have been 100 or more meteors an hour zipping about, not bad for my latitude of 49° North.
The early part of the evening was lit by moonlight, which lent itself to some nice nightscapes scenes but fewer meteors.
But once the Moon set and the sky darkened the show really began. Competing with the meteors was some dim aurora, but also the brightest display of airglow I have even seen.
It was bright enough to be visible to the eye as grey bands, unusual. Airglow is normally sub-visual.
But the camera revealed the airglow bands as green, red, and yellow, from fluorescing oxygen and sodium atoms. The bands slowly rippled across the sky from south to north.
Airglow is something you can see only from dark sites. It is one of the wonders of the night sky, that can make a dark sky not dark!
The lead image is stack of 31 frames containing meteors (two frames had 2 meteors), shot from 1:13 am to 2:08 a.m. CST, so over 55 minutes. The camera was not tracking the sky but was on a fixed tripod. I choose one frame with the best visibility of the airglow as the base layer. For every other meteor layer, I used Free Transform to rotate each frame around a point far off frame at upper left, close to where the celestial pole would be and then nudged each frame to bring the stars into close alignment with the base layer, especially near the meteor being layered in.
This placed each meteor in its correct position in the sky in relation to the stars, essential for showing the effect of the radiant point accurately.
Each layer above the base sky layer is masked to show just the meteor and is blended with Lighten mode. If I had not manually aligned the sky for each frame, the meteors would have ended up positioned where they appeared in relation to the ground but the radiant point would have been smeared — the meteors would have been in the wrong place.
Unfortunately, it’s what I see in a lot of composited meteor shower shots.
It would have been much easier if I had had this camera on a tracker so all frames would have been aligned coming out of the camera. But the other camera was on the tracker! It took the other composite image, the one looking north.
The ground is a mean combined stack of 4 frames to smooth noise in the ground. Each frame is 30 seconds at f/2 with the wonderful Sigma 20mm Art lens and Nikon D750 at ISO 5000. The waxing Moon had set by the time this sequence started, leaving the sky dark and the airglow much more visible.
I present a horizon-to-zenith panorama of the pantheon of autumn constellations.
Yes, I know it’s winter, but as it gets dark each night now in early January the autumn stars are still front and centre. I took the opportunity during a run of very clear nights at home to shoot a panorama of the autumn sky.
It is a mosaic that sweeps up the sky and frames many related Greek mythological constellations:
• from the watery constellations of Aquarius, Pisces, and Cetus at the bottom near the horizon…
• to Pegasus and Aries in mid-frame…
• on up to Andromeda and Perseus at upper left…
• and finally Cassiopeia and Cepheus at the top of frame embedded in the Milky Way overhead. The Andromeda Galaxy, M31, is just above centre.
Here, I’ve labeled the participating constellations, though only a few, such as the “square” of Pegasus and the “W” of Cassiopeia, have readily identifiable patterns.
Most of these constellations are related in Greek mythology, with Princess Andromeda being the daughter of Queen Cassiopeia and King Cepheus, who was rescued from the jaws of Cetus the Sea Monster by Perseus the Hero, who rode on Pegasus the Winged Horse in some accounts.
Zodiacal Light brightens the sky at bottom right in Aquarius, and angles across the frame to the left.
I shot this from home on a very clear night January 2, 2016 with the Zodiacal Light plainly visible to the naked eye.
This is a mosaic of 5 panels, each a stack of 5 x 2 minute exposures, plus each panel having another stack of 2 x 2 minute exposures blended in, and taken through the Kenko Softon filter to add the fuzzy star glows to make the constellations stand out.
All were shot with the 24mm Canon lens at f/2.8 and Canon 5DMkII at ISO 1600. All tracked on the AP Mach One mount.
All stacking and stitching in Photoshop CC 2015. Final image size is 8500 x 5500 pixels and 3.6 gigabytes for the layered master.
In a sweeping panorama, here is the entire northern hemisphere Milky Way from horizon to horizon.
This is the result of one of the major projects on my recent trek to Arizona and New Mexico – a mosaic of images shot along the Milky Way over several hours.
The goal is a complete 360° panorama of the entire Milky Way, and I’ve got most of the other segments in previous shoots from Alberta, Australia and Chile. But I did not have good shots of the northern autumn segments, until now.
The panorama sweeps from Cygnus (at top, setting in the western sky in the evening), across the sky overhead in Perseus, Auriga and Taurus (in the middle), and down into Orion, Canis Major, and Puppis (at bottom, low in the southern sky at midnight).
The view is looking outward to the near edge of our Milky Way, in the direction opposite the centre of our Galaxy. In this direction the Milky Way becomes dimmer and less defined. Notable are the many red H-alpha emission regions along the Milky Way, as well as the many lanes of dark interstellar dust nearby and obscuring the more distant stars.
However, a diffuse glow in Taurus partly obscures its Taurus Dark Clouds — that’s the Gegenschein, caused by sunlight reflecting off cometary dust particles directly opposite the Sun and marking the anti-solar point this night, by coincidence then close to galactic longitude of 180° opposite the galactic centre.
Here I provide a guided map of the mosaic. Orion is at lower right, while the Pleiades and Andromeda Galaxy lie near the right edge. The Andromeda Galaxy is the only thing in this image that is not part of the Milky Way.
The bright star Canopus is just rising at bottom, in haze. Vega and Altair are just setting at the very top. So the panorama sweeps from Altair to Canopus.
The sky isn’t perfect! Haze and airglow in our atmosphere add discolouration, especially close to the horizon. In my final 360° pan, I’ll use only the central portions of this panorama.
Now let’s put the horizon-to-horizon panorama into cosmic perspective…
In this diagram, based on art from NASA’s Spitzer Space Telescope Institute, I show my Northern Milky Way Panorama in perspective to the “big picture” of our entire Galaxy, using artwork based on our best map of how our Galaxy is thought to look.
We are looking in a “god’s eye” view across our Galaxy from a vantage point on the far side of the Galaxy.
Where we are is marked with the red dot, the location of our average Sun in a minor spiral arm called the Orion Spur.
The diagram places my panorama image in the approximate correct location to show where its features are in our Galaxy. As such it illustrates how my panorama taken from Earth shows our view of the outer portions of our Galaxy, from the bright Cygnus area at right, to Perseus in the middle, directly opposite the centre of the Galaxy, then over to Orion at left.
The panorama sweeps from a “galactic longitude” of roughly 90° at right in Cygnus, to 180° in Perseus, over to 240° in Orion and Canis Major at left.
In the northern autumn and early winter seasons we are looking outward toward the outer Perseus Arm. So the Milky Way we see in our sky is fainter than in mid-summer when we are looking the other way, toward the dense centre of the Galaxy and the rich inner Norma and Sagittarius arms.
Yet, this outer region contains a rich array of star-forming regions, which mostly show up as the red nebulas. But this region of the Milky Way is also laced with dark lanes of interstellar “stardust.”
The panorama is composed of 14 segments, most being stacks 5 x 2.5-minute exposures with the filter-modified Canon 5D MkII at ISO 1600 and 35mm lens at f/2.8.
The end segments near the horizons at top and bottom are stacks of 2 x 2.5-minute exposures.
Each segment also has an additional image shot through a Kenko Softon filter to add the star glows, to make the bright stars show up better.
The camera was oriented with the long dimension of the frame across the Milky Way, not along it, to maximize the amount of sky framed on either side of the Milky Way.
The camera was on the iOptron Sky-Tracker. I shot the segments for this pan from Quailway Cottage, Arizona on December 8/9, 2015, with the end segments taken Dec 10/11, 2015. I decided to add in the horizon segments for completeness, and so shot those two nights later when sky conditions were a little different.