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.
Hello from Austria!
I'm having a problem calibrating my data. On my last project I shot lights with a Canon Ra connected to an ASIair. The data was saved as FITS. I was only able to record the calibration data in the camera's CR3 format.
In APP I can create the masters without any problems, but they don't correct the lights.
If I switch from "raw" to "calibrated" in the window, nothing changes even though I have assigned the masters to the lights!?
Can't FITS be calibrated with CR3?
CS Gernot
Hi Gernot @skanker,
That is a problem yes that has to do with image dimensions in both the FITS and CR3 format. They will probably be different and this is because AsiAir is cutting of the raw border of the CR3 data and putting that in the FITS files for capture. And the resulting FITS files will have smaller dimensions then the CR3 raws which still contain the raw border. Without knowing the cropping offsets that asiair does internally, we can not solve nor fix this. If you know the offsets, then we can fix this with the batch crop tool to make the images compatible and have calibration working on the correct pixels in the lights.
As a general rule it is good to keep in mind : always shoot calibration data in the same file format with the same software and same software version as your lights to prevent unexpected results.
Mabula
Hi Mabula!
Thanks for the explanation. I was able to immediately identify the problem with the image sizes in the APP. Unfortunately, due to a technical glitch, I was unable to record the calibration files after the session. I will now try to create the data retrospectively with the ASIair. Please keep your fingers crossed for me 🙂
Greetings from Austria
Gernot
