Integrated image do...
 
Share:
Notifications
Clear all

MAY 4 2026: APP 2.0.0-beta44 has been released !

New improved internal memory controls should now work on all computers

May 1 2026: APP 2.0.0-beta43 has been released !

Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.

Apr 29 2026 APP 2.0.0-beta42 has been released !

New improved Normalization engine, Fixed random crashes in integration, fixed RGB Combine & Calibrate Star Colors, fixed Narrowband extraction algorithms, new development platform with performance gains, bug fixes in the tools, etc...

Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options

Update on the 2.0.0 release & the full manual

We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.

Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.

 

[Solved] Integrated image doesn't have the right color - solved the canon1200D wasn't yet supported in APP 1.041, it is in 1.042

8 Posts
3 Users
1 Reactions
4,652 Views
(@jarbi58)
Red Giant
Joined: 9 years ago
Posts: 34
Topic starter  

Hi,

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 ?

Thanks,

Janos

 

 



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5254
 

Hi Janos,

You are right, my mistake, I just added complete support for the Canon 1200D in the new version. I will try to upload this new version today.

https://www.astropixelprocessor.com/community/release-information/astro-pixel-processor-1-042-next-version/#post-15

For now, try to use the GBRG pattern. The 1200D is on the current downloadable version not yet supported. And the CR2 loader defaults to RGGB.

I'll give you a signal here, when you can download the new version 😉

Mabula



   
ReplyQuote
(@jarbi58)
Red Giant
Joined: 9 years ago
Posts: 34
Topic starter  

Thanks Mabula,

I will reprocess it then with GBRG, no problem ! I will do it again with the new version soon to see the difference,

 

Cheers,

Janos



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5254
 

Hi Janos,

I have already created new installers with support for the EOS 1200D, check the download section 😉

Let me know if it works with the "supported" CFA pattern. And feel free to post your results, you can attach images to your posts.

Cheers,

Mabula



   
ReplyQuote
(@jarbi58)
Red Giant
Joined: 9 years ago
Posts: 34
Topic starter  

Hi,

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 !

St avg 1911.0s WSC 1 3.0 x 1.0 LZ3 ref StSh add sc BWMV nor AA RL noMBB St

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

 



   
Mabula-Admin reacted
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5254
 
Posted by: Janos

Hi,

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 !

St avg 1911.0s WSC 1 3.0 x 1.0 LZ3 ref StSh add sc BWMV nor AA RL noMBB St

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.

Cheers,

Mabula



   
ReplyQuote
 Axel
(@axel)
Main Sequence Star
Joined: 9 years ago
Posts: 19
 
Posted by: Mabula Haverkamp

Hi Janos,

You are right, my mistake, I just added complete support for the Canon 1200D in the new version. I will try to upload this new version today.

https://www.astropixelprocessor.com/community/release-information/astro-pixel-processor-1-042-next-version/#post-15

For now, try to use the GBRG pattern. The 1200D is on the current downloadable version not yet supported. And the CR2 loader defaults to RGGB.

I'll give you a signal here, when you can download the new version 😉

Mabula

Dear Mabula,

I understand from your post that the correct pattern for a EOS1300D is GBRG. Where did you get the info?

When I upload it in Pixinsight it  reads the CR2 data and indicates "filter pattern RG/GB"

Thanks for your help

Axel



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5254
 

Hi Axel,

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...)

Regards,

Mabula

 



   
ReplyQuote
Share: