Why do I see blocky artifacts in a night sky when viewing or exporting Canon RAW files in Lightroom?
Asked 9/11/2019
2 views
2 answers
0
I shot a night-sky panorama with Canon .CR2 files. After importing them into Lightroom and exporting TIFFs for stitching, I noticed a blocky/compression-like pattern in the sky. The same artifact is also visible when viewing the original RAW file directly in Lightroom, so it does not appear to be caused by the panorama stitching.
Why can this happen with a RAW file in Lightroom, and is there anything I can change during import or export, such as color space or bit depth, to reduce it?
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
6y ago
2 Answers
2
I imported several .cr2 images into Lightroom, exported them as .tif without any adjustments...
There's no such thing. If you are seeing an image on your screen and/or exporting a TIFF, the raw data is being interpreted in one of a countless number of possible legitimate interpretations. If you "made no adjustments" it just means you are leaving the default settings Lightroom used to initially open the raw file. What those default settings are depends upon what they have been set to, either by the software designer or someone who has changed them after installation onto the computer you are using.
When you export as TIFF you "bake in" many of the choices that were made regarding how to interpret the raw image data. White point, black point, white balance, etc. are all much less flexible with a TIFF file than with a raw file. If you then try to move any of those things very far using the TIFF, you'll get artifacts. Sure, a TIFF from a 12 or 14 bit raw file can be 16-bit, but that does not mean it contains all of the information the raw file contained. Raw files contain a single monochromatic luminance value for each photosite (a/k/a pixel well or sensel) on the sensor. TIFF files (as you are using them) contain RGB values for each pixel in an image. These are two very different things.
One thing to keep in mind is that Lightroom does not use demosaicing algorithms produced by Canon when dealing with .cr2 files. Instead, Adobe develops their own algorithms, primarily through what we might call reverse engineering.
It was shot on an 80D using a 17-70mm Sigma Lens in the mRAW format.
mRAW is not really a true raw image format that preserves the monochromatic luminance value collected by each sensel on the camera's sensor. Raw files directly out of the camera have only 14 bits per pixel. The pixels are all monochrome. In sRaw and mRaw files, the images are already demosaiced, and there is more color information per pixel. It's not 14*3 = 42 bits per pixel, though. The data are converted from RGB into a sort of linear YCbCr format with 1:2 chromaticity subsampling.
That's probably the primary source of the chrominance noise that seems to be a major contributor to your artifact.
The artifacting does not occur when observing the .cr2 file in a viewer like IrfanView when increasing the contrast there.
Then the issue is most likely with Lightroom's demosaicing algorithms for Canon mRAW files. Irfanview is probably displaying the JPEG preview image embedded in the mRAW file. The JPEG preview is generated in-camera using Canon's demosaicing algorithms. (Presumably the same algorithms are used to create the RGB values for each pixel of the mRAW files). You will get results nearly identical to the in-camera generated JPEG preview using Canon's Digital Photo Professional 4 software if DPP 4 is set to the same settings as the camera's settings at the time the JPEG preview was generated when the image was shot.
Originally by user15871. Source · Licensed CC BY-SA 4.0
user15871
6y ago
0
Generated from our catalog & community — verify before relying on it.
A RAW file is not a finished image. Lightroom must interpret the sensor data to display it, and even with “no adjustments” you are still seeing Lightroom’s default rendering of that RAW data. When you export to TIFF, that interpretation is baked in.
So the issue is not that Lightroom is adding JPEG compression; it’s that the RAW data plus the default processing can reveal artifacts or tonal/blocky patterns in very dark, low-detail areas like a night sky. Changing TIFF color space or bit depth won’t fix the underlying cause, though higher bit depth preserves more editing flexibility after export.
In short:
- RAW is always interpreted, never shown completely unprocessed.
- “No adjustments” in Lightroom still means default settings are being applied.
- Exporting TIFF locks those choices in.
- The artifact is likely coming from how the dark sky data is being rendered, not from panorama stitching or JPEG compression.
If needed, review Lightroom’s default RAW settings and tone-related rendering choices rather than import color space alone.
Recommended products
UniqueBot
AI6y ago
Your Answer
Related Questions
Why do I see blocky sky gradients in Lightroom, even from RAW files?
Why does noise seem to reappear after saving a noise-reduced RAW edit as JPEG?
Why won't Lightroom import Canon 450D RAW+JPEG files, while RAW-only files work?
Why do smooth sky gradients show pale arcs or bands in my photos?
Why do my Nikon D810 night photos show moiré after exporting small JPEGs from Lightroom?