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-beta34 release notes
Please check the release notes video on our official YouTube channel here:
- UPDATED LibRaw for camera RAW support to LibRaw 202502 snapshot
We have updated LibRaw for camera RAW support from Libraw 0.21.1 to the latest 202502 snapshot which was released a couple of days ago. This update adds a lot of new camera models to APP's RAW support as described in the following release notes per camera brand.
- CANON CAMERA SUPPORT
the following models have been added to the Canon CR2/CR3 fully tested models: EOS M2, EOS R6 MARK II, EOS R8, EOS R50, EOS R100
- NIKON CAMERA SUPPORT
the following models have been added to the Nikon NEF fully tested models: 1 S2, 1 AW1, D2XS, Z50, D6, Z f, Z8, Z9. Note for Z f , Z fc, Z 8, Z 9 models : HE/HE* formats are not supported, standard/lossless compression only. LibRaw does not yet provide support for the High Efficiency or HE compression methods.
- SONY CAMERA SUPPORT
the following models have been added to the Sony ARW fully tested models: SLR-A390, ILCE-QX1, DSC-HX95, ILCE-6001 (Sony tweak), ILCE-7RM5, ILME-FX30, ILCE-6700, ZV-E1, ILME-FX3, ILCE-7CM2, ILCE-7CR, ILCE-9M3, UMC-R10C
Please note for models ILCE-7RM5, ILCE-7CR, ILCE-9M3 : Lossless compressed medium,small do not work, only Lossless compressed Large, Lossless Ucompressed and Lossy compressed works
- HASSELBLAD CAMERA SUPPORT
the following models have been added to the Hasselblad 3FR & fff fully tested models: CFV-50c, X2D-100c, L2D-20C, cfv 50C II, CF132
- PENTAX CAMERA SUPPORT
the following models have been added to the Pentax PEF fully tested models: K2000, KF
- PANASONIC CAMERA SUPPORT
the following models have been added to the Panasonic RW2 & RAW fully tested models: DC-S5M2, DC-S5M2X, DC-GH6, DC-TZ200D, DMC-FX150, DC-G9M2, DC-ZS200D, DC-TZ95D, DMC-GF8, DC-G95D, DC-TZ200
- OM DIGITAL SOLUTIONS CAMERA SUPPORT
the following models have been added to the OM DIGITAL SOLUTIONS fully tested models: OM-1MARKII, OM-5, TG-7
- OLYMPUS CAMERA SUPPORT
the following models have been added to the OLYMPUS fully tested models: E-10, E-20, E-20N, E-20P, E-M5, E-M10 Mark IIIs, E-P7, SP570UZ
- FUJIFILM CAMERA SUPPORT
the following models have been added to the Fujifilm RAF fully tested models: GFX100-II, X-S20, X100VI
- Fixed Fuji X-Trans RAF ArrayIndexOutOfBoundsException in ImageNormalizer
As mentioned here https://www.astropixelprocessor.com/community/main-forum/astro-pixel-processor-crashes-when-loading-fuji-raw-files/#post-32320 when trying to normalize light or flat frames from Fuji X-Trans RAF files, APP could throw an ArrayIndexOutOfBoundsException in the ImageNormalizer module. This bug has been fixed in calibration, normalization and integration.
- Fixed Fuji X-Trans raw crop offsets
For some of the Fuji X-Trans camera models, the raw crop offsets were not correct, creating visual artefacts at the image borders (left, top, bottom, right) like you can see in the screenshot below on the left side of the image, the next screenshot shows that this is now fixed properly. This fix applies to the X-Trans models X-T3, X-T30, X-T4, X-PRO3, X100V, X-S10, X-E4, X-T30, X-30, X-20. This fix uses different sensor offsets to crop the raw borders off and it will not affect your master calibration frames, so users with these camera models will still be able to use the old master calibration frames properly.
- FIXED 2)CALIBRATE, save RGB calibrated frames with split channels
As reported here https://www.astropixelprocessor.com/community/main-forum/error-in-beta-33-when-i-want-to-split-the-channels-after-stacking/ Â , 2.0.0-beta33 has a regression bug in the calibrated frames saver when you save with the option split channels enabled. This Null Pointer Exception has been fixed and saving with split channels works again.
- Fixed Fits save bug when date and time can not be found on a computer
In some rare cases, APP can error when a FITS file is saved, when the date and/or time can not be found on a computer for some reason. This is fixed now.
- FIXED SAVE FITS FROM ORIGINAL FITS WITH COMPRESSION
As reported here https://www.astropixelprocessor.com/community/main-forum/encounted-error-during-stacking-process/ APP could throw a ClassCastException in the linear/raw FITS image loader task, when it loads an image saved by APP produced from original FITS files with compression. This bug is a regression from the improvement that APP will now keep distinct header tags from original or reference fits files. This fix now ensures that all related FITS header tags for compression are removed from the original header before being merged with the APP fits header.
- FIXED NULLPOINTEREXCEPTION in REGISTRATIONTASK
As reported here https://www.astropixelprocessor.com/community/appreleases/reproducible-error-during-registration-process-beta33/#post-32303 in very rare cases, APP could throw a Null Pointer Exception in the RegistrationTask. The issue is likely caused by a frame with no stars in it, or simply a corrupt file. APP will now check for this Null Pointer and will simply abort the regisration task on that particular frame/file.
