Tags

, , , , ,

While I’m not a hard-core astro-photographer, I have to confess that for me there are few experiences that come close to standing out in a landscape far from city lights, observing and photographing the night sky. There’s something primeval by way of the connection that it provides with the universe – and with those generations from the past who, without means to easily light their rooms, must have been keen observers of the night skies and their periodic changes in the arrangement of moon, planets and stars.

Over recent months, I’d begun to pursue photography of the night skies over New Zealand with a little more commitment, exploring the astrophotography websites to hone my skills both in image capture and processing. And that began to pay off with some results that begin to capture for me something of the mysteries of what I see above me in our National Parks on a clear, moonless night. That is until I come across the words ‘star-eater algorithm! – and discovered the veritable can of worms that has been opened up by Sony’s latest firmware (3.3) for its Sony A7RII and A7SII cameras.

What is the star-eater algorithm?

The exact nature of Sony’s star-eating algorithms has been analysed and described in a great detail elsewhere, with Jim Kasson’s website (here) containing probably the most detailed examination of what it does. Otherwise, try a web search for “Sony A7R star-eating”.

In brief, the star-eating algorithm is a blanket modification of the raw image that comes off the camera sensor, and is probably designed to deal both with the noise that occurs particularly with longer exposures, and with those pesky pixels that begin to cease functioning in any digital camera with time. The catch is that this filter not only deals to noise and dead pixels – it also destroys much of the fine-scale digital data that describes those small features of the night sky, i.e., stars – hence the name! As a consequence, the ‘raw’ file no longer contains the data returned from the sensor, but a filtered version of it that is now missing the most important detail that astrophotographers are targeting.

Changes in firmware 3.3

So why the reference to firmware version 3.3?

From various descriptions on the internet, it appears that in previous versions of their firmware for the A7RII and A7SII, Sony applied their median filtering algorithm only to long exposures shot with the bulb setting. Exposures shot on manual or aperture priority out to 30 seconds were not affected, so that raw files shot with shorter exposures contained the raw data delivered by the sensor (provided that excessive ISO’s were not used).

That all changed in firmware version 3.3, the release notes for which (here) only identify changes for radio control of lighting, improvements for temperature control, and a vague improvement in ‘overall stability and operability of the camera’. Ominously, Sony warn that installation of this firmware upgrade is permanent and cannot be reversed – we’ll come back to that later!

As users began to implement this update on their Sony cameras, disturbing reports began to surface in the astrophotography community (here) – it appeared that Sony had extended their application of median filtering used with bulb exposures so that it now affected all exposures longer than 3.2 seconds. In short, once version 3.3 of the firmware has been installed on an A7RII or A7SII, it seems that any exposure of four seconds or longer no longer delivers true raw-format data – only pretend raw-format data in which much of the fine detail of objects such as stars is very substantially degraded.

Impacts of the star-eating algorithm on star photos

This change by Sony has huge practical implications for astrophotography, given that night sky exposures are generally set to maximise the capture of night-sky detail (longer) while avoiding star trailing (shorter). Typical exposures when using a 35 mm lens are of the order of six seconds, extending to ten seconds for a 21 mm lens, and  12-14 seconds for a 15 mm lens. While all of these exposure lengths can still be used, the files that they now deliver have had substantial amounts of the star detail obliterated by this blanket imposition of a median filter.

To demonstrate the magnitude of this I have posted examples below,  these consisting of 100% and 200% crops from two single images of the Milky Way shot a week ago, the first of 3.2 seconds, and the second of 4 seconds. They were shot a minute or so apart using my Sony A7RII and a Zeiss ZM Distagon 35mm lens, tripod mounted, with image stabilization disabled, and using a 2-second timer delay. Both images were imported into Lightroom where all sliders were set to 0, apart from saturation which was set to +20; exposure was set to +1 for the 3.2 second image and to 0.8 for the 4 second image, this difference being applied to correct for the difference in exposure length. Default Lightroom noise settings were applied. Inspection of these image pairs will show the significant loss of image detail that results from Sony’s extension of their median filtering to all images of four seconds and longer.

Incidentally, this same effect is also dramatically revealed when using software such as DeepSkyStacker (DSS) to process sets of images such as these. In particular, DSS detects around 20-30% more stars when processing a stack of 3.2 second images (no star-eater), than in an equivalent set of 4 second images (star-eater), even though the latter should contain more stars given its longer exposure!

Not surprisingly, stacks of 30 images processed in DSS with dark and flat files also exhibit a disappointing loss of detail when the exposure time is extended beyond 3.2 seconds. Note in this next pair of images both the suppression of small (single-pixel) stars and the overall loss of fine detail in all features, e.g., in the star cluster lower left.

After full DSS treatment

What can we do?

Given the significant degree of degradation in an existing camera capability that has occurred as a result of this firmware upgrade, I think that there is a responsibility on the user community to persistently find clear and constructive ways to raise this issue with Sony, including reminding them of the way that Nikon got around this problem.

To be fair, Sony have responded to user concerns in the past, providing an uncompressed version of their raw files in response to complaints about the compressed format data that was the only raw option in earlier versions of their firmware.

However, I would rate the impacts of this median filtering of long-exposure images as having a way more damaging impact on image quality than Sony’s original lossy file compression. Combine that with the irreversible nature of this change for those of us who trusted Sony enough to install their firmware upgrade, and some action on Sony’s part would seem to be imperative.

My dream then, is that Sony will correct this either by providing a firmware upgrade that includes a menu option to allow spatial filtering to be turned off for long exposures, or by making it possible for users to backwards step their cameras to version 3.2 firmware if they so wish.

If so, users of A7SII’s and A7RII’s might once again have access to the raw image data as it comes off the camera sensor, with freedom to then process it as best suits their application.

Update – Tuesday 9th…

Late last week, I contacted the Sony help line here in New Zealand about this issue, and was connected through to a call centre in the Philippines. The support person asked me to send a link to this blog, and I subsequently received a request for the raw files used to create the first pair of figures above. Since then I have had further contact from Sony to clarify details regarding my camera, lens used, firmware version, etc. When I spoke to them again today I was informed that Sony’s engineers are working on this problem, and will most likely resolve it through an updated version of the firmware – fingers crossed!

Update – Sunday 28th May…

Still no definitive word from Sony that they are committed to addressing this mess, although I have been assured informally by Sony user support staff that they are ‘working on it’. Interestingly, Jim Kasson has just reported that the same issue occurs with Sony’s new flagship model, the A9 – see here – so one can guess that astro-photographers won’t be flocking to that camera!