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.
Yes, calibration needs to be done with the same binning then as well.
Hi Vincent,
One thing that is not clear to me is whether amp glow is a problem in darks captured for creating a bad pixel map. Â Is it better to use long-exposure darks with visible amp glow? Or, are shorter exposure darks with little or no amp glow better to use (maybe with a greater number of them)?
Thanks
As far as I know, amp-glow is not a huge problem as the bad pixel map is a map of hot and cold pixels only. If you're unsure, I would just use one of your longest darks you have already and use that for the mapping.
Hello there, I have a question.Â
All of the discussion here focuses on creating the BPM from raw flat and dark frames.Â
If, instead, I have the master darks and master flats already created, my understanding was that, I could just load all the masters and create a BPM from them instead. Is that correct?Â
Is there any functional difference between the two methods?Â
The reason I ask is because I have the masters but not the raw frames.Â
Sorry if this has been asked and answered but:
- Does it matter which flats you use, as they would be potentially taken with different filters?
Yes that matters a lot. If you take, for instance, flats with an R filter and use them on B lights then the response of the sensor will be different which will introduce all kinds of artifacts in the calibrated image. Also the properties of at least a part of the optical train may differ when using different filters, especially small band versus broad band. In short: always take flats with the same filter as the lights that you want to calibrate.
Sorry, now a bit confused about creating a BPM in APP. I can find plenty of information about the type of darks (long exposure, warm camera etc.), but only indirect info about making the flats. As I understand it (only basic!), these flats are "generic", merely to give data about cold pixels.  So, am I wrong to assume that any recent flats from the camera (eg. diffuse light with histogram peak in the middle) will do? To clarify, this is only with regard to creating a BPM - appreciate the importance of a "full light path" for ordinary use of flats.Â
Thanks
Peter
PS Brilliant features in recent APP versions - thanks so much.
For the creation of a BPM, a regular good flat is fine yes. I would, I think, use a luminance flat then. Though I never used it for a BPM as cold pixels aren't a real issue anymore as far as I know.
Hi, the "Calibration" button is not on the 2) CALIBRATE section anymore, where did it move or is there a new way of creating a bad pixel map?
No, this hasn't been a button for a long time, it's called "Create masters and assign to lights". When you already have masters, they will simply be used and when you have no lights, the masters will be created. Might be nice to call the button a bit different maybe.
