UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
When I do combine RGB in APP and I have the Ha channel, which APP figures out during loading and spits out a master file called halpha on stacking, I have to assign it as hydrogen alpha when it asks what channel I am putting in since it always shows as custom. It is almost as if APP can't read the fits header it assigns to the stacked master for hydrogen alpha channels.
When I do combine RGB in APP and I have the Ha channel, which APP figures out during loading and spits out a master file called halpha on stacking, I have to assign it as hydrogen alpha when it asks what channel I am putting in since it always shows as custom. It is almost as if APP can't read the fits header it assigns to the stacked master for hydrogen alpha channels.
What filter name exactly are you using @imnewhere in your capture software? Or what filter name is present in your light frames?
APP would say it will be custom if you use a name that we have not hard coded for h-alpha recognition. It will be easy to fix for sure 😉
Mabula
Â
When I do combine RGB in APP and I have the Ha channel, which APP figures out during loading and spits out a master file called halpha on stacking, I have to assign it as hydrogen alpha when it asks what channel I am putting in since it always shows as custom. It is almost as if APP can't read the fits header it assigns to the stacked master for hydrogen alpha channels.
What filter name exactly are you using @imnewhere in your capture software? Or what filter name is present in your light frames?
APP would say it will be custom if you use a name that we have not hard coded for h-alpha recognition. It will be easy to fix for sure 😉
Mabula
Â
Here is the one for Ha: 2022-04-25T00-30-06_CED_90_Halpha_T-25_600s_cal.fits
Oiii and Siii are like this:
2022-04-25T00-17-42_CED_90_OIII_T-25_600s_cal.fits and 2022-05-09T23-32-28_CED_90_SII_T-25_600s_cal.fits
APP reads them as exactly what they are and assigns them without me having to select a filter. I have all of them stuck in one folder based on object, telescope, and exposure length, so all the Ha, Oiii, and Sii are selected at one time and APP knows what to assign them as.
The files that APP spits out are labeled like this:
NGC_7635-Halpha-session_1.fits
NGC_7635-OIII-session_1.fits
NGC_7635-SII-session_1.fits
That is where the problem shows up because the one labeled as ObjectX-Halpha-session_x.fits is what shows as custom. The LRGB, Oiii, and Sii all are assigned what they are. I imagine it is in the combine RGB where the breakdown happens and it is related to it being called Halpha rather than Hydrogen Alpha since Halpha doesn't show up in the picklist there.
I've raised an RFC on this related topic https://www.astropixelprocessor.com/community/rfcs-request-for-changes/when-oiii-ha-extraction-creates-an-integration-set-filter-to-oiii-or-ha/
Essentilaly it would be good if the filter metadata is updated when creating these extracted Ha, Oiii and Sii images.
