Filter Pattern for Canon 60d

Hi,

I’ve just been trying the 0.99.6 build on Windows and it seems to be reporting the wrong filter pattern:

15:45:51: Decoding Canon EOS 60D file (ISO=1600, Exposure=300.0 sec)
15:45:51: Filter pattern: GBRG
15:45:51: Reading RAW: file Western_Veil_L__MG_0175_300s_ISO1600.CR2, 1 layer(s), 5202x3464 pixels
15:45:51: Saving FITS: file …/process\light_00001.fit, 1 layer(s), 5202x3464 pixels

Later on in the process I see:

15:46:58: Bayer pattern found in header (GBRG) is different from Bayer pattern in settings (RGGB). Overriding settings.
15:46:58: Filter Pattern: GBRG
15:46:58: Reading FITS: file light_00011.fit, 1 layer(s), 5202x3464 pixels

Where as in version 0.9.11 I see the correct pattern being displayed:

15:34:41: Decoding Canon EOS 60D file (ISO=1600, Exposure=300.0 sec)
15:34:41: CFA pattern: RGGB
15:34:41: Reading RAW: file Western_Veil_L__MG_0175_300s_ISO1600.CR2, 1 layer(s), 5202x3465 pixels
15:34:41: Saving FITS: file light_00001.fit, 1 layer(s), 5202x3465 pixels

This is a change of libraw.
Old version and new version are not compatible.
But now, don’t worry. It works.

Is this already fixed? I’m running into the same problem when debayering RAW files shot with my EOS 2000D using v 0.99.8.1. The right pattern is RGGB but SiriL claims that the filter pattern reported by the header is GBRG.

Either way, isn’t is possible to add an option so that one can force a particular pattern?

There are no bugs to fix.

You already can. But please don’t.
Trust in Siril, he knows how to read the bayer pattern of your DSLR.

1 Like

I want to trust SiriL :slight_smile:

But that doesn’t change the fact that the filter pattern reported by SiriL isn’t the one my camera is using.

Yes but again trust in Siril. Bayper patern is not important because that depends where you start to debayer.

It’s not the first time a 2000D user reports me this kind of thing.
Don’t touch anything, if you debayer from the CR2 file, and the debayer will be great.

So I should ignore the pattern reported in the log, it works as intended, right?

Edit: is this related to Issue on some camera | LibRaw ? In other words, it depends which line of pixels you begin reading when you open the image?

Right.

Process your image, you will see :).

1 Like