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.
Astro Pixel Processor 2.0.0-beta33 release notes
Please check the release notes video on our official YouTube channel here:
- IMPROVED and FIXED, keep FITS HEADER TAGS from reference/source files including RA, DEC, FOCALLEN, XPIXSZ, YPIXSZ, DATE-OBS etc...
As mentioned in several topics like this one https://www.astropixelprocessor.com/community/rfcs-request-for-changes/include-more-fits-header-information-in-the-integration/#post-31871 , whenever APP would make a new FITS file, old FITS tags from the reference or source file would be lost like the RA and DEC coordinates of the object in the image. This is now fixed for the entire application. Calibration masters will still have all the information from the capture software like gain and sensor offset if present, integration files will have all the distinct FITS tags from the reference frame which should make sure that all information is correct like the RA and DEC coordinates. And saving FITS files in all tools will keep the original FITS header tags that APP will not add itself. The FTIS header will have a note that indicates when the transferred tags start from the source/reference file: HDU1 - NOTE-XX = 'Distinct header tags from the original/reference frame follow below'Â
See the below screenshots for the FITS headers that APP will now produce keeping the distinct FITS tags from the reference or source FITS files. Also note the addition of FILTER tag and FRAMETYP tags as described in the release notes below:
- IMPROVED APPLICATION STARTUP behaviour
2.0.0-beta32 had slower startup time compared to older APP 2.0.0-beta versions due to a changed development platform setting, we have adjusted this now to give the same and smoother startup behaviour as earlier.
- FIXED FITS HEADER FILTER tag
As pointed out here https://www.astropixelprocessor.com/community/main-forum/encountered-error-in-module-combinenewbufferedimage-with-16-panel-mosaic/#post-29125 APP would not save the FILTER tag in the FITS header of FITS files that are created by APP. This is now fixed, also for stacking multiple filters into 1 integration FITS file.
- ADDED FITS HEADER IMAGETYP tag
We have added the IMAGETYP tag to the FITS header of fits files produced by APP. This should help other applications understand the frame type, like MasterDark, MasterFlat etc...
Â
- IMPROVED LICENSE and SETTINGS
We have removed the top left LICENSE and CFG buttons and replaced it with a new single button LICENSE & SETTINGS. The reason for the change is that the CFG button was not very intuitive and thus not all APP users were aware that you can change/enable/disable several application wide settings like the popup menus with instructions or having the image viewer in it's own separate window. We have also added 3 separate buttons in the new menu to reset settings and all menus from 0) RAW/FITS to 6) INTEGRATE easily to it's defaults which can be usefull in some cases. Please note that all these settings and menus are now saved and thus remembered with an APP restart. Your License information and management can be accessed with the LICENSE management button inside this new menu. The below screenshot shows the new button and the new menu. We think that this new button and it's new menu will make things easier and more intuitive.
- FIXED/IMPROVED LICENSE ACTIVATION
We have improved the license activation experience and it's activation window and have also removed a bug relating to failed license activation. If a faulty license was added, in some cases, the user was not warned about the failed activation, this is now fixed. The below screenshot shows the new license activation window:
- IMPROVED DeepSky Object Name in 0) LOAD
If the reference frame is a FITS file and if it contains the FITS OBJECT tag, that OBJECT tag name is used automatically for the Deepsky Object name, but you can still overrule it when you start the integration in 6) Integrate.
- FIXED READ support for TIFF from Celestron Origin telescope
As mentioned here https://www.astropixelprocessor.com/community/camerasupport/has-anyone-successfully-stacked-files-from-celestron-origin/#post-32264 APP would throw a ArrayIndexOutOfBoundsException while trying to read the FinalStackedMaster.tiff produced by the Celestron Origin telescope. This image is the automatically stacked image by the telescope. APP can now read these TIFFs without problems.
- FIXED Weird horizontal lines on macOS with big field of views
The fix in 2.0.0-beta32 for ArrayOutOfBoundsException in Integrator also has fixed the issue on macOS where weird horizontal lines would manifest in integrations of big Fields of View, like big mosaics. It was mentioned in 2 topics: https://www.astropixelprocessor.com/community/main-forum/strange-horizontal-lines-in-mosaic-integrations/#post-28274 and https://www.astropixelprocessor.com/community/appreleases/image-artefacts-on-multipanel-mosaic-2-0-0-beta17/#post-28039 Â
Â
