15th Feb 2024: Astro Pixel Processor 2.0.0-beta29 released - macOS native File Chooser, macOS CMD-Q fixed, read-only Fits on network fixed and other bug fixes
7th December 2023: added payment option Alipay to purchase Astro Pixel Processor from China, Hong Kong, Macau, Taiwan, Korea, Japan and other countries where Alipay is used.
Hi all,
I am using a dual setup with a ZWO294mc (which needs to force the RGGB pattern under 0 raw/fits) and a QHY294MM (which doesn't need that),
What do I have to use under 0 raw/fits to integrate both cam's frames together?
TIA and CS
Mike
In that case I would process them separately and then save the calibrated frames. Those calibrated frames can then be loaded in together. If that doesn't work, please let me know.
Adding to what Vincent wrote: force bayer only is needed if APP cannot determine itself that the OSC frames need debayering. APP will determine that based on the FITS header so if the bayer pattern is in there then you do no need to force bayer.
Note that if you load both OSC and mono frames then force bayer should not be enabled since then APP will think that the mono frames are OSC as well. So if you load all frames and process them and you see that APP cannot determine that the OSC lights need debayering, then you need to process them separated from the mono frames and force bayer on the OSC data.
@wvreeven
Thanks, that was my thought, too.
Not sure if the FITS header work, but I will try it.
Regards
Mike
@vincent-mod
Thank you Vincent. That also answers my following question about registration 😉 If I use all the different but calibrated files, they will register during the processing!
Regards
Mike
