Two major eclipses of the Moon and a partial eclipse of the Sun over eastern North America highlight the astronomical year of 2021.
I provide my selection of three dozen of the best sky sights for 2021. I focus on events you can actually see, and from North America. I also emphasize events with the potential for good “photo ops.”
What I Don’t Include
Thus, I’m excluding minor meteor showers and ones that peak at Full Moon, and events that happen with the objects too close to the Sun.
I also don’t include events seen only from the eastern hemisphere, such as the April 17 occultation of Mars by the Moon — it isn’t even a close conjunction for us in North America. The August 15 rare triple transit of three Galilean moons at once on the disk of Jupiter occurs during daylight hours for western North America, rendering it very challenging to see. An outburst on August 31 of the normally quiet Aurigid meteor shower is predicted to happen over Asia, not North America.
I also don’t list the growing profusion of special or “supermoons” that get click-bait PR every year, choosing instead to limit my list to just the Harvest Moon of September as a notably photogenic Moon.
Good Year for Lunar Eclipses
But two Full Moons — in May and in November — do undergo eclipses that will be wonderful sights for the eye and camera. As a bonus, the Full Moon of May is the closest Full Moon of 2021, making it, yes, a “supermoon.”
The New Moon eclipses the Sun on June 10, bringing an annular eclipse to remote regions of northern Canada and the Arctic (including the North Pole!). Eastern North America and all of Europe can witness a partial solar eclipse this day.
For an authoritative annual guide to the sky and detailed reference work, see the Observer’s Handbook published each year in Canadian and U.S. editions by The Royal Astronomical Society of Canada. I used it to compile this list.
The RASC has also partnered with Firefly Books to publish a more popular-level guide to the coming year’s sky for North America, in the 2021 Night Sky Almanac, authored by Canadian science writer Nicole Mortillaro. It provides excellent monthly star charts.
However, feel free to print out my blog or save it as a PDF for your personal reference. To share my listing with others, please send them the link to this blog page. Thanks!
The year begins with a chance to see three planets together at dusk.
January 10 — Mercury, Jupiter and Saturn within 2 degrees (°)
Even three weeks after their much publicized Great Conjunction, Jupiter and Saturn are still close and visible low in the evening twilight. On January 10 Mercury joins them to form a neat triangle of worlds, but very low in the southwest. Clear skies and binoculars are a must!
NOTE: The red circle on this and most charts represents the 6.5° field of view of a typical 10×50 binocular. So you can see here how binoculars will frame the trio perfectly. All charts are courtesy the desktop app Starry Night™ bySimulation Curriculum.
January 14 — Thin waxing crescent Moon above line of Mercury, Jupiter and Saturn
Saturn disappears behind the Sun on January 23, followed by Jupiter on January 28, so early January is our last chance to see the evening trio of planets, tonight with the crescent Moon.
January 20 — Mars and Uranus 1.6° apart
Uranus will be easy to spot in binoculars as a magnitude 5.8 green star below red Mars, so this is your chance to find the seventh planet. The quarter Moon shines below the planet pair.
January 23 — Mercury at a favourable evening elongation
This and its appearance in May are the best opportunities for northern hemisphere observers to catch the innermost planet in the evening sky in 2021. Look for a bright magnitude -0.8 “star” in the dusk twilight.
This is a quiet month with Mars the main evening planet, but now quite small in the telescope.
February 18 — Waxing Moon 4° below Mars
The pairing appears near the Pleiades and Hyades star clusters high in the evening sky.
Mars shines high in evening sky in Taurus, while the three planets that were in the evening sky in January begin to emerge into the dawn sky.
March 1 — Zodiacal light “season” begins in the evening
From sites away from light pollution look for a faint glow of light rising out of the southwest sky on any clear evening for the next two weeks with no Moon.
March 3 — Mars 2.5° below the Pleiades
This will be a nice sight in binoculars tonight and tomorrow high in the evening sky, and a good target for tracked telephoto lens shots.
March 4 — Mercury and Jupiter just 1/2° apart
Close to be sure! But this pairing will be so low in the dawn sky it will be difficult to spot. They will appear equally close on March 5 should clouds intervene on March 4.
March 9 — Line of Mercury, Jupiter, Saturn and waning crescent Moon
Three planets and the waxing crescent Moon form a line across the dawn sky but again, very low in the southeast. The even thinner Moon will be below Jupiter on March 10. Observers at low latitudes (south of 35° N) will have the best view on these mornings.
March 20 — Equinox at 5:37 a.m. EDT
Spring officially begins for the northern hemisphere, autumn for the southern, as the Sun crosses the celestial equator heading north. Today, the Sun rises due east and sets due west for photo ops.
March 30 — Zodiacal light season again!
With the Moon out of the way, the faint zodiacal light can again be seen and photographed in the west over the next two weeks, but only from a site without significant light pollution on the western horizon.
The inner planets appear in the evening sky, while Mars meets M35.
April 6 — Milky Way arch season begins
With the waning Moon just getting out of view, this morning and for the next two weeks are good nights to shoot panoramas of the bright summer Milky Way as an arch across the sky, with the galactic core in view to the south. The moonless first two weeks of May, June and July will also work this year, but by August the Milky Way is reaching high overhead and so is difficult to capture in a horizontal landscape panorama.
April 24 — Mercury and Venus 1° apart
The two inner planets will be very low in the western evening sky tonight and tomorrow, but with clear skies this is a chance to catch both at once. Use a telephoto lens for the best image.
April 26 — Mars passes 1/2° north of M35 star cluster
This will be a fine scene for binoculars or a photo op for a tracked telephoto lens or telescope in a long enough exposure to reveal the rich star cluster Messier 35 in Gemini.
On May 26 a totally eclipsed Moon shines red in the west before sunrise for western North America.
May 12 — Venus and Moon 1.5° apart
Look low in the western evening sky this night for the pairing of the thin crescent Moon and Venus, and the next night, May 13, for the crescent Moon higher and 4° away from Mercury. These are good nights to capture both inner planets using a short telephoto lens.
May 16 — Mercury at a favourable evening elongation
With Mercury angled up high in the northwest this is the best week of the year to catch it in the evening sky from northern latitudes.
May 26 — Total Eclipse of the Moon
The first total lunar eclipse since January 20, 2019, this “TLE” can be seen as a total eclipse only from western North America, Hawaii, and from Australia and New Zealand. Totality lasts a brief 15 minutes, with the Moon in Scorpius not far from red Antares. The red Moon in a twilight sky will be beautiful, as it was for the April 4, 2015 eclipse at dawn over Monument Valley, Utah shown above.
Those in western North America will see the totally eclipsed Moon setting into the southwest in the dawn hour before sunrise, as depicted here. Over a suitable landscape this will be a photogenic scene, as even at mid-eclipse the Moon will be bright red because it passes so far from the centre of Earth’s umbral shadow.
Unfortunately, those in eastern North America will have to be content with a view of a partially eclipsed Moon setting in the morning twilight.
A bonus is that this is also the closest and largest Full Moon of 2021, with a close perigee of 357,311 kilometres occurring just 9 hours earlier. So the Full Moon that rises on the evening of May 25 will be the year’s “supermoon.”
See Fred Espenak’s EclipseWise.com page for details on timing and viewing regions. The dark region on this map does not see any of this eclipse.
May 26 — Comet 7/P Pons-Winnecke at perihelion
The brightest comet predicted to be visible in 2021 (as of this writing) is the short-period Comet Pons-Winnecke (aka Comet 7/P). It reaches its closest point to the Sun — perihelion — the night of the lunar eclipse and is well placed in Aquarius high in the southeastern dawn sky above Jupiter and Saturn.
But … it is expected to be only 8th magnitude, making it a binocular object at best, looking like a fuzzball, not the spectacular object depicted here in this exaggerated view of its brightness and tail length.
May 28 — Mercury and Venus less than 1/2° apart
Look low in the northwest evening sky for a very close conjunction of the two inner worlds. A telescope will frame them well, with Mercury a tiny crescent and Venus an almost fully illuminated disk.
While eastern North America misses the total lunar eclipse, two weeks later observers in the east do get to see a partial solar eclipse.
June 10 — Annular eclipse of the Sun
Should you manage to get yourself to the path of the Moon’s anti-umbral shadow you will see the dark disk of the Moon contained within the bright disk of the Sun but not large enough to cover the Sun completely. You see a ring of light, as above from a 1994 annular eclipse.
The Moon is near apogee, so its disk is about as small as it gets, in contrast to the perigee Moon two weeks earlier. During the maximum of 3 minutes 51 seconds of annularity the sky will get unusually dark, but none of the dramatic effects of a total eclipse will appear. The annulus of sunlight that remains is still so bright special solar filters must be used at all times, covering the eyes and lenses.
The region with the best accessibility to the path is northwestern Ontario north and east of Thunder Bay. However, the annular phase of the eclipse there occurs at or just after sunrise, so clouds are likely to obscure the view, as are trees!
The eastern seaboard of the U.S. and much of eastern Canada can see a partial eclipse of the Sun, as can most of Europe. For details of times and amount of eclipse see Fred Espenak’s EclipseWise website.
Summer officially begins for the northern hemisphere, winter for the southern, as the Sun reaches its most northerly position above the celestial equator. The Sun rises farthest to the northeast and sets farthest to the northwest, and the length of daylight is at its maximum.
June 22 — Mars passes through the Beehive star cluster
Mars, now at a modest magnitude +1.8, appears amid the Beehive star cluster, aka M44, tonight and tomorrow evening, but low in the northwest in the twilight sky. Use binoculars or a telescope for the best view.
Venus and Mars put on a show low in the western twilight.
July 2 — Venus passes through the Beehive star cluster
Venus (at a brilliant magnitude -3.9) follows Mars through the Beehive cluster this evening, but with the pairing even lower in the sky, making it tough to pick out the star cluster.
July 4 — Mercury at a good morning elongation
Though not at its best for a morning appearance from northern latitudes, Mercury should still be easy to spot and photograph in the pre-dawn sky in Taurus, outshining bright Aldebaran.
July 11 — Grouping of Venus, Mars and waxing crescent Moon
Look low in the evening sky for the line of the thin crescent Moon, bright Venus and dim Mars all in the same binocular field. Venus passes 1/2° above Mars on the next two nights, July 12 and 13.
July 21 — Grouping of Venus, Mars and Regulus
The two planets appear with bright Regulus in Leo, all within a binocular field, but again, low in the northwest twilight. The colour contrast of red Mars with white Venus and blue-white Regulus should be apparent in binoculars.
The popular Perseid meteors peak, and we can see (maybe!) the extremely close conjunction of Mercury and Mars.
August 1 — Milky Way core season opens
For southerly latitudes, the first two weeks of May and June are also good, but from the northern U.S. and much of Canada, the nights don’t get dark enough to see and shoot the bright galactic centre until August. The rich star clouds of Sagittarius now shine due south as it gets dark each night over the next two weeks.
August 2 — Saturn at opposition
Saturn is at its closest and brightest for 2021 tonight, rising at sunset and shining due south in Capricornus in the middle of the night.
August 12 — Perseid meteor shower peaks
The annual Perseid meteor shower peaks tonight with a waxing crescent Moon that sets early, to leave most of the night dark and ideal for watching meteors. Look for the crescent Moon 5° above Venus on August 10.
August 18 — Mars and Mercury only 0.06° apart!
Now this is a very close conjunction, with Mercury passing only 4 arc minutes from Mars (compared to the 6 arc minute separation of the Great Conjunction of Jupiter and Saturn on December 21, 2020). But the planets will be very low in the west at dusk and tough to sight. This will be a conjunction for skilled observers blessed with clear skies and a low horizon.
August 20 — Jupiter at opposition
Jupiter, now in Aquarius, reaches its closest and brightest for 2021 tonight, also rising at sunset and shining due south in the middle of the night. On the night of August 21/22, the Full Moon, also at opposition — as all Full Moons are — appears 4° below Jupiter, as shown above.
It’s Harvest Moon time, with this annual special Full Moon occurring close to the equinox this year for an ideal geometry, making the Moon rise due east.
September 5 — Zodiacal light “season” begins in the morning
With no Moon for the next two weeks, from sites away from light pollution look to the pre-dawn sky for a faint glow of light rising out of the east before twilight brightens the morning sky.
September 20 — Full “Harvest” Moon
Occurring two days before the equinox, this Full Moon will rise nearly due east (a little to the south of east) at sunset and set nearly due west at sunrise at dawn on September 21, for some fine photo ops.
September 22 — Equinox at 3:21 p.m. EDT
Autumn officially begins for the northern hemisphere, spring for the southern, as the Sun crosses the celestial equator heading south. Today, the Sun rises due east and sets due west for photo ops.
Mercury adorns the dawn while Venus shines bright but low at dusk.
October 4 — Zodiacal light “season” begins in the morning
With the Moon out of the way for the next two weeks, the zodiacal light will again be visible in the east in the pre-dawn hours.
October 9 — The Moon 2.5° from Venus
The crescent Moon passes close to Venus this evening, with the pair not far from the star Antares. The low altitude of the worlds lends itself to some fine photo ops. Look for a similar close conjunction on the evening of November 7.
October 25 — Mercury at its most favourable morning elongation
The high angle of the ecliptic — the path of the planets — on autumn dawns swings Mercury up as high as it can get in the morning sky, making this week the best for sighting Mercury as a “morning star” in 2021 from northern latitudes.
October 29 — Venus at its greatest angle away from the Sun
While now farthest from the Sun in our sky, its low altitude at this time of year makes this an unfavourable evening appearance of Venus.
The second lunar eclipse brings a mostly red Moon to the skies over North America.
November 3 — Moon and Mercury 2° apart, then a daylight occultation
Before dawn, with Mercury still well-placed in the morning sky, the waning crescent Moon shines 2° above the planet, with Mars below and the star Spica nearby. Later in the day, about noon to early afternoon (the time varies with your location), the Moon will occult (pass in front of) Mercury. This will be a challenging observation even with a telescope, with the pale and thin Moon only 14° east of the Sun. A very clear sky will be essential!
November 19 — 97% Partial Eclipse of the Moon
Though not a total eclipse, this is the next best thing: a 97% partial! And unlike the May 26 eclipse, all of North America gets to see this one.
Mid-eclipse, when the Moon is most deeply embedded in Earth’s umbral shadow, occurs at 4:04 a.m. EST (1:04 a.m. PST) on November 19. While not convenient timing, it ensures that all of the continent can see the entire 3.5-hour long eclipse. The partial umbral phase begins at 3:18 a.m EST (12:18 a.m. PST).
At mid-eclipse, the Moon will resemble Mars — a red world with a bright south “polar cap” caused by the small 3% of the southern edge of the Moon outside the umbra. Its position near the Pleiades and Hyades clusters will make for a great wide-field image.
Remember — this occurs on the night of November 18/19! So don’t miss it thinking the eclipse starts on the evening of November 19. You’ll be a day late!
The year ends with a chance to see four planets together at dusk.
December 4 — Total Eclipse of the Sun
I include this for completeness, but this total solar eclipse (TSE) could not be more remote, as the path of totality lies over Antarctica. Only the most intrepid will be there, in expedition ships and in aircraft. (I took this image over Antarctica at the November 23, 2003 total eclipse one 18-year Saros cycle before this year’s TSE.) Even the partial phases are visible only from southernmost Australia and Africa.
December 6 — Moon 2.5° below Venus
With Venus just past its official December 3 date of “greatest brilliancy” (at magnitude -4.7), the waxing crescent Moon appears close below it, with Saturn and Jupiter further along the line of the ecliptic in the southwest. The Moon appears below Saturn on December 7 and below Jupiter on December 8.
December 13 — Geminid meteor shower peaks
The most prolific meteor shower of the year peaks with a waxing 10-day-old gibbous Moon lighting the sky, so not great conditions. But with luck it will still be possible to see and capture bright fireballs.
December 21 — Solstice at 10:59 a.m. EST
Winter officially begins for the northern hemisphere, summer for the southern, as the Sun reaches its most southerly position below the celestial equator. The Sun rises farthest to the southeast and sets farthest to the southwest, and the length of daylight is at its minimum.
December 31 — Four planets in view
As the year ends the same three planets that adorned the evening sky in early January are back, with the addition of Venus. So on New Year’s Eve we can see four of the naked eye planets (only Mars is missing) at once in the evening sky.
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.
I had the chance to test out an early sample of Canon’s new EOS Ra camera designed for deep-sky photography.
Once every 7 years astrophotographers have reason to celebrate when Canon introduces one of their “a” cameras, astronomical variants optimized for deep-sky objects, notably red nebulas.
In 2005 Canon introduced the ground-breaking 8-megapixel 20Da, the first DLSR to feature Live View for focusing. Seven years later, in 2012, Canon released the 18-megapixel 60Da, a camera I still use and love.
Both cameras were cropped-frame DSLRs.
Now in 2019, seven years after the 60Da, we have the newly-released EOS Ra, the astrophoto version of the 30-megapixel EOS R released in late 2018. The EOS R is a full-frame mirrorless camera with a sensor similar to what’s in Canon’s 5D MkIV DSLR.
Here, I present a selection of sample images taken with the new EOS Ra.
Both versions of the EOS R have identical functions and menus.
The big difference is that the EOS Ra, as did Canon’s earlier “a” models, has a factory-installed filter in front of the sensor that transmits more of the deep red “hydrogen-alpha” wavelength emitted by glowing nebulas.
Normal cameras suppress much of this deep-red light as a by-product of their filters cutting out the infra-red light that digital sensors are very sensitive to, but that would not focus well.
I was sent an early sample of the EOS Ra, and earlier this autumn also had a sample of the stock EOS R.
Both were sent for testing so I could prepare a test report for Sky and Telescope magazine. The full test report will appear in an upcoming issue.
• How the Ra compares to previous “a” models and third-party filter-modified cameras
• How the Ra works for normal daylight photography
• Noise levels compared to other cameras
• Features unique to the EOS Ra, such as 30x Live View focusing
UPDATE — November 25, 2019
As part of further testing I shot the Heart and Soul Nebulas in Cassiopeia through my little Borg 77mm f/4 astrograph with both the EOS Ra and my filter-modified 5D MkII (modified years ago by AstroHutech) to compare which pulled in more nebulosity. It looked like a draw.
Both images are single 8-minute exposures, taken minutes apart and developed identically in Adobe Camera Raw, but adjusted for colour balance to equally neutralize the sky background. The histograms look similar. Even so, the Ra looks a little redder overall. But keep in mind a sky or nebula can be made to appear any shade of red you like in processing.
The question is which camera shows more faint nebulosity?
The modified 5D MkII has always been my favourite camera for this type of astrophotography, picking up more nebulosity than other “a” models I’ve tested, including the Nikon D810a.
But in this case, I’d say the EOS Ra is performing as well as, if not better than the 5D MkII. How well any third-party modified camera you buy now performs will depend which, if any, filter the modifier installs in front of the sensor. So your mileage will vary.
For most of my other testing I shot through my much-prized Astro-Physics Traveler, a 105mm aperture f/6 apochromatic refractor on the Astro-Physics Mach1 mount.
To connect the EOS Ra (with its new RF lens mount) to my existing telescope-to-camera adapter and field flattener lens I used one of Canon’s EF-EOS R lens adapters.
The bottom line is that the EOS Ra works great!
It performs very well on H-alpha-rich nebulas and has very low noise. It will be well-suited to not only deep-sky photography but also to wide-field nightscape and time-lapse photography, perhaps as Canon’s best camera yet for those applications.
WHAT ABOUT THE PRICE?
The EOS Ra will sell for $2,500 US, a $700 premium over the cost of the stock EOS R. Some complain. Of course, if you don’t like it, you don’t have to buy it. This is not an upgrade being forced upon you.
As I look at it, it is all relative. When Nikon’s astronomy DSLR, the 36 Mp D810a, came out in 2015 it sold for $3,800 US, $1,300 more than the EOS Ra. It was, and remains a fine camera, if you can find one. It is discontinued.
A 36 Mp cooled and dedicated CMOS astro camera, the QHY367, with the same chip as the D810a, goes for $4,400, $1,900 more than the Ra. Yes, it will produce better images I’m sure than the EOS Ra, but deep-sky imaging is all it can do. At a cost, in dollars and ease of use.
And yes, buying a stock EOS R and having it modified by a third party costs less, and you’ll certainly get a good camera, for $300 to $400 less than an Ra. But …
• The EOS Ra has a factory adjusted white balance for ease of “normal” use — no need to buy correction filters. So there’s a $$ saving there, even if you can find clip-in correction filters for the EOS R — you can’t.
• And the Ra retains the sensor dust cleaning function. Camera modifier companies remove it or charge more to reinstall it.
• And the 30x live view magnification is very nice.
• The EOS Ra also carries a full factory warranty.
Do I wish the EOS Ra had some other key features? Sure. A mode to turn all menus red would be nice. As would an intervalometer built-in, one that works with the Bulb Timer to allow sequences of programmed multi-minute exposures. Both could be added in with a firmware update.
And providing a basic EF-EOS R lens adapter in the price would be a welcome plus, as one is essential to use the EOS Ra on a telescope.
That’s my take on it. I’ll be buying one. But then again I bought the 20Da, twice!, and the 60Da, and I hate to think what I paid for those much less capable cameras.
BONUS TEST — The RF 15-35mm L Lens
Canon is also releasing an impressive series of top-class RF lenses for their R mirrorless cameras. The image below is an example astrophoto with the new RF 15-35mm f/2.8 L zoom lens, an ideal combination of focal lengths and speed for nightscape shooting.
Below is a further set of stacked and processed images with the RF 15-35mm L lens, taken in quick succession, at 15mm, 24mm, and 35mm focal lengths, all shot wide open at f/2.8. The EOS Ra was on the Star Adventurer tracker (as below) to follow the stars.
Click or tap on the images below to view a full-resolution version for closer inspection.
The RF 15-35mm lens performs extremely well at 15mm exhibiting very little off-axis aberrations at the corners.
Off-axis aberrations do increase at the longer focal lengths but are still very well controlled, and are much less than I’ve seen on my older zoom and prime lenses in this focal length range.
The RF 15-35mm is a great complement to the EOS Ra for wide-field Milky Way images.
I was impressed with the new EOS Ra. It performs superbly for astrophotography.
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!
I put the new Nikon Z6 mirrorless camera through its paces for astrophotography.
Following Sony’s lead, in late 2018 both Nikon and Canon released their entries to the full-frame mirrorless camera market.
Here I review one of Nikon’s new mirrorless models, the Z6, tested solely with astrophotography in mind. I did not test any of the auto-exposure, auto-focus, image stabilization, nor rapid-fire continuous mode features.
• Current owners of Nikon cropped-frame cameras wanting to upgrade to full-frame would do well to consider a Z6 over any current Nikon DSLR.
• Anyone wanting a full-frame camera for astrophotography and happy to “go Nikon” will find the Z6 nearly perfect for their needs.
Nikon Z6 vs. Z7
I opted to test the Z6 over the more expensive Z7, as the 24-megapixel Z6 has 6-micron pixels resulting in lower noise (according to independent tests) than the 46 megapixel Z7 with its 4.4 micron pixels.
In astrophotography, I feel low noise is critical, with 24-megapixel cameras hitting a sweet spot of noise vs. resolution.
However, if the higher resolution of the Z7 is important for your daytime photography needs, then I’m sure it will work well at night. The Nikon D850 DSLR, with a sensor similar to the Z7, has been proven by others to be a good astrophotography camera, albeit with higher noise than the lesser megapixel Nikons such as the D750 and Z6.
NOTE: Tap or click on images to download and display them full screen for closer inspection.
High ISO Noise
To test noise in a real-world situation, I shot a dark nightscape scene with the three cameras, using a 24mm Sigma Art lens on the two Nikons, and a 24mm Canon lens on the Sony via a MetaBones adapter. I shot at ISOs from 800 to 12,800, typical of what we use in nightscapes and deep-sky images.
The comparison set above shows performance at the higher ISOs of 3200 to 12,800. I saw very little difference among the trio, with the Nikon Z6 very similar to the Sony a7III, and with the four-year-old Nikon D750 holding up very well against the two new cameras.
The comparison below shows the three cameras on another night and at ISO 3200.
Both the Nikon Z6 and Sony a7III use a backside illuminated or “BSI” sensor, which in theory is promises to provide lower noise than a conventional CMOS sensor used in an older camera such as the D750.
In practice I didn’t see a marked difference, certainly not as much as the one- or even 1/2-stop improvement in noise I might have expected or hoped for.
Nevertheless, the Nikon Z6 provides as low a noise level as you’ll find in a camera offering 24 megapixels, and will perform very well for all forms of astrophotography.
Nikon and Sony both employ an “ISO-invariant” signal flow in their sensor design. You can purposely underexpose by shooting at a lower ISO, then boost the exposure later “in post” and end up with a result similar to an image shot at a high ISO to begin with in the camera.
I find this feature proves its worth when shooting Milky Way nightscapes that often have well-exposed skies but dark foregrounds lit only by starlight. Boosting the brightness of the landscape when developing the raw files reveals details in the scene without unduly introducing noise, banding, or other artifacts such as magenta tints.
That’s not true of “ISO variant” sensors, such as in most Canon cameras. Such sensors are far less tolerant of underexposure and are prone to noise, banding, and discolouration in the brightened shadows.
To test the Z6’s ISO invariance (as shown above) I shot a dark nightscape at ISO 3200 for a properly exposed scene, and also at ISO 100 for an image underexposed by a massive 5 stops. I then boosted that image by 5 stops in exposure in Adobe Camera Raw. That’s an extreme case to be sure.
I found the Z6 provided very good ISO invariant performance, though with more chrominance specking than the Sony a7III and Nikon D750 at -5 EV.
Below is a less severe test, showing the Z6 properly exposed on a moonlit night and at 1 to 4 EV steps underexposed, then brightened in processing. Even the -4 EV image looks very good.
In my testing, even with frames underexposed by -5 EV, I did not see any of the banding effects (due to the phase-detect auto-focus pixels) reported by others.
As such, I judge the Z6 to be an excellent camera for nightscape shooting when we often want to extract detail in the shadows or dark foregrounds.
Compressed vs. Uncompressed / Raw Large vs. Small
The Z6, as do many Nikons, offers a choice of shooting 12-bit or 14-bit raws, and either compressed or uncompressed.
I shot all my test images as 14-bit uncompressed raws, yielding 46 megabyte files with a resolution of 6048 x 4024 pixels. So I cannot comment on how good 12-bit compressed files are compared to what I shot. Astrophotography demands the best original data.
However, as the menu above shows, Nikon now also offers the option of shooting smaller raw sizes. The Medium Raw setting produces an image 4528 x 3016 pixels and a 18 megabyte file (in the files I shot), but with all the benefits of raw files in processing.
The Medium Raw option might be attractive when shooting time-lapses, where you might need to fit as many frames onto the single XQD card as possible, yet still have images large enough for final 4K movies.
However, comparing a Large Raw to a Medium Raw did show a loss of resolution, as expected, with little gain in noise reduction.
This is not like “binning pixels” in CCD cameras to increase signal-to-noise ratio. I prefer to never throw away information in the camera, to allow the option of creating the best quality still images from time-lapse frames later.
Nevertheless, it’s nice to see Nikon now offer this option on new models, a feature which has long been on Canon cameras.
Star Image Quality
Above is the Orion Nebula with the D750 and with the Z6, both shot in moonlight with the same 105mm refractor telescope.
I did not find any evidence for “star-eating” that Sony mirrorless cameras have been accused of. (However, I did not find the Sony a7III guilty of eating stars either.) Star images looked as good in the Z6 as in the D750.
Raw developers (Adobe, DxO, ON1, and others) decoded the Z6’s Bayer-array NEF files fine, with no artifacts such as oddly-coloured or misshapen stars, which can arise in cameras lacking an anti-alias filter.
LENR Dark frames
Above, 8-minute exposures of nothing, taken with the lens cap on at room temperature: without LENR, and with LENR, both boosted a lot in brightness and contrast to exaggerate the visibility of any thermal noise. These show the reduction in noise speckling with LENR activated, and the clean result with the Z6. At small size you’ll likely see nothing but black!
For deep-sky imaging a common practice is to shoot “dark frames,” images recording just the thermal noise that can then be subtracted from the image.
The Long Exposure Noise Reduction feature offered by all cameras performs this dark frame subtraction internally and automatically by the camera for any exposures over one second long.
I tested the Z6’s LENR and found it worked well, doing the job to effectively reduce thermal noise (hot pixels) without adding any other artifacts.
Some astrophotographers dismiss LENR and never use it. By contrast, I prefer to use LENR to do dark frame subtraction. Why? Through many comparison tests over the years I have found that separate dark frames taken later at night rarely do as good a job as LENR darks, because those separate darks are taken when the sensor temperature, and therefore the noise levels, are different than they were for the “light” frames.
I’ve found that dark frames taken later, then subtracted “in post” inevitably show less or little effect compared to images taken with LENR darks. Or worse, they add a myriad of pock-mark black specks to the image, adding noise and making the image look worse.
The benefit of LENR is lower noise. The penalty of LENR is that each image takes twice as long to shoot — the length of the exposure + the length of the dark frame. Because …
As Expected on the Z6 … There’s no LENR Dark Frame Buffer
Only Canon full-frame cameras offer this little known but wonderful feature for astrophotography. Turn on LENR and it is possible to shoot three (with the Canon 6D MkII) or four (with the Canon 6D) raw images in quick succession even with LENR turned on. The Canon 5D series also has this feature.
The single dark frame kicks in and locks up the camera only after the series of “light frames” are taken. This is excellent for taking a set of noise-reduced deep-sky images for later stacking without need for further “image calibration.”
No Nikon has this dark frame buffer, not even the “astronomical” D810a. And not the Z6.
I have to mention this every time I describe Canon’s dark frame buffer: It works only on full-frame Canons, and there’s no menu function to activate it. Just turn on LENR, fire the shutter, and when the first exposure is complete fire the shutter again. Then again for a third, and perhaps a fourth exposure. Only then does the LENR dark frame lock up the camera as “Busy” and prevent more exposures. That single dark frame gets applied to each of the previous “light” frames, greatly reducing the time it takes to shoot a set of dark-frame subtracted images.
But do note that Canon’s dark frame buffer will not work if…:
a) You leave Live View on. Don’t do that for any long exposure shooting.
b) You control the camera through the USB port via external software. It works only when controlling the camera via its internal intervalometer or via the shutter port using a hardware intervalometer.
With DSLRs deep-sky images shot through telescopes, then boosted for contrast in processing, usually exhibit a darkening along the bottom of the frame. This is caused by the upraised mirror shadowing the sensor slightly, an effect never noticed in normal photography.
Mirrorless cameras should be free of this mirror box shadowing. The Sony a7III, however, still exhibits some edge shadows due to an odd metal mask in front of the sensor. It shouldn’t be there and its edge darkening is a pain to eliminate in the final processing.
As I show in my review of the a7III, the Sony also exhibits a purple edge glow in long-exposure deep-sky images, from an internal light source. That’s a serious detriment to its use in deep-sky imaging.
Happily, the Z6 proved to be free of any such artifacts. Images are clean and evenly illuminated to the edges, as they should be. I saw no amp glows or other oddities that can show up under astrophotography use. The Z6 can produce superb deep-sky images.
During my short test period, I was not able to shoot red nebulas under moonless conditions. So I can’t say how well the Z6 performs for recording H-alpha regions compared to other “stock” cameras.
With the D810a gone, if it is deep red nebulosity you are after with a Nikon, then consider buying a filter-modified Z6 or having yours modified.
Both LifePixel and Spencer’s Camera offer to modify the Z6 and Z7 models. However, I have not used either of their services, so cannot vouch for them first hand.
Live View Focusing and Framing
For all astrophotography manually focusing with Live View is essential. And with mirrorless cameras there is no optical viewfinder to look through to frame scenes. You are dependent on the live electronic image (on the rear LCD screen or in the eye-level electronic viewfinder, or EVF) for seeing anything.
Thankfully, the Z6 presents a bright Live View image making it easy to frame, find, and focus on stars. Maximum zoom for precise focusing is 15x, good but not as good as the D750’s 20x zoom level, but better than Canon’s 10x maximum zoom in Live View.
The Z6 lacks the a7III’s wonderful Bright Monitoring function that temporarily ups the ISO to an extreme level, making it much easier to frame a dark night scene. However, something similar can be achieved with the Z6 by switching it temporarily to Movie mode, and having the ISO set to an extreme level.
As with most Nikons (and unlike Sonys), the Z6 remembers separate settings for the still and movie modes, making it easy to switch back and forth, in this case for a temporarily brightened Live View image to aid framing.
That’s very handy, and the Z6 works better than the D750 in this regard, providing a brighter Live View image, even with the D750’s well-hidden Exposure Preview option turned on.
Where the Z6 pulls far ahead of the otherwise similar D750 is in its movie features.
The Z6 can shoot 4K video (3840 x 2160 pixels) at either 30, 25, or 24 frames per second. Using 24 frames per second and increasing the ISO to between 12,800 to 51,200 (the Z6 can go as high as ISO 204,800!) it is possible to shoot real-time video at night, such as of auroras.
But the auroras will have to be bright, as at 24 fps, the maximum shutter speed is 1/25-second, as you might expect.
The a7III, by comparison, can shoot 4K movies at “dragged” shutter speeds as slow as 1/4 second, even at 24 fps, making it possible to shoot auroras at lower and less noisy ISO speeds, albeit with some image jerkiness due to the longer exposures per frame.
The D750 shoots only 1080 HD and, as shown above, produces very noisy movies at ISO 25,600 to 51,200. It’s barely usable for aurora videos.
The Z6 is much cleaner than the D750 at those high ISOs, no doubt due to far better internal processing of the movie frames. However, if night-sky 4K videos are an important goal, a camera from the Sony a7 series will be a better choice, if only because of the option for slower dragged shutter speeds.
For examples of real-time auroras shot with the Sony a7III see my music videos shot in Yellowknife and in Norway.
The Z6 uses the EN-EL15b battery compatible with the battery and charger used for the D750. But the “b” variant allows for in-camera charging via the USB port.
In room temperature tests the Z6 lasted for 1500 exposures, as many as the D750 was able to take in a side-by-side test. That was with the screens off.
At night, in winter temperatures of -10 degrees C (14° F), the Z6 lasted for three hours worth of continuous shooting, both for long deep-sky exposure sets and for a test time-lapse I shot, shown below.
A time-lapse movie, downsized here to HD from the full-size originals, shot with the Z6 and its internal intervalometer, from twilight through to moonrise on a winter night. Processed with Camera Raw and LRTimelapse.
However, with any mirrorless camera, you can extend battery life by minimizing use of the LCD screen and eye-level EVF. The Z6 has a handy and dedicated button for shutting off those screens when they aren’t needed during a shoot.
The days of mirrorless cameras needing a handful of batteries just to get through a few hours of shooting are gone.
Lens and Telescope Compatibility
As with all mirrorless cameras, the Nikon Z cameras use a new lens mount, one that is incompatible with the decades-old Nikon F mount.
The Z mount is wider and can accommodate wider-angle and faster lenses than the old F mount ever could, and in a smaller package. While we have yet to see those lenses appear, in theory that’s the good news.
The bad news is that you’ll need Nikon’s FTZ lens adapter to use any of your existing Nikon F-mount lenses on either the Z6 or Z7. As of this writing, Nikon is supplying an FTZ free with every Z body purchase.
I got an FTZ with my loaner Z6 and it worked very well, allowing even third-party lenses like my Sigma Art lenses to focus at the same point as they normally do (not true of some thIrd-party adapters), preserving the lens’s optical performance. Autofocus functions all worked fine and fast.
You’ll also need the FTZ adapter for use on a telescope, as shown above, to go from your telescope’s camera adapter, with its existing Nikon T-ring, to the Z6 body.
The reason is that the field flattener or coma corrector lenses often required with telescopes are designed to work best with the longer lens-to-sensor distance of a DSLR body. The FTZ adapter provides the necessary spacing, as do third-party adapters.
The only drawback to the FTZ is that any tripod plate attached to the camera body itself likely has to come off, and the tripod foot incorporated into the FTZ used instead. I found myself often having to swap locations for the tripod plate, an inconvenience.
Camera Controller Compatibility
Since it uses the same Nikon-type DC2 shutter port as the D750, the Z6 it should be compatible with most remote hardware releases and time-lapse motion controllers that operate a Nikon through the shutter port. An example are the controllers from SYRP.
On the other hand, time-lapse devices and external intervalometers that run Nikons through the USB port might need to have their firmware or apps updated to work with the Z6.
For example, as of early May 2019, CamRanger lists the Z6 as a supported camera; the Arsenal “smart controller” does not. Nor does Alpine Labs for their Radian and Pulse controllers, nor TimeLapse+ for its excellent View bramping intervalometer. Check with your supplier.
For those who like to use laptops to run their camera at the telescope, I found the Windows program Astro Photography Tool (v3.63) worked fine with the Z6, in this case connecting to the camera’s USB-C port using the USB-C to USB-A cable that comes with the camera. This allows APT to shift not only shutter speed, but also ISO and aperture under scripted sequences.
Inevitably, raw files from brand new cameras cannot be read by any raw developer programs other than the one supplied by the manufacturer, Nikon Capture NX in this case. However, even by the time I did my testing in winter 2019 all the major software suppliers had updated their programs to open Z6 files.
Adobe Lightroom and Photoshop, Affinity Photo, DxO PhotoLab, Luminar 3, ON1 PhotoRAW, and the open-source Raw Therapee all open the Z6’s NEF raw files just fine.
Specialized programs for processing astronomy images might be another story. For example, as of v1.08.06, PixInsight, a favourite program among astrophotographers, does not open Z6 raw files. Nor does Nebulosity v4. But check with the developers for updates.
Other Features for Astrophotography
Here are other Nikon Z6 features I found of value for astrophotography, and for operating the camera at night.
Tilting LCD Screen
Like the Nikon D750 and Sony A7III, the Z6 offers a tilting LCD screen great for use on a telescope or tripod when aimed up at the sky. However, the screen does not flip out and reverse, a feature useful for vloggers, but seldom needed for astrophotography.
OLED Top Screen (Above)
The Sony doesn’t have one, and Canon’s low-cost mirrorless Rp also lacks one. But the top-mounted OLED screen of the Z6 is a great convenience for astrophotography. It makes it possible to monitor camera status and battery life during a shoot, even with the rear LCD screen turned off to prolong battery life.
Sony’s implementation of touch-screen functions is limited to just choosing autofocus points. By contrast, the Nikon Z6 offers a full range of touchscreen functions, making it easy to navigate menus and choose settings.
I do wish there was an option, as there is with Pentax, to tint the menus red for preserving night vision.
As with other Nikons, the Z6 offers an internal intervalometer capable of shooting time-lapses, just as long as individual exposures don’t need to be longer than 30 seconds.
In addition, there’s the Exposure Smoothing option which, as I have found with the D750, is great for smoothing flickering in time-lapses shot using auto exposure.
Sony has only just added an intervalometer to the a7III with their v3 firmware update, but with no exposure smoothing.
Custom i Menu / Custom Function Buttons
The Sony a7III has four custom function buttons users can assign to commonly used commands, for quick access. For example, I assign one Custom button to the Bright Monitoring function which is otherwise utterly hidden in the menus, but superb for framing nightscapes, if only you know it’s there!
The Nikon Z6 has two custom buttons beside the lens mount. However, I found it easier to use the “i” menu (shown above) by populating it with those functions I use at night for astrophotography. It’s then easy to call them up and adjust them on the touch screen.
Thankfully, the Z6’s dedicated ISO button is now on top of the camera, making it much easier to find at night than the awkwardly placed ISO button on the back of the D750, which I am always mistaking for the Image Quality button, which you do not want to adjust by mistake.
As most cameras do, the Z6 also has a “My Menu” page which you can also populate with favourite menu commands.
Lighter Weight / Smaller Size
The Z6 provides similar imaging performance, if not better (for movies) than the D750, and in a smaller and lighter camera, weighing 200 grams (0.44 pounds) less than the D750. Being able to downsize my equipment mass is a welcome plus to going mirrorless.
Electronic Front Curtain Shutter / Silent Shooting
By design, mirrorless cameras lack any vibration from a bouncing mirror. But even the mechanical shutter can impart vibration and blurring to high-magnification images taken through telescopes.
The electronic front curtain shutter (lacking in the D750) helps eliminate this, while the Silent Shooting mode does just that — it makes the Z6 utterly quiet and vibration free when shooting, as all the shutter functions are now electronic. This is great for lunar and planetary imaging.
What’s Missing for Astrophotography (not much!)
Bulb Timer for Long Exposures
While the Z6 has a Bulb setting, there is no Bulb Timer as there is with Canon’s recent cameras. A Bulb Timer would allow setting long Bulb exposures of any length in the camera, though Canon’s cannot be combined with the intervalometer.
Instead, the Nikon must be used with an external Intervalometer for any exposures over 30 seconds long. Any number of units are compatible with the Z6, through its shutter port which is the same type DC2 jack used in the D750.
In-Camera Image Stacking to Raws
The Z6 does offer the ability to stack up to 10 images in the camera, a feature also offered by Canon and Pentax. Images can be blended with a Lighten (for star trails) or Average (for noise smoothing) mode.
However, unlike with Canon and Pentax, the result is a compressed JPG not a raw file, making this feature of little value for serious imaging. Plus with a maximum of only 10 exposures of up to 30-seconds each, the ability to stack star trails “in camera” is limited.
Unlike the top-end D850, the Z6’s buttons are not illuminated, but then again neither are the Z7’s.
As a bonus — the Nikon 35mm S-Series Lens
With the Z6 I also received a Nikkor 35mm f/1.8 S lens made for the Z-mount, as the lens perhaps best suited for nightscape imaging out of the native Z-mount lenses from Nikon. See Nikon’s website for the listing.
If there’s a downside to the Z-series Nikons it’s the limited number of native lenses that are available now from Nikon, and likely in the future from anyone, due to Nikon not making it easy for other lens companies to design for the new Z mount.
In testing the 35mm Nikkor on tracked shots, stars showed excellent on- and off-axis image quality, even wide open at f/1.8. Coma, astigmatism, spherical aberration, and lateral chromatic aberration were all well controlled.
However, as with most lenses now offered for mirrorless cameras, the focus is “by-wire” using a ring that doesn’t mechanically adjust the focus. As a result, the focus ring turns continuously and lacks a focus scale.
So it is not possible to manually preset the lens to an infinity mark, as nightscape photographers often like to do. Focusing must be done each night.
Until there is a greater selection of native lenses for the Z cameras, astrophotographers will need to use the FTZ adapter and their existing Nikon F-mount or third-party Nikon-mount lenses with the Zs.
I was impressed with the Z6.
For any owner of a Nikon cropped-frame DSLR (from the 3000, 5000, or 7000 series for example) wanting to upgrade to full-frame for astrophotography I would suggest moving to the Z6 over choosing a current DSLR.
Mirrorless is the way of the future. And the Z6 will yield lower noise than most, if not all, of Nikon’s cropped-frame cameras.
For owners of current Nikon DSLRs, especially a 24-megapixel camera such as the D750, moving to a Z6 will not provide a significant improvement in image quality for still images.
But … it will provide 4K video and much better low-light video performance than older DSLRs. So if it is aurora videos you are after, the Z6 will work well, though not quite as well as a Sony alpha.
In all, there’s little downside to the Z6 for astrophotography, and some significant advantages: low noise, bright live view, clean artifact-free sensor images, touchscreen convenience, silent shooting, low-light 4K video, all in a lighter weight body than most full-frame DSLRs.
But what about lenses for the Sony? Here’s one ideal for astrophotography.
Made for Sony e-mount cameras, the Venus Optics 15mm f/2 Laowa provides excellent on- and off-axis performance in a fast and compact lens ideal for nightscape, time-lapse, and wide-field tracked astrophotography with Sony mirrorless cameras. (UPDATE: Venus Optics has announced versions of this lens for Canon R and Nikon Z mount mirrorless cameras.)
I use it a lot and highly recommend it.
Size and Weight
While I often use the a7III with my Canon lenses by way of a Metabones adapter, the Sony really comes into its own when matched to a “native” lens made for the Sony e-mount. The selection of fast, wide lenses from Sony itself is limited, with the new Sony 24mm G-Master a popular favourite (I have yet to try it).
However, for much of my nightscape shooting, and certainly for auroras, I prefer lenses even wider than 24mm, and the faster the better.
Aurora over Båtsfjord, Norway. This is a single 0.8-second exposure at f/2 with the 15mm Venus Optics lens and Sony a7III at ISO 1600.
The Laowa 15mm f/2 from Venus Optics fills the bill very nicely, providing excellent speed in a compact lens. While wide, the Laowa is a rectilinear lens providing straight horizons even when aimed up, as shown above. This is not a fish-eye lens.
The Venus Optics 15mm realizes the potential of mirrorless cameras and their short flange distance that allows the design of fast, wide lenses without massive bulk.
While compact, at 600 grams the Laowa 15mm is quite hefty for its size due to its solid metal construction. Nevertheless, it is half the weight of the massive 1250-gram Sigma 14mm f/1.8 Art. The Laowa is not a plastic entry-level lens, nor is it cheap, at $850 from U.S. sources.
For me, the Sony-Laowa combination is my first choice for a lightweight travel camera for overseas aurora trips
However, this is a no-frills manual focus lens. Nor does it even transfer aperture data to the camera, which is a pity. There are no electrical connections between the lens and camera.
However, for nightscape work where all settings are adjusted manually, the Venus Optics 15mm works just fine. The key factor is how good are the optics. I’m happy to report that they are very good indeed.
Testing Under the Stars
To test the Venus Optics lens I shot “same night” images, all tracked, with the Sigma 14mm f/1.8 Art lens, at left, and the Rokinon 14mm SP (labeled as being f/2.4, at right). Both are much larger lenses, made for DSLRs, with bulbous front elements not able to accept filters. But they are both superb lenses. See my test report on these lenses published in 2018.
The next images show blow-ups of the same scene (the nightscape shown in full below, taken at Dinosaur Provincial Park, Alberta), and all taken on a tracker.
I used the Rokinon on the Sony a7III using the Metabones adapter which, unlike some brands of lens adapters, does not compromise the optical quality of the lens by shifting its focal position. But lacking a lens adapter for Nikon-to-Sony at the time of testing, I used the Nikon-mount Sigma lens on a Nikon D750, a DSLR camera with nearly identical sensor specs to the Sony.
Above is a tracked image (so the stars are not trailed, which would make it hard to tell aberrations from trails), taken wide open at f/2. No lens correction has been applied so the vignetting (the darkening of the frame corners) is as the lens provides.
As shown above, when used wide open at f/2 vignetting is significant, but not much more so than with competitive lenses with much larger lenses, as I compare below.
And the vignetting is correctable in processing. Adobe Camera Raw and Lightroom have this lens in their lens profile database. That’s not the case with current versions (as of April 2019) of other raw developers such as DxO PhotoLab, ON1 Photo RAW, and Raw Therapee where vignetting corrections have to be dialled in manually by eye.
When stopped down to f/2.8 the Laowa “flattens” out a lot for vignetting and uniformity of frame illumination. Corner aberrations also improve but are still present. I show those in close-up detail below.
Above, I compare the vignetting of the three lenses, both wide open and when stopped down. Wide open, all the lenses, even the Sigma and Rokinon despite their large front elements, show quite a bit of drop off in illumination at the corners.
The Rokinon SP actually seems to be the worst of the trio, showing some residual vignetting even at f/2.8, while it is reduced significantly in the Laowa and Sigma lenses. Oddly, the Rokinon SP, even though it is labeled as f/2.4, seemed to open to f/2.2, at least as indicated by the aperture metadata.
Above I show lens sharpness on-axis, both wide open and stopped down, to check for spherical and chromatic aberrations with the bright blue star Vega centered. The red box in the Navigator window at top right indicates what portion of the frame I am showing, at 200% magnification in Photoshop.
On-axis, the Venus Optics 15mm shows stars just as sharply as the premium Sigma and Rokinon lenses, with no sign of blurring spherical aberration nor coloured haloes from chromatic aberration.
Focusing is precise and easy to achieve with the Sony on Live View. My unit reaches sharpest focus on stars with the lens set just shy of the middle of the infinity symbol. This is consistent and allows me to preset focus just by dialing the focus ring, handy for shooting auroras at -35° C, when I prefer to minimize fussing with camera settings, thank you very much!
The Laowa and Sigma lenses show similar levels of off-axis coma and astigmatism, with the Laowa exhibiting slightly more lateral chromatic aberration than the Sigma. Both improve a lot when stopped down one stop, but aberrations are still present though to a lesser degree.
However, I find that the Laowa 15mm performs as well as the Sigma 14mm Art for star quality on- and off-axis. And that’s a high standard to match.
The Rokinon SP is the worst of the trio, showing significant elongation of off-axis star images (they look like lines aimed at the frame centre), likely due to astigmatism. With the 14mm SP, this aberration was still present at f/2.8, and was worse at the upper right corner than at the upper left corner, an indication to me that even the premium Rokinon SP lens exhibits slight lens de-centering, an issue users have often found with other Rokinon lenses.
Real-World Examples – The Milky Way
The fast speed of the Laowa 15mm is ideal for shooting tracked wide-field images of the Milky Way, and untracked camera-on-tripod nightscapes and time-lapses of the Milky Way.
Image aberrations are very acceptable at f/2, a speed that allows shutter speed and ISO to be kept lower for minimal star trailing and noise while ensuring a well-exposed frame.
Real World Examples – Auroras
Where the Laowa 15mm really shines is for auroras. On my trips to chase the Northern Lights I often take nothing but the Sony-Laowa pair, to keep weight and size down.
Above is an example, taken from a moving ship off the coast of Norway. The fast f/2 speed (I wish it were even faster!) makes it possible to capture the Lights in only 1- or 2-second exposures, albeit at ISO 6400. But the fast shutter speed is needed for minimizing ship movement.
The Sony also excels at real-time 4K video, able to shoot at ISO 12,800 to 51,200 without excessive noise.
Aurora Reflections from Alan Dyer on Vimeo.
The Sky is Dancing from Alan Dyer on Vimeo.
The Northern Lights At Sea from Alan Dyer on Vimeo.
Click through to see the posts and the videos shot with the Venus Optics 15mm.
As an aid to video use, the aperture ring of the Venus Optics 15mm can be “de-clicked” at the flick of a switch, allowing users to smoothly adjust the iris during shooting, avoiding audible clicks and jumps in brightness. That’s a very nice feature indeed.
In all, I can recommend the Venus Optics Laowa 15mm lens as a great match to Sony mirrorless cameras, for nightscape still and video shooting. UPDATE: Versions for Canon R and Nikon Z mount mirrorless cameras will now be available.
Can the new version of ON1 Photo RAW match Photoshop for astrophotography?
The short TL;DR answer: No.
But … as always, it depends. So do read on.
Released in mid-November 2018, the latest version of ON1 Photo RAW greatly improves a non-destructive workflow. Combining Browsing, Cataloging, Raw Developing, with newly improved Layers capabilities, ON1 is out to compete with Adobe’s Creative Cloud photo suite – Lightroom, Camera Raw, Bridge, and Photoshop – for those looking for a non-subscription alternative.
Many reviewers love the new ON1 – for “normal” photography.
But can it replace Adobe for night sky photos? I put ON1 Photo RAW 2019 through its paces for the demanding tasks of processing nightscapes, time-lapses, and deep-sky astrophotos.
In my eBook “How to Photograph and Process Nightscapes and Time-Lapses” (linked to at right) I present dozens of processing tutorials, including several on how to use ON1 Photo RAW, but the 2018 edition. I was critical of many aspects of the old version, primarily of its destructive workflow when going from its Develop and Effects modules to the limited Layers module of the 2018 edition.
I’m glad to see many of the shortfalls have been addressed, with the 2019 edition offering a much better workflow allowing layering of raw images while maintaining access to all the original raw settings and adjustments. You no longer have to flatten and commit to image settings to layer them for composites. When working with Layers you are no longer locked out of key functions such as cropping.
I won’t detail all the changes to ON1 2019 but they are significant and welcome.
The question I had was: Are they enough for high-quality astrophotos in a non-destructive workflow, Adobe Photoshop’s forté.
While ON1 Photo RAW 2019 is much better, I concluded it still isn’t a full replacement of Adobe’s Creative Cloud suite, as least not for astrophotography.
NOTE: All images can be downloaded as high-res versions for closer inspection.
ON1 2019 is Better, But for Astrophotography …
Functions in Layers are still limited. For example, there is no stacking and averaging for noise smoothing. Affinity Photo has those.
Filters, though abundant for artistic special effect “looks,” are limited in basic but essential functions. There is no Median filter, for one.
Despite a proliferation of contrast controls, for deep-sky images (nebulas and galaxies) I was still not able to achieve the quality of images I’ve been used to with Photoshop.
The lack of support for third-party plug-ins means ON1 cannot work with essential time-lapse programs such as Timelapse Workflow or LRTimelapse.
Nightscapes: ON1 Photo RAW 2019 works acceptably well for nightscape still images:
Its improved layering and excellent masking functions are great for blending separate ground and sky images, or for applying masked adjustments to selected areas.
Time-Lapses: ON1 works is just adequate for basic time-lapse processing:
Yes, you can develop one image and apply its settings to hundreds of images in a set, then export them for assembly into a movie. But there is no way to vary those settings over time, as you can by mating Lightroom to LRTimelapse.
As with the 2018 edition, you still cannot copy and paste masked local adjustments from image to image, limiting their use.
Exporting those images is slow.
Deep-Sky: ON1 is not a program I can recommend for deep-sky image processing:
Stars inevitably end up with unsightly sharpening haloes.
De-Bayering artifacts add blocky textures to the sky background.
And all the contrast controls still don’t provide the “snap” and quality I’m used to with Photoshop when working with low-contrast subjects.
Library / Browse Functions
ON1 is sold first and foremost as a replacement for Adobe Lightroom, and to that extent it can work well. Unlike Lightroom, ON1 allows browsing and working on images without having to import them formally into a catalog.
However, you can create a catalog if you wish, one that can be viewed even if the original images are not “on-line.” The mystery seems to be where ON1 puts its catalog file on your hard drive. I was not able to find it, to manually back it up. Other programs, such as Lightroom and Capture One, locate their catalogs out in the open in the Pictures folder.
For those really wanting a divorce from Adobe, ON1 now offers an intelligent AI-based function for importing Lightroom catalogs and transferring all your Lightroom settings you’ve applied to raw files to ON1’s equivalent controls.
However, while ON1 can read Photoshop PSD files, it will flatten them, so you would lose access to all the original image layers.
ON1’s Browse module is good, with many of the same functions as Lightroom, such as “smart collections.” Affinity Photo – perhaps ON1’s closest competitor as a Photoshop replacement – still lacks anything like it.
But I found ON1’s Browse module buggy, often taking a long while to allow access into a folder, presumably while it is rendering image previews.
There are no plug-ins or extensions for exporting directly to or synching to social media and photo sharing sites.
ON1 did a fairly good job. Some of its special effect filters, such a Dynamic Contrast, Glow, and Sunshine, can help bring out the Milky Way, though do add an artistic “look” to an image which you might or might not like.
Below, I compare Adobe Camera Raw (ACR) to ON1. It was tough to get ON1’s image looking the same as ACR’s result, but then again, perhaps that’s not the point. Does it just look good? Yes, it does.
Compared to Adobe Camera Raw, which has a good array of basic settings, ON1 has most of those and more, in the form of many special Effects, with many combined as one-click Presets, as shown below.
A few presets and individual filters – the aforementioned Dynamic Contrast and Glow – are valuable. However, most of ON1’s filters and presets will not be useful for astrophotography, unless you are after highly artistic and unnatural effects.
Noise Reduction and Lens Correction
Critical to all astrophotography is excellent noise reduction. ON1 does a fine job here, with good smoothing of noise without harming details.
Lens Correction works OK. It detected the 20mm Sigma art lens and automatically applied distortion correction, but not any vignetting (light “fall-off”) correction, perhaps the most important correction in nightscape work. You have to dial this in manually by eye, a major deficiency.
By comparison, ACR applies both distortion and vignetting correction automatically. It also includes settings for many manual lenses that you can select and apply in a click. For example, ACR (and Lightroom) includes settings for popular Rokinon and Venus Optics manual lenses; ON1 does not.
Hot Pixel Removal
I shot the example image on a warm summer night and without using in-camera Long Exposure Noise Reduction (to keep the gap between exposures short when shooting sets of tracked and untracked exposures for later compositing).
However, the penalty for not using LENR to expedite the image taking is a ground filled with hot pixels. While Adobe Camera Raw does have some level of hot pixel removal working “under the hood,” many specks remained.
ON1 showed more hot pixels, until you clicked Remove Hot Pixels, found under Details. As shown at centre above, it did a decent job getting rid of the worst offenders.
But as I’ll show later, the penalty is that stars now look distorted and sometimes double, or you get the outright removal of stars. ON1 doesn’t do a good job distinguishing between true sharp-edged hot pixels and the softer images of stars. Indeed, it tends to over sharpen stars.
A competitor, Capture One 11, does a better job, with an adjustable Single Pixel removal slider, so you can at least select the level of star loss you are willing to tolerate to get rid of hot pixels.
Star Image Quality
Yes, we are pixel peeping here, but that’s what we do in astrophotography. A lot!
Stars in ON1 don’t look as good as in Camera Raw. Inevitably, as you add contrast enhancements, stars in ON1 start to exhibit dark and unsightly “sharpening haloes” not present in ACR, despite me applying similar levels of sharpening and contrast boosts to each version of the image.
Camera Raw has been accused of producing images that are not as sharp as with other programs such as Capture One and ON1.
There’s a reason. Other programs over-sharpen, and it shows here.
We can get away with it here in wide-field images, but not later with deep-sky close-ups. I don’t like it. And it is unavoidable. The haloes are there, albeit at a low level, even with no sharpening or contrast enhancements applied, and no matter what image profile is selected (I used ON1 Standard throughout).
You might have to download and closely inspect these images to see the effect, but ON1’s de-Bayering routine exhibits a cross-hatched blocky pattern at the pixel-peeping level. ACR does not.
I see this same effect with some other raw developers. For example, the free Raw Therapee shows it with many of its choices for de-Bayering algorithms, but not all. Of the more than a dozen raw developers I tested a year ago, ACR and DxO PhotoLab had (and still have) the most artifact-free de-Bayering and smoothest noise reduction
Again, we can get away with some pixel-level artifacts here, but not later, in deep-sky processing.
Nightscape Processing — Layering and Compositing
The 2018 version of ON1 forced you to destructively flatten images when bringing them into the Layers module.
The 2019 version of ON1 improves that. It is now possible to composite several raw files into one image and still retain all the original Develop and Effects settings for non-destructive work.
You can then use a range of masking tools to mask in or out the sky.
For the example above, I have stacked tracked and untracked exposures, and am starting to mask out the trailed stars from the untracked exposure layer.
To do this with Adobe, you would have to open the developed raw files in Photoshop (ideally using “smart objects” to retain the link back to the raw files). But with ON1 we stay within the same program, to retain access to non-destructive settings. Very nice!
To add masks, ON1 2019 does not have the equivalent of Photoshop’s excellent Quick Selection Tool for selecting the sky or ground. It does have a “Perfect Brush” option which uses the tonal value of the pixels below it, rather than detecting edges, to avoid “painting over the lines.”
While the Perfect Brush does a decent job, it still requires a lot of hand painting to create an accurate mask without holes and defects. There is no non-destructive “Select and Mask” refinement option as in Photoshop.
Yes, ON1’s Refine Brush and Chisel Mask tools can help clean up a mask edge but are destructive to the mask. That’s not acceptable to my non-destructive mindset!
The masking tools are also applicable to adding “Local Adjustments” to any image layer, to brighten or darken regions of an image for example.
These work well and I find them more intuitive than the “pins” ACR uses on raw files, or DxO PhotoLab’s quirky “U-Point” interface.
ON1’s Local Adjustments work more like Photoshop’s Adjustment Layers and are similarly non-destructive. Excellent.
A very powerful feature of ON1 is its built-in Luminosity masking.
Yes, Camera Raw now has Range Masks, and Photoshop can be used to create luminosity masks, but making Photoshop’s luminosity masks easily adjustable requires purchasing third-party extension panels.
ON1 can create an adjustable and non-destructive luminosity mask on any image or adjustment layer with a click.
While such masks, based on the brightness of areas, aren’t so useful for low-contrast images like the Milky Way scene above, they can be very powerful for merging high-contrast images (though ON1 also has an HDR function not tested here).
ON1 has the advantage here. Its Luminosity masks are a great feature for compositing exposures or for working on regions of bright and dark in an image.
Here again is the final result, above.
It is not just one image each for the sky and ground, but is instead a stack of four images for each half of the composite, to smooth noise. This form of stacking is somewhat unique to astrophotography, and is commonly used to reduce noise in nightscapes and in deep-sky images, as shown later.
Here I show how you have to stack images in ON1.
Unlike Photoshop and Affinity Photo, ON1 does not have the ability to merge images automatically into a stack and apply a mathematical averaging to the stack, usually a Mean or Median stack mode. The averaging of the image content is what reduces the random noise.
Instead, with ON1 you have perform an “old school” method of average stacking – by changing the opacity of the layers, so that Layer 2 = 50%, Layer 3 = 33%, Layer 4 = 25%, and so on. The result is identical to performing a Mean stack mode in Photoshop or Affinity.
Fine, except there is no way to perform a Median stack, which can be helpful for eliminating odd elements present in only one frame, perhaps an aircraft trail.
Copy and Paste Settings
Before we even get to the stacking stage, we have to develop and process all the images in a set. Unlike Lightroom or Camera Raw, ON1 can’t develop and synchronize settings to a set of images at once. You can work on only one image at a time.
So, you work on one image (one of the sky images here), then Copy and Paste its settings to the other images in the set. I show the Paste dialog box here.
This works OK, though I did find some bugs – the masks for some global Effects layers did not copy properly; they copied inverted, as black instead of white masks.
However, Luminosity masks did copy from image to image, which is surprising considering the next point.
The greater limitation is that no Local Adjustments (ones with masks to paint in a correction to a selected area) copy from one image to another … except ones with gradient masks. Why the restriction?
So as wonderful as ON1’s masking tools might be, they aren’t of any use if you want to copy their masked adjustments across several images, or, as shown next, to a large time-lapse set.
While Camera Raw’s and Lightroom’s Local Adjustment pins are more awkward to work with, they do copy across as many images as you like.
A few Adobe competitors, such as Affinity Photo (as of this writing) simply can’t do this.
By comparison, with the exception of Local Adjustments, ON1 does have good functions for Copying and Pasting Settings. These are essential for processing a set of hundreds of time-lapse frames.
Once all the images are processed – whether it be with ON1 or any other program – the frames have to exported out to an intermediate set of JPGs for assembly into a movie by third-party software. ON1 itself can’t assemble movies, but then again neither can Lightroom (as least not very well), though Photoshop can, through its video editing functions.
For my test set of 220 frames, each with several masked Effects layers, ON1 took 2 hours and 40 minutes to perform the export to 4K JPGs. Photoshop, through its Image Processor utility, took 1 hour and 30 minutes to export the same set, developed similarly and with several local adjustment pins.
ON1 did the job but was slow.
A greater limitation is that, unlike Lightroom, ON1 does not accept any third party plug-ins (it serves as a plug-in for other programs). That means ON1 is not compatible with what I feel are essential programs for advanced time-lapse processing: either Timelapse Workflow (from https://www.timelapseworkflow.com) or the industry-standard LRTimelapse (from https://lrtimelapse.com).
Both programs work with Lightroom to perform incremental adjustments to settings over a set of images, based on the settings of several keyframes.
Lacking the ability to work with these programs means ON1 is not a program for serious and professional time-lapse processing.
Wide-Angle Milky Way
Now we come to the most demanding task: processing long exposures of the deep-sky, such as wide-angle Milky Way shots and close-ups of nebulas and galaxies taken through telescopes. All require applying generous levels of contrast enhancement.
As the above example shows, try as I might, I could not get my test image of the Milky Way to look as good with ON1 as it did with Adobe Camera Raw. Despite the many ways to increase contrast in ON1 (Contrast, Midtones, Curves, Structure, Haze, Dynamic Contrast and more!), the result still looked flat and with more prominent sky gradients than with ACR.
And remember, with ACR that’s just the start of a processing workflow. You can then take the developed raw file into Photoshop for even more precise work.
With ON1, its effects and filters all you have to work with. Yes, that simplifies the workflow, but its choices are more limited than with Photoshop, despite ON1’s huge number of Presets.
Similarly, taking a popular deep-sky subject, the Andromeda Galaxy, aka M31, and processing the same original images with ON1 and ACR/Photoshop resulted in what I think is a better-looking result with Photoshop.
Of course, it’s possible to change the look of such highly processed images with the application of various Curves and masked adjustment layers. And I’m more expert with Photoshop than with ON1.
But … as with the Cygnus Milky Way image, I just couldn’t get Andromeda looking as good in ON1. It always looked a little flat.
Dynamic Contrast did help snap up the galaxy’s dark lanes, but at the cost of “crunchy” stars, as I show next. A luminosity “star mask” might help protect the stars, but I think the background sky will inevitably suffer from the de-Bayering artifacts.
Star and Background Sky Image Quality
As I showed with the nightscape image, stars in ON1 end up looking too “crunchy,” with dark halos from over sharpening, and also with the blocky de-Bayering artifacts now showing up in the sky.
I feel it is not possible to avoid dark star haloes, as any application of contrast enhancements, so essential for these types of objects, brings them out, even if you back off sharpening at the raw development stage, or apply star masks.
ON1 is applying too much sharpening “under the hood.” That might “wow” casual daytime photographers into thinking ON1 is making their photos look better, but it is detrimental to deep-sky images. Star haloes are a sign of poor processing.
Noise and Hot Pixels
ON1’s noise reduction is quite good, and by itself does little harm to image details.
But turn on the Remove Hot Pixel button and stars start to be eaten. Faint stars fade out and brighter stars get distorted into double shapes or have holes in them.
Hot pixel removal is a nice option to have, but for these types of images it does too much harm to be useful. Use LENR or take dark frames, best practices in any case.
Image Alignment and Registration
Before any processing of deep-sky images is possible, it is first necessary to stack and align them, to make up for slight shifts from image to image, usually due to the mount not being perfectly polar aligned. Such shifts can be both translational (left-right, up-down) and rotational (turning about the guide star).
New to ON1 2019 is an Auto-Align Layers function. It worked OK but not nearly as well as Photoshop’s routine. In my test images of M31, ON1 didn’t perform enough rotation.
Once stacked and aligned, and as I showed above, you then have to manually change the opacities of each layer to blend them for noise smoothing.
By comparison, Photoshop has a wonderful Statistics script (under File>Scripts) that will automatically stack, align, then mean or median average the images, and turn the result into a non-destructive smart object, all in one fell swoop. I use it all the time for deep-sky images. There’s no need for separate programs such as Deep-Sky Stacker.
In ON1, however, all that has to be done manually, step-by-step. ON1 does do the job, just not as well.
ON1 Photo RAW 2019 is a major improvement, primarily in providing a more seamless and less destructive workflow.
Think of it as Lightroom with Layers!
But it isn’t Photoshop.
True to ON1’s heritage as a special effect plug-in, it has some fine Effect filters, such as Dynamic Contrast above, ones I sometimes use from within Photoshop as plug-in smart filters.
Under Sharpen, ON1 does offer a High Pass option, a popular method for sharpening deep-sky objects.
Missing Filters and Adjustments
But for astrophoto use, ON1 is missing a lot of basic but essential filters for pixel-level touch-ups. Here’s a short list:
• Missing are Median, Dust & Scratches, Radial Blur, Shake Reduction, and Smart Sharpen, just to mention a handful of filters I find useful for astrophotography, among the dozens of others Photoshop has, but ON1 does not. But then again, neither does Lightroom, another example of how ON1 is more light Lightroom with layers and not Photoshop.
• While ON1 has many basic adjustments for color and contrast, its version of Photoshop’s Selective Color lacks Neutral or Black sliders, great for making fine changes to color balance in astrophotos.
• While there is a Curves panel, it has no equivalent to Photoshop’s “Targeted Adjustment Tool” for clicking on a region of an image to automatically add an inflection point at the right spot on the curve. This is immensely useful for deep-sky images.
• Also lacking is a basic Levels adjustment. I can live without it, but most astrophotographers would find this a deal-breaker.
• On the other hand, hard-core deep-sky photographers who do most of their processing in specialized programs such as PixInsight, using Photoshop or Lightroom only to perform final touch-ups, might find ON1 perfectly fine. Try it!
Saving and Exporting
ON1 saves its layered images as proprietary .onphoto files and does so automatically. There is no Save command, only a final Export command. As such it is possible to make changes you then decide you don’t like … but too late! The image has already been saved, writing over your earlier good version. Nor can you Save As … a file name of your choice. Annoying!
Opening a layered .onphoto file (even with ON1 itself already open) can take a minute or more for it to render and become editable.
Once you are happy with an image, you can Export the final .onphoto version as a layered .PSD file but the masks ON1 exports to the Photoshop layers may not match the ones you had back in ON1 for opacity. So the exported .PSD file doesn’t look like what you were working on. That’s a bug.
Only exporting a flattened TIFF file gets you a result that matches your ON1 file, but it is now flattened.
Bugs and Cost
I encountered a number of other bugs, ones bad enough to lock up ON1 now and then. I’ve even seen ON1’s own gurus encounter bugs with masking during their live tutorials. These will no doubt get fixed in 2019.x upgrades over the next few months.
But by late 2019 we will no doubt be offered ON1 Photo RAW 2020 for another $80 upgrade fee, over the original $100 to $120 purchase price. True, there’s no subscription, but ON1 still costs a modest annual fee, presuming you want the latest features.
Now, I have absolutely no problem with that, and ON1 2019 is a significant improvement.
However, I found that for astrophotography it still isn’t there yet as a complete replacement for Adobe.
I put the new Sony a7III mirrorless camera through its paces for the features and functions we need to shoot the night sky.
Sony’s a7III camera has enjoyed rave reviews since its introduction earlier in 2018. Most tests focus on its superb auto exposure and auto focus capabilities that rival much more costly cameras, including Sony’s own a7rIII and a9.
For astrophotography, none of those auto functions are of any value. We shoot everything on manual. Indeed, the ease of manually focusing in Live View is a key function.
In my testing I compared the Sony a7III to two competitive DSLRs, the Canon 6D MkII and Nikon D750.
All three are “entry-level” full-frame cameras, with 24 to 26 megapixels and in a similar price league of $1,500 (Nikon) to 2,000 (Sony).
I tested a Sony a7III purchased locally. It was not supplied to me by Sony in return for an “influential” blog post.
I did this testing in preparation for the new third edition of my Nightscapes and Time-Lapse eBook, which includes information on Sony mirrorless cameras, as well as many, many other updates and additions!
NOTE:Click or Tap on most images to bring them up full-frame for inspection.
Mirrorless vs. DSLR
As with Sony’s other popular Alpha 7 and 9 series cameras, the new Alpha 7III is a full-frame mirrorless camera, a class of camera Canon and Nikon have yet to offer, though models are rumoured or promised.
In the meantime, Sony commands the full-frame mirrorless market.
As its name implies, a mirrorless camera lacks the reflex mirror of a digital single lens reflex camera that, in a DSLR, provides the light path for framing the scene though the optical viewfinder.
In a mirrorless, the camera remains in “live view” all the time, with the sensor always feeding a live image to either or both the rear LCD screen and electronic viewfinder (EVF). While you can look through and frame using the EVF as you would with a DSLR, you are looking at an electronic image from the sensor, not an optical image from the lens.
The advantage of purely electronic viewing is that the image you are previewing matches the image you’ll capture, at least for short exposures. The disadvantage is that full-time live view draws more power, with mirrorless cameras notorious for being battery hungry.
Other mirrorless advantages include:
Compact size and lighter weight, yet offering all the image quality of a full-frame DSLR.
The thinner body allows the use of lenses from any manufacturer, albeit requiring the right adapter, an additional expense.
Lenses developed natively for mirrorless models can be smaller and lighter. An example is the Laowa 15mm f/2 I used for some of the testing.
The design lends itself to video shooting, with many mirrorless cameras offering 4K as standard, while often in DSLRs only high-end models do.
More rapid-fire burst modes and quieter shutters are a plus for action and wedding photographers, though they are of limited value for astrophotography.
Points of Comparison
In testing the Sony a7III I ignored all the auto functions. Instead, I concentrated on those points I felt of most concern to astrophotographers, such as:
Effectiveness of Long Exposure Noise Reduction (LENR)
Quality of Raw files, such as sharpness of stars
Brightness of Live View for framing and focusing
Uniformity of sensor illumination
Compatibility for time-lapse imaging
Levels of luminance and chrominance noise were excellent and similar to – but surprisingly not better than – the Nikon D750.
The Star Eater is effectively gone. Stars are not smoothed out in long exposures.
The Sony exhibited good – though not great – “ISO invariant” performance.
Dark frame subtraction using Long Exposure Noise Reduction removed most – but not all – hot pixels from thermal noise.
Live View Focusing and Framing
Live View was absolutely superb, though the outstanding Bright Monitoring function is as well-hidden as Sony could possibly make it.
Sensor Illumination Uniformity
The Sony showed some slight edge-of-frame shadowing from the mask in front of the sensor, as well as a weak purple amp glow.
• The a7III lacks any internal intervalometer or ability to add one via an app. But it is compatible with many external intervalometers and controllers.
• The a7III’s red sensitivity for recording H-Alpha-emitting nebulas was poor.
• It lacks the “light-frame” buffer offered by full-frame Canons that allows shooting several frames in quick succession even with LENR turned on.
The a7III offers 4K video and, at 24 frames-per-second, is full-frame. Shutter speeds can be as slow as 1/4-second, allowing real-time aurora shooting at reasonable ISO speeds.
Shooting typical 400-frame time-lapses used about 40% of the battery capacity, similar to the other DSLRs.
The Sony a7III is a superb camera for still and time-lapse nightscape shooting, and excellent for real-time aurora videos. It is good, though not great, for long-exposure deep-sky imaging.
The Sony a7III uses a sensor that is “Backside Illuminated,” a feature that promises to improve low-light performance and reduce noise.
I saw no great benefit from the BSI sensor. Noise at typical astrophoto ISO speeds – 800 to 6400 – were about equal to the four-year-old Nikon D750.
That was a bit surprising. I expected the new BSI-equipped Sony to better the Nikon by about a stop. It did not. This emphasizes just how good the Nikon D750 is.
Nevertheless, noise performance of the Sony a7III was still excellent, with both the Sony and Nikon handily outperforming the Canon 6D MkII, with its slightly smaller pixels, by about a stop in noise levels.
NOTE: I performed all Raw developing with Adobe Camera Raw v10.3. It is possible some of the artifacts I saw are due to ACR not handling the a7III’s .ARW files as well as it should. But to develop all the images from Sony, Nikon, and Canon equally for comparisons, ACR is the best choice.
Both the Sony and Nikon use sensor and signal path designs that are “ISO invariant.” As a result, images shot underexposed at slower ISOs, then boosted in exposure later in processing look identical to properly exposed high-ISO images. Well, almost.
The Sony still showed some discoloration artifacts and added noise when boosting images by +4 EV that the Nikon did not. Even with uncompressed Raws, the Sony was not quite as ISO invariant as the Nikon, though the difference shows up only under extreme push-processing of badly underexposed frames.
Plus, the Sony was far better than the Canon 6D MkII’s “ISO variant” sensor. Canon really needs to improve their sensors to keep in the game.
Compressed vs. Uncompressed
The Sony a7III offers a choice of shooting Uncompressed or Compressed Raw files. Uncompressed Raws are 47 Mb in size; Compressed Raws are 24 Mb.
In well-exposed images, I saw little difference in image quality.
But the dark shadows in underexposed nightscapes withstood shadow recovery better in the uncompressed files. Compressed files showed more noise and magenta discoloration in the shadows.
It is not clear if Sony’s compressed Raws are 12-bit vs. 14-bit for uncompressed files.
Nevertheless, for the demands of nightscape and deep-sky shooting and processing, I suggest shooting Uncompressed Raws. Use Compressed only if you plan to take lots of time-lapse frames and need to conserve memory card space on extended shoots.
Star Eater (Updated March 27, 2021)
Over the last year or so, firmware updates from Sony introduced a much-publicized penchant for Sony Alphas to “eat” stars even in Raw files, apparently due to an internal noise reduction or anti-aliasing routine users could not turn off. Stars were smoothed away along with the noise in exposures longer than 3.2 seconds in some Sony cameras (longer than 30 seconds in others).
I feel that in the a7III the Star Eater has been largely vanquished.
While others beg to differ and claim this camera still eats stars, they offer no evidence of it other than graphs and charts, not A-B photos of actual tracked starfields taken with the Sony vs. another camera thought not to eat stars.
As the images below show, there is a very slight one-pixel-level softening that kicks in at 4 seconds and longer but it did not eat or wipe out stars. Stars are visible to the same limiting magnitude and close double stars are just as well resolved across all exposures. Indeed, at slower ISOs and longer exposures, more stars are visible.
I saw none of the extreme effects reported by others with other Sonys, where masses of faint stars disappeared or turned into multi-colored blotches. It is possible the effect is still present in other Sony Alpha models. I have not tested those.
But in the a7III, I did not see any significant “star eating” in any long exposures even up to the 4 minutes I used for some deep-sky shots. In images taken at the same time with other cameras not accused of star eating, the Sony showed just as many faint stars as the competitors. Stars were visible to just as faint a limiting magnitude, and that’s what counts, NOT graphs and charts, especially when such results are not shown for other cameras.
In short, long exposures showed just as many stars as did short exposures.
This was true whether I was shooting compressed or uncompressed Raws, with or without Long Exposure Noise Reduction. Neither compression nor LENR invoked “star eating.”
LENR Dark frames
For elimination of hot pixels from thermal noise I prefer to use Long Exposure Noise Reduction when possible for nightscape and deep-sky images, especially on warm summer nights.
Exceptions are images taken for star trail stacking and for time-lapses, images that must be taken in quick succession, with minimal time gap between frames.
Turning on LENR did eliminate most hot pixels in long exposures, but not all. A few remained. Also, when boosting the exposure a lot in processing, the images taken with LENR on showed more shot and read noise than non-LENR frames.
The dark frame the camera was taking and subtracting was actually adding some noise, perhaps due to a temperature difference. The cause is not clear.
Sony advises that when using LENR Raw images are recorded with only 12-bit depth, not 14-bit. This might be a contributing factor. Yet frames taken with LENR on were the same 47 Mb size as normal uncompressed frames.
For those who think this is normal for LENR use, the Nikon D750 shows nothing like this – frames taken with LENR on are free of all hot pixels and do not show more shot or read noise, nor deterioration of shadow detail from lower bit depths.
However, I emphasize that the noise increase from using LENR with the Sony was visible only when severely boosting underexposed images in processing.
In most shooting situations, I found using LENR provided the overriding positive benefit of reducing hot pixels. It just needs to be better, Sony!
How evenly an image is illuminated is a common factor when testing lenses.
But astrophotography, which often requires extreme contrast boosts, reveals non-uniform illumination of the sensor itself, regardless of the optics, originating from hardware elements in front of the sensor casting shadows onto the sensor.
This is most noticeable – indeed usually only noticeable – when shooting deep-sky targets though telescopes.
With DSLRs it is the raised mirror which often casts a shadow, produced a dark vignetted band along the bottom of the frame. Its extent varies from camera model to model.
With a mirrorless camera the sensor is not set far back in a mirror box, as it is in a DSLR. As such, I would have expected a more uniformly illuminated sensor.
Instead, I saw a slight shadowing at the top and bottom edges but just at the corners. This is from a thin metal mask in front of the sensor. It intrudes into the light path ever so slightly. It shouldn’t.
This is an annoying flaw, though applying “flat fields” or ad hoc local adjustments should eliminate this. But that’s a nuisance to do, and should not be necessary with a mirrorless camera.
Worse is that long deep-sky exposures at high ISOs also exhibited a faint purple glow at the left edge, perhaps from heat from nearby electronics, a so-called “amp glow.” Or I’ve read where this is from an internal infrared source near the sensor.
Taking a dark frame with LENR did not eliminate this, and it should, demonstrating again that for whatever reason in the a7III LENR is not as effective as it should be.
I have not seen such “amp” glows in cameras (at least in the DSLRs I’ve used) for a number of years, so seeing it in the new Sony a7III was another surprise.
This would be much tougher to eliminate in deep-sky images where the extreme contrast boosts we typically apply to images of nebulas and galaxies will accentuate any odd glows.
UPDATE: March 27, 2021 — Subsequent firmware updates seem to have eliminated this amp glow. One supplier of filter-modified cameras, Spencer’s Camera, who had refused to modify Sonys because of this glow, now lists many Sony Alphas as suitable for modification. However, the sensor masks and “green stars” (described below) still make the Sony a7III less desirable for deep-sky imaging than other mirrorless cameras I’ve tested.
When shooting deep-sky objects, particularly red nebulas, we like a camera to have a less aggressive infrared cutoff filter, to pick up as much of the deep red Hydrogen-Alpha emission line as possible.
The Sony showed poor deep-red sensitivity, though not unlike other cameras. It was a little worse than the stock Canon 6D MkII.
This isn’t a huge detriment, as anyone who really wants to go after deep nebulosity must use a “filter-modified” camera anyway.
Canon and Nikon both offered factory modified cameras at one time, notably the Canon 60Da and Nikon D810a. Sony doesn’t have an “a” model mirrorless.
To get the most out of the Sony for deep-sky imaging you would have to have it modified by a third-party, though the amp glow described above makes it a poor choice for modification.
Live View Focusing and Framing
Up to now my report on the Sony a7III hasn’t shown as glowing a performance as all the YouTube reviews would have you believe.
But Live Focus is where the a7III really stands out. I love it!
In Live View it is possible to make the image so bright you can actually see the Milky Way live on screen! Wow! This makes it so easy to frame nightscapes and deep-sky fields.
But this special “Bright Monitoring” mode is as well hidden as Sony could make it. Unless you actually read the full-length 642-page PDF manual (you have to download it), you won’t know about it. Bright Monitoring does not appear in any of the in-camera menus you can scroll through, so you won’t stumble across it.
Instead, you have to go to the Camera Settings 2 page, then select Still Image–Custom Key. In the menu options that appear you can now scroll to one called Bright Monitoring. Surprise! Assign it to one of the hardware Custom C buttons. I put it on C2, making it easy to call up when needed.
The other Live View function that works well, but also needs assigning to a C button is the Camera Settings 1 > Focus Magnifier. I put this on C1. It magnifies the Live View by 5.9x or 11.7x, allowing for precise manual focusing on a star.
Two other functions are useful for Live View:
Camera Settings 2 > Live View Display > Setting Effect ON. This allows the Live View image to reflect the camera settings in use, better simulating the actual exposure, even without Bright Monitoring on.
Camera Settings 1 > Peaking Setting. Turning this ON superimposes a shimmering effect on parts of an image judged in focus. This might be an aid, or an annoyance. Try it.
In all, the Sony provides superb, if well-hidden, Live View options that make accurately framing and focusing a nightscape or time-lapse scene a joy.
Great Features for Astrophotography
Here are some other Sony a7III features I found of value for astrophotography, and for operating the camera at night.
Tilting LCD Screen
Like the Nikon D750, the Sony’s screen tilts vertically up and down, great for use when on a telescope, or on any tripod when aimed up at the sky. As photographers age, this becomes a more essential feature!
The four C buttons can be programmed for oft-used functions, making them easy to access at night. Standard functions such as ISO and Drive Mode are easy to get at on the thumb wheel, unlike the Nikon D750 where I am forever hunting for the ISO or Focus Zoom buttons, or the Canon 6D MkII which successfully hides the Focus Zoom and Playback buttons at night.
In new models, Sony now offers the option of a final “My Menu” page which you can populate with often-used functions from the other 35 pages of menu commands!
Adaptability to Many Lenses
Using the right lens adapter (I use one from Metabones), it is possible to use lenses with mounts made for Canon, Nikon, Sigma and others. Plus there are an increasing number of lenses from third parties offered with native Sony E-mounts. This is good news, as astrophotography requires fast, high-quality lenses, and the Sony allows more choices.
Lighter Weight / Smaller Size
The compact a7III body weighs a measured 750 grams, vs. 900 grams each for the Nikon D750 and Canon 6D MkII. The lower weight can be helpful for use on lightweight telescopes, on small motion control devices, and for simply keeping weight and bulk down when traveling.
Dual Card Slots
Not essential, but having two card slots is very helpful, for backup, for handling overflows from very long time-lapse shoots, or assigning them for stills vs. movies, or Raws vs. JPGs. Only Slot 1 will work with the fastest UHS II cards that are needed for recording the highest quality 4K video.
It is possible to power the camera though the USB port (indeed that’s how you charge the battery, as no separate battery charger is supplied as standard, a deficiency). This might be useful for long shoots, though likely as not that same USB port will be needed for an intervalometer or motion control device. But if the Sony had a built-in intervalometer…!
To reduce battery drain it is possible to turn off the EVF completely – I find I never use it at night – and to turn off the LCD display when shooting, though the latter is an option you have to activate to add to the Display button’s various modes.
The downside is that when shooting is underway you get no reassuring indication anything is happening, except for a brief LED flash when an image is written to a card.
Electronic Front Curtain Shutter
Most DSLRs do not offer this, but the Sony’s option of an electronic front curtain shutter and the additional Silent Shooting mode completely eliminates vibration, useful for some high-magnification shooting through telephotos and telescopes.
What’s Missing for Astrophotography
Intervalometer — NOW INCLUDED! UPDATE: In April 2019 Sony issued a v3 Firmware update for the a7III which added an internal intervalometer. I’ve used this new function and it works very well.
I had originally remarked that this useful function was missing. But no more! Thank you Sony!
While a built-in intervalometer is not essential, I find I often do use the Canon and Nikon in-camera intervalometers for simple shoots. So it is great to have one available on the Sony. However, like other brands’ internal intervalometers Sony’s is good only for exposures up to 30 seconds long.
Bulb Timer or Long Exposures
However, while the Sony has a Bulb setting there is no Bulb Timer as there is with the Canon. The Bulb Timer would allow setting long Bulb exposures of any length in the camera.
Instead, for any exposures over 30 seconds long (or time-lapses with >30-second-long frames) the Sony must be used with an external Intervalometer. I use a $50 Vello unit, and it works very well. It controls the Sony through the camera’s Multi USB port.
In-Camera Image Stacking
Also missing, and present on most new Canons, are Multiple Exposure modes for in-camera stacking of exposures in a Brighten mode (for star trails) or Averaging mode (for noise smoothing).
Yes, this can all be done later in processing, but having the camera do the stacking can often be convenient, and great for beginners, as long as they understand what those functions do, or even that they exist!
When using its internal intervalometer, the Nikon D750 has an excellent Exposure Smoothing option. This does a fine job smoothing frame-to-frame flickering in time-lapses, something the Canon cannot do. Nor the Sony, as it has no intervalometer at all.
Light Frame Buffer in LENR
This feature is little known and utilized, and only Canon full-frame cameras offer it. Turn on LENR and it is possible to shoot three (with the 6D MkII) or four (with the 6D) Raw images in quick succession even with LENR turned on. The Canon 5D series also has this.
The dark frame kicks in and locks up the camera only after the series of “light frames” are taken. This is wonderful for taking a set of noise-reduced deep-sky images for later stacking. Nikons don’t have this, not even the D810a, and not Sonys.
The Sony’s buttons are not illuminated. While these might add glows to long exposure images, if they could be designed not to do that (i.e. they turn off during exposures), lit buttons would be very handy at night.
Limited Touch Screen Functions
An alternative would be an LCD screen that was touch sensitive. The Sony a7III’s screen is, but only to select an area for auto focus or zooming up an image in playback. The Canon 6D MkII has a fully functional touch screen which can be, quite literally, handy at night.
Here’s another area where the new Sony a7III really shines.
It offers 4K (or more precisely UltraHD) video recording for videos of 3840 x 2160 pixels. (True 4K is actually 4096 x 2160 pixels.)
With a fast enough UHS-II Class card it can record 4K video up to 30 frames per second and at a bit rate of either 60 or 100 Mbps.
At 24 fps videos are full-frame with no cropping. Hurray! You can take full advantage of wide-angle lenses, great for auroras. At 30 fps, 4K videos are cropped with a 1.2x crop factor.
In Movie Mode ISO speeds go up to ISO 102,400, but are pretty noisy, if unusable at such speeds.
But when shooting aurora videos I found, to my surprise, I could “drag” the shutter speeds as slow as 1/4-second, fully 4 stops better than the Nikon’s slowest shutter speed of 1/60 second in Full HD, and 3 stops better than the Canon’s slowest movie shutter of 1/30 second.
Coupled with a fast f/1.4 to f/2 lens, the slow shutter speed allows real-time aurora shooting at “only” ISO 6400 to 12,800, for quite acceptable levels of noise. I am very impressed!
Real-time video of auroras is not possible with anything like this quality with the Nikon (I’ve used it often), and absolutely not with the Canon. And neither are 4K.
Is the a7III as good for low-light video as the Sony a7s models, with their larger 8.5-micron pixels?
I would assume not, but not having an a7s (either Mark I or II) to test I can’t say for sure. But the a7III should do the job for bright auroras, the ones with rapid motion worth recording with video, plus offer 24 megapixels for high-quality stills of all sky subjects.
I think it’s a great camera for both astrophoto stills and video.
An example is in a 4K video I shot on May 6, 2018 of an usual aurora known as “STEVE.”
Steve Aurora – May 6, 2018 (4K) from Alan Dyer on Vimeo.
For another example of using the Sony a7III for recording real-time video of the night sky see this video of the aurora shot from Norway in March 2019.
The Northern Lights At Sea from Alan Dyer on Vimeo.
I found the a7III would use up about about 40% of the battery capacity in a typical 400-frame time-lapse on mild spring nights, with 30-second exposures. This is with the EVF and rear LCD Display OFF, and the camera in Airplane mode to turn off wireless functions to further conserve battery power. I was using the wired Vello intervalometer.
This is excellent performance on par with the DSLRs I use. At last, we have a mirrorless camera that not only doesn’t eat stars, it also does not eat batteries!
One battery can get you through a night of shooting, though performance will inevitably decline in winter, as with all cameras.
Lens and Telescope Compatibility
As versatile as a mirrorless camera is for lens choice, making use of that versatility requires buying the right lens adapter(s). They can cost anywhere from $100 to $400. The lowest cost units just adapt the lens mechanically; the more costly units also transfer lens data and allow auto focusing with varying degrees of compatibility.
For use on telescopes, the simple adapters will be sufficient, and necessary as many telescope-to-camera adapters and field flatteners are optimized for the longer lens flange-to-sensor distance of a DSLR. Even if you could get a mirrorless camera to focus without a lens adapter to add the extra spacing, the image quality across the field might be compromised on many telescopes.
I used the Metabones Canon-to-Sony adapter when attaching the Sony to my telescopes using my existing Canon telescope adapters. Image quality was just fine.
Time-Lapse Controller Compatibility
Due to limitations set by Sony, controlling one of their cameras with an external controller can be problematic.
Devices that trigger only the shutter should be fine. That includes simple intervalometers like the Vello, the Syrp Genie Mini panning unit, and the Dynamic Perception and Rhino sliders, to name devices I use. However, all will need the right camera control cable, available from suppliers like B&H.
And, as I found, the Sony might need to be placed into Continuous shooting mode to have the shutter fire with every trigger pulse from the motion controller. When used with the Genie Mini (below) the Sony fired at only every other pulse if it was in Single shot mode, an oddity of Sony’s firmware.
Some time-lapse controllers are able to connect to a camera through its USB port and then adjust the ISO and aperture as well, for ramped “holy grail” sunset-to-Milky Way sequences.
In conclusion, here’s my summary recommendations for the three competitive cameras, rating them from Poor, to Fair, to Good, to Excellent.
SONY: I deducted marks from the Sony a7III for deep-sky imaging for its lack of a light frame buffer, poor red sensitivity, odd LENR performance, and purple amp glow not seen on the other cameras and that dark frames did not eliminate.
However, I did not consider “star eating” to be a negative factor, as the Sony showed just as many stars and as well-resolved as did the competitors, and what more could you ask for?
I rate the Sony excellent for nightscape imaging and for real-time aurora videos. I list it as just “good” for time-lapse work only because it will not be fully compatible with some motion controllers and rampers. So beware!
NIKON: I deducted points for real-time video of auroras – the D750 can do them but is pretty noisy with the high ISOs needed. Its red sensitivity is not bad, but its lack of a light frame buffer results a less productive imaging cycle when using LENR on deep-sky shooting.
I know … people shoot dark frames separately for subtracting later in processing. However, I’ve found these post-shoot darks rarely work well, as the dark frames are not at the same temperature as the light frames, and often add noise or dark holes.
CANON: The 6D MkII’s lack of an ISO invariant sensor rears its ugly head in underexposed shadows in dark-sky nightscapes. I like its image stacking options, which can help alleviate the noise and artifacts in still images, but aren’t practical for time-lapses. Thus my Good rating for nightscapes but Fair rating for time-lapses. (See my test at https://amazingsky.net/2017/08/09/testing-the-canon-6d-mark-ii-for-nightscapes/)
While the 6D MkII has HD video, it is incapable of any low-light video work.
And its light-frame buffer is great for minimizing shooting time for a series of deep-sky images with in-camera LENR dark frames, which I find are the best for minimizing thermal noise. Give me a Canon full-frame any day for prime-focus deep-sky shooting.
It’s just a pity the 6D MkII has only a 3-frame buffer when using LENR. Really Canon? The 2008-vintage 5D MkII had a 5-frame buffer! Your cameras are getting worse for astrophotography while Sony’s are getting better.
CANON 6D Mk II
Real-Time Video (Auroras)
Wide-field Deep Sky
Telescopic Deep Sky
I trust you’ll find the review of value. Thanks for reading!
ADDENDUM as of JUNE 6, 2018
Since publishing the first results a number of people commented with suggestions for further testing, to check claims that:
The Sony would perform better for noise under dark sky conditions, at high ISOs, rather than the moonlit scene above. OK, let’s try that.
The Sony would perform better in an ISO Invariancy “face-off” if its ISOs were kept above 640, to keep all the images within the Sony’s upper ISO range of its dual-gain sensor design, with two ranges (100 to 400, and 640 on up). Fair enough.
What little “star-eater” effect I saw might be mitigated by shooting on Continuous drive mode or by firing the shutter with an external timer. That’s worth a check, too.
For the additional tests, I shot all images within a 3-hour span on the night of June 5/6, using the Sony a7III, Nikon D750, and Canon 6D MkII, with the respective lenses: the Laowa 15mm lens at f/2, the Sigma 14mm Art at f/2, and the Rokinon 14mm SP at f/2.5.
The cameras were on a Star Adventurer Mini tracker to keep stars pinpoints, though the ground blurred in the longer exposures.
DARK SKY NOISE TEST
I show only the Sony and Nikon compared here, shot at the common range of ISOs used for nightscape shooting, 800 to 12800. All images are equally well exposed. The inset image at right in Photoshop shows the scene, the Milky Way above dark trees in my backyard!
To the eye, the Sony and Nikon look very similar for noise levels, just as in the moonlit scene. Both are very good – indeed, among the best performing cameras for high-ISO noise levels. But the Sony, being four years newer than the Nikon, is not better.
BUT … what the Sony did exhibit was better details in the shadows than the Nikon.
And this was with equal processing and no application of Shadow Recovery. This is where the Sony’s Backside Illuminated sensor with presumably higher quantum efficiency in gathering photons might be providing the advantage. With its good shadow details, you have to apply less shadow recovery in post-processing, which does keep noise down. So points to Sony here.
I did put all the high ISO images through the classic noise reduction program Noise Ninja to measure total Luminance and Chrominance noise, and included the Canon 6D MkII’s images.
The resulting values and graph show the Sony actually measured worse for noise than the Nikon at each high ISO speed, 3200 to 12800, though with both performing much better than the Canon.
The higher noise of the Canon is visually obvious, but I’d say the Sony a7III and Nikon D750 are pretty equal visually for noise, despite the numbers.
DARK SKY ISO INVARIANCY
Again, here I show only the Sony and Nikon, the two “ISO invariant” cameras. The correct exposure for the scene was 30 seconds at ISO 6400 and f/2. The images shown here were shot at lower ISOs to underexposure the dark scene by 2 to 4 stops or EV. Those underexposed images were then boosted later in processing (in Adobe Camera Raw) by the required Exposure Value to equalize the image brightness.
Contrary to expectations, the Sony did not show any great loss in image quality as it crossed the ISO 640 boundary into its lower ISO range. But the Nikon did show more image artifacts in the “odd-numbered” ISOs of 640 and 500. In this test, the Nikon did not perform as well as the Sony for ISO invariancy. Go figure!
Again, the differences are in images vastly underexposed. And both cameras performed much better than the ISO “variant” Canon in this test.
STAR EATER REVISITED
I shot images over a wide-range of exposures, from 2 seconds to 2 minutes, but show only the ones covering the 2-second to 4-second range, where the “star-eater” anti-aliasing or noise smoothing applied by Sony kicks in (above 3.2 seconds it seems).
I shot with the Sony a7III on Single shot drive mode, on Continuous Low drive mode (with the camera controlling the shutter speed in both cases), and a set with the Sony on Bulb and the shutter speed set by an external Vello intervalometer.
This is really pixel peeping at 400%. In Single drive mode, stars and noise soften ever so slightly at 4 seconds and higher. In Continuous mode, I think the effect is still there but maybe a little less. In shots on Bulb controlled by the External Timer, maybe the stars at 4 seconds are a little sharper still. But this is a tough call. To me, the star eater effect on the Sony a7III is a non-issue. It may be more serious on other Sony alphas.
DE-BAYERING STAR ARTIFACTS
An issue that, to me, has a more serious effect on star quality is the propensity of the Sony, and to some extent the Nikon, to render tiny stars as brightly colored points, unrealistically so. In particular, many stars look green, from the dominance of green-filtered photosites on Bayer-array sensors.
Here I compare all three cameras for this effect in two-minute tracked exposures taken with Long Exposure Noise Reduction (i.e. in-camera dark frame subtraction) off and on.
The Sony shows a lot of green stars with or without LENR. The Nikon seems to discolor stars only when LENR is applied. Why would that be? The Canon is free of any such issue – stars are naturally colored whether LENR dark frames are applied or not.
This is all with Raws developed with Adobe Camera Raw.
When opening the same Raws in other programs (ON1 Photo RAW, Affinity Photo, DxO PhotoLab, and Raw Therapee) the results can be quite different, with stars often rendered with fringes of hot, colored pixels. Or rendered with little or no color at all. Raw Therapee offers a choice of de-Bayering, or “de-mosaic,” routines, and each produces different looking stars, and none look great! Certainly not as good as the Canon rendered with Camera Raw.
What’s going on here is a mystery – it’s a combination of the cameras’ unique Raw file formats, anti-alias filter in front of the sensor (or lack thereof in the Sony), and the de-Bayering routines of all the many Raw developers wrestling with the task of rendering stars that occupy only a few pixels. It’s unfair to blame just the hardware or the software.
But this test re-emphasized my thoughts that Canon DSLRs remain the best for long-exposure deep-sky imaging where you can give images as much exposure time as they need, while the ISO invariant Sony and Nikons exceed at nightscape shooting where exposures are often limited and plagued by dark shadows and noise.
I present a new 4-minute music video (in 4K resolution) featuring time-lapses of the Milky Way.
One of the most amazing sights is the Milky Way slowly moving across the sky. From Canada we see the brightest part of the Milky Way, its core region in Sagittarius and Scorpius moving across the souther horizon in summer.
But from the southern hemisphere, the galactic core rises dramatically and climbs directly overhead, providing a jaw-dropping view of our edge-on Galaxy stretching across the sky. It is a sight all stargazers should see.
I shot the time-lapses from Alberta, Canada and from Australia, mostly in 2016 and 2017.
I include a still-image mosaic of the Milky Way from Aquila to Crux shot in Chile in 2011.
Do watch in 4K if you can! And in Full-Screen mode.
Locations include Writing-on-Stone and Police Outpost Provincial Parks, and Banff and Jasper National Parks in Alberta.
In Australia I shot from the Victoria coast and from inland in New South Wales near Coonabarabran, with some scenes from the annual OzSky Star Safari held each April.
The first total lunar eclipse in 2.5 years provides lots of opportunities for some great photos.
On the morning of January 31, before sunrise for North America, the Full Moon passes through the umbral shadow of the Earth, creating the first total eclipse of the Moon since September 27, 2015.
The pre-dawn event provides many photo opportunities. Here’s my summary of tips and techniques for capturing the eclipsed Moon.
But First … What is a Lunar Eclipse?
As the animation (courtesy NASA/Goddard Space Flight Center) shows, an eclipse of the Moon occurs when the Full Moon (and they can happen only when the Moon is exactly full) travels through the shadow of the Earth.
The Moon does so at least two times a year, though often not as a total eclipse, one where the entire disk of the Moon is engulfed by the umbra.
When the Moon is within only the outer penumbral shadow we see very little effect, with a barely perceptible darkening of the Moon, if that. I don’t even list the times below for the start and end of the penumbral phases.
It’s only when the Moon begins to enter the central umbral shadow that we see an obvious effect. That’s when the partial eclipse begins, and we see a dark bite appear on the left edge of the Moon. The shadow appears to creep across the Moon to darken more of its disk. While it looks like the shadow is moving across the Moon, it is really the Moon moving into, then out of, the umbral shadow that causes the eclipse.
At this eclipse the partial phases last about an hour before and after totality.
Once the Moon is completely immersed in the umbra, totality begins, and lasts 77 minutes at this eclipse, a generous length. However, in North America, only sites in the western half of the continent get to see all or most of totality.
Where is the Eclipse?
As the chart above shows, the Pacific area including Hawaii, Australia, and eastern Asia can see the entire eclipse with the Moon high in the evening or midnight sky.
Most of North America (my tips are aimed at North American photographers) can see at least some part of this eclipse.
From the eastern half of the continent the Moon sets at sunrise during either totality (from the central areas of North America), or during the first partial phases (from eastern North America). Those in the east can take advantage of interesting photo opportunities by capturing the partially eclipsed Moon setting in the west in the dawn twilight.
However, the most dramatic images of a deep red Moon in the western sky, such as above, will be possible only from the west. And even then, the further north and west you live, the better your view.
Even from the southwestern United States the Moon sets just after the end of totality, requiring a site with a low and clear horizon to the west in order to see the whole event.
I live in Alberta, Canada, and the diagrams I provide here are for my area, where the Moon sets during the final partial phase. I offer them as examples of the kinds of planning you can do to ensure great photos. But exactly where the Moon will be during totality, and where and when it will set on your horizon, will depend on your location.
The latter two apps present the sightlines toward the Moon overlaid on a map of your location, to help you plan where to be to shoot the eclipsed Moon setting behind a suitable foreground.
When is the Eclipse?
While where the Moon is in your sky depends on your site, the various eclipse events happen at the same time for everyone, with differences in hour due only to the time zone you are in.
Here are the times for the start and end of the partial and total phases.
Note that all times are A.M., in the early morning, before sunrise, on January 31. Go out at 6 P.M. on the evening of January 31 and you’ll be 12 hours too late. You missed it!
All times are A.M. on January 31. “—“ means the event is not visible; the Moon has set.
The time of moonset at your site will vary with your location. Use planning apps to calculate your local moonset time.
Picking a Site
No matter where you are in North America you want a site with a good view to the west and northwest, preferably with a clear view of a relatively unobstructed but photogenic horizon.
While having an eclipse occur at dawn (or at dusk) does limit the amount of eclipse we can see, it has the benefit of providing many more photo opportunities of the eclipsed Moon above a scenic landscape or foreground element.
From eastern North America you will have to be content with images of the partially eclipsed Moon setting, similar to the image above of a rising partially-eclipsed Moon.
From the centre of the continent, where the Moon sets during totality, the dim, reddened Moon is likely to disappear into the brightening sky. Remember, when the Moon is full it sets just as the Sun rises. So shots of a red Moon right on the horizon aren’t likely to be possible. The Moon will be too dim and the sky too bright.
From sites in the west, the Moon will set either just at the end of totality or shortly afterwards, making the Moon brighter and more obvious in the sunrise sky, as the foreground in the west lights up with red light from the Sun rising in the east.
It is that same red sunlight filtered by our atmosphere that continues on into our planet’s shadow and lights the Moon red during totality.
Picking a Technique
Lunar eclipses lend themselves to a wide range of techniques, from a simple camera on a tripod, to a telescope on a tracking mount following the sky.
What you use depends not only on the gear you have on hand, but also on your site. It might not be practical to set up loads of gear at a scenic site you have to trek into — especially when you have to set up in the wee hours of a cold winter morning.
You could set up earlier that night on January 30, but only if your site is safe enough to leave the gear unattended while you sleep.
Keep it simple!
Option 1: Simple Camera-on-Tripod
The easiest method is to take single shots with a moderate wide-angle or normal lens with the camera on a fixed tripod. No fancy trackers are needed here.
If the sky is bright with twilight, you might be able to meter the scene and use Auto exposure.
But earlier in the night, with the Moon in a darker sky, as I show above, use Manual exposure and try settings of 1 to 10 seconds at f/2.8 to f/4 at ISO 400 to 1600. That’s a wide range, to be sure, but it will vary a lot depending on when you shoot and where you are, factors that will affect how bright the sky is at your site. Just shoot, check, and adjust.
Option 2: Advanced Camera-on-Tripod
A more advanced method is to compose the scene so the lens frames the entire path of the Moon from the start of the partial eclipse until moonset.
As shown above, that will take at least a 35mm lens on a full frame camera, or 20mm lens on a cropped frame camera.
Take exposures every 15 to 30 seconds if you want to turn the set into a time-lapse movie. But a still-image composite with the lunar disks well separated will need shots only every 5 to 10 minutes.
Such a composite takes good planning and proper exposures to pull off, but will be true to the scene, with the lunar disk and its motion shown to the correct scale as it was in the sky. That’s in stark contrast to the flurry of ugly “faked” composites that will appear on the web by the end of February 1, ones with huge telephoto Moons pasted willy-nilly onto a wide-angle sky. Don’t do it!
Exposures for any lunar eclipse are tricky, whether you are shooting closeups or wide-angles, because the Moon and sky change so much in brightness.
For wide-angle composites, you can expose just for the bright lunar disk and let the sky go dark. Exposures for just the Moon will range from very short (about 1/500th second at ISO 100) for the partials, to 1 to 2 seconds at ISO 400 for the totals, then shorter again (1/15 to 1/2 second at ISO 400) for the end shots in twilight when the Moon and sky may be similar in brightness. That’ll take constant monitoring and adjusting throughout the shoot.
As I did below, you’d then composite and layer the well-exposed disks into another background image exposed longer for the sky, likely shot in twilight. To maintain the correct relative locations of the lunar disks and foreground, the camera cannot move.
That technique works best if it’s just a still image you are after, such as below.
The above image is a composite of the April 4, 2015 total lunar eclipse from Monument Valley, Utah. That eclipse occurred under similar circumstances as this month’s eclipse, with the eclipse underway as the Moon set in the west at sunrise.
By comparison, the composite here is made of a few selected frames out of hundreds I took at 15-second intervals, and with each frame exposed for the sky, for use in a time-lapse movie. In this case, the Moon became overexposed at the end as it emerged from the umbra.
Indeed, if it’s a time-lapse movie you want (see the video linked to below), then each frame will have to be exposed well enough to show the sky and landscape.
While this method will overexpose the partially-eclipsed Moon, the Moon will darken and become better exposed throughout totality when the same long exposure for the reddened Moon might also work for the sky, to pick up stars. Exposures will have to shorten again as the sky brightens with twilight.
Again, constant baby-sitting and adjusting the camera will be needed. So if it’s cold where you are prepare for a frigid multi-hour shoot. I doubt you’ll be able to leave the camera on Auto exposure to run on its own, not until at least bright twilight begins.
Option 3: Telephoto Close-Ups
The Moon is surprisingly small (only 1/2-degree across) and needs a lot of focal length to do it justice.
For an “in-your-face” close-up of the eclipse you’ll need a 300mm to 800mm (!) lens. Unfortunately, the Moon and sky are moving and any exposures over 1 to 2 seconds (required during totality) will blur the Moon badly if its disk is large on the frame.
If you don’t have a tracking mount, one solution is to keep the Moon’s disk small (using no more than a fast f/2.8 200mm lens) and exposures short by using a high ISO speed.
Or plan to shoot with a telephoto only when the Moon is low in the sky, as I did above, when you can include the horizon which you would want to be sharp anyway. Framing the Moon and horizon won’t need a super telephoto.
The sky will then also be brighter and require short exposures that don’t need to be tracked. However, how bright and obvious the Moon will be will again depend on your location. This may or may not be a practical option, certainly not if the Moon is setting during mid-totality where you are.
Option 4: Tracked Telescopic Close-Ups
If you have a mount that can be polar aligned to track the sky, then more options are open to you.
You can use a telescope mount or one of the compact and portable trackers, such as the Sky-Watcher Star Adventurer or iOptron Sky Tracker units. While these latter units work great, you are best to keep the payload weight down and your lens size under 300mm.
That’s just fine for this eclipse, as you really don’t need a frame-filling Moon. The reason is that the Moon will appear about 4 degrees away from the bright star cluster called the Beehive, or Messier 44, in Cancer. As shown above, a 200mm to 300mm lens will frame this unique pairing well.
Even so, exposures to show the cluster properly might have to be long enough that the Moon overexposes, even at mid-totality. If so, take different exposures for the Moon and stars and composite them later, as I did below.
If you do want to shoot with more focal length, a monster telephoto lens will work, but a small telescope such as an 80mm aperture f/6 to f/7 refractor will provide enough focal length and image size at much lower cost. But either way, the lens or telescope should be mounted on a solid equatorial telescope mount, and polar aligned to track the sky.
For the sharpest lunar disks, use the Lunar tracking rate.
Exposures will vary from as short as 1/500th second at ISO 100 to 200 for the barely eclipsed Moon, to 4 to 16 seconds at f/6 to f/8 and at ISO 400 to 1600 for the Moon at mid-totality.
As I did above, during the deep partial phases shoot both long exposures for the red umbra and short exposures for the bright part of the Moon not yet in the umbra. Merge those later with High Dynamic Range (HDR) techniques and software, or with luminosity masks.
Even if you’re not sure how to do this now, shoot all the required exposures anyway so you’ll have them when your processing skills improve.
Option 5: Time-Lapse Close-Ups
With a tracking telescope you could fire shots every 30 seconds or so, and then assemble them into a time-lapse movie.
But as with wide-angle time-lapses, that will take constant attention to gradually and smoothly shift exposures, ideally by 1/3rd-stop increments every few shots during the partial and total phases.
If you track at the lunar rate, as I did in the still image below and in the music video linked to at bottom, the Moon will stay centred while it drifts though the stars.
Track at the sidereal rate and the stars will stay more or less fixed while the Moon drifts through the frame from right to left (west to east). But that takes even more careful planning to position the Moon correctly at the start of the sequence so it remains “in frame” for the duration of the eclipse and ends up where you want at the end, which will occur with the Moon low in a bright sky.
Again, planetarium software such as Starry Night, which can be set to display a camera frame, is essential to plan the shoot.
Either way, do take care to accurately polar align your mount, or you’ll be confronted with the monumental task of having to manually align hundreds of images later. Trust me, I know!
I would consider the telescopic time-lapse method the most challenging of techniques.
Considering the hour of the night and the likely cold temperatures, your best plan might be to keep it simple. It’s what I plan to do. I’ll be happy to get a few good wide-angle still images, and perhaps a tracked telephoto close-up of the Moon and Beehive as a bonus.
While there is another total lunar eclipse (TLE) in six months on July 27/28, it is not visible at all from North America.
Our next TLE occurs 12 Full Moons, or one lunar year from now, on the night of January 20/21, 2019, when all of North America gets to watch totality at a more reasonable hour, though perhaps not at a more reasonable temperature.
I leave you with a music video of the last TLE, on September 27, 2015 that incorporates still and time-lapse sequences shot using all of the above methods.
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.