I started to use the workflow on one of my CR2 RAW image sets, taken with a modded Canon 1200D. When I look at the integrated image, the colors don't look right as if I would have choosen a wrong bayer pattern. In APP in step 0 I have set "supported" since this camera is listed. Could someone point me to the right direction ?
Just to share my first humble result with APP ;-). I have processed my Canon 1200D RAW-s with the latest version, "supported" gives the correct colors now after integration. This is a stack of 47x50s exposures with a Tokina 300mm telelens on a Sky adventurer. No calibration frames applied so far. I have done some noise reduction and removing color aberration halo's from stars in Photoshop CC.
The most effortless processing sofware I've ever seen !
I have some additional questions about the Tools part en finetuning details, but I should post it on the workflow subforum I suppose ?
Just to share my first humble result with APP ;-). I have processed my Canon 1200D RAW-s with the latest version, "supported" gives the correct colors now after integration. This is a stack of 47x50s exposures with a Tokina 300mm telelens on a Sky adventurer. No calibration frames applied so far. I have done some noise reduction and removing color aberration halo's from stars in Photoshop CC.
The most effortless processing sofware I've ever seen !
I have some additional questions about the Tools part en finetuning details, but I should post it on the workflow subforum I suppose ?
cheers,
Janos
Hi Janos,
Great ! Thank you for sharing 😉
Yes, post it on workflow and I'll help you out there.
We can start with a vignetting correction or light pollution removal to remove illumination differences in the field of view.
Indeed the correct CFA pattern for both 1200D & 1300D (or REBEL T5 & T6) is actually GBRG.
Pixinsight uses dcraw for CR2 conversion and dcraw internally is cutting corners... APP uses the whole sensor which PI with DCRAW does not. So the reason for PI to report it as RGGB is because DCRAW has removed an uneven amount of lines from the top of the whole sensor.
So this is basically an implementation issue induced by DCRAW, not by PI 😉
(I have written the CR2 conversion myself and have read & studied the dcraw code ... dcraw is great but it skips corners...)