2026-10-09 APP 2.0.0-beta48 has been released !
This is mainly a bug fix release for the reported bugs in beta47. In addition it has a significant User Interface performance improvement noticable when you need to process 1000s of images in APP.
2026-10-03 APP 2.0.0-beta47 has been released !
This is a very big release... many code optimizations/rewrites, many parts of APP are much faster and more precise, especially star analysis and registration are much faster ! Big mosaics will go much faster 🙂
And we introduce a new preview filter, which includes the new Adaptive Deep Sky Stretch and a General Levels Stretch, this has been long over due. The old preview filter (the panel on the right side to stretch and preview your data) has not been updated for a couple of years and it is a critical part of any APP session.
Adaptive Deep Sky Stretch or ADSS is a much more intuitive stretch algorithm. It is also color preserving (which is a great new addition in itself ! ) which means that the highlights are no longer bleached, color is maintained from the linear data while stretching. You can simply stretch your data using the sky background level and signal width sliders which work much easier and more intuitive. You no longer need to fiddle with the old complicated sliders with zoom buttons. All the zoom buttons for the sliders are made redundant. And you can enter slider values in the slider value fields yourself. I will make a youtube video in the coming days to explain and fully introduce ADSS. Once the video is ready, it will be highlighted on the forum.
RGB Combine upgrade !. The RGB Combine Tool has been rewritten mostly. The tool is faster and easier to use and most importantly, the Luminance slider to inject a luminance channel or channels into the RGB composite is now working correctly. It no longer bleaches the RGB colors. Combined with the new ADSS preview, you will get much better and easier great composites with great color! I will also explain this in a new youtube video.
Good morning,
I'm using APP 1.075 beta4 to calibrate and integrate images taken on a Canon 5D MkIV DSLR and see this message during integration.
09:54:18 - 6) INTEGRATE: integrate light frames: wrote frame: 8 to file mapper
09:54:20 - GENERAL IMAGE LOADER: loading frame D:\Temp_workspace\200919 Veil Nebula\Lights\L__21B9042_ISO800_240s__24C.CR2
09:54:20 - 6) INTEGRATE: integrate light frames: loaded frame 9 of 36 frames
09:54:20 - GENERAL IMAGE LOADER: frame D:\Temp_workspace\200919 Veil Nebula\Lights\L__21B9041_ISO800_240s__24C.CR2 was loaded successfully
09:54:21 - 6) INTEGRATE: integrate light frames: LNC: got center coordinates and area of frame 9 in integration composition
09:54:22 - 2) CALIBRATE: Adaptive Data Pedestal: enabled
09:54:22 - 2) CALIBRATE: Adaptive Data Pedestal set at: 9.761E-03
09:54:22 - 2) CALIBRATE: WARNING !!! we have detected a possible sensor offset issue between the MasterBias and the Masterdark !
09:54:22 - 2) CALIBRATE: WARNING !!! the MasterBias has a median value of: 3.125E-02 for channel 1
09:54:22 - 2) CALIBRATE: WARNING !!! the MasterDark has a median value of: 3.112E-02 for channel 1
09:54:22 - 2) CALIBRATE: WARNING !!! normally, the median value of the MasterDark should be the same or larger than the median value of the MasterBias
09:54:22 - 2) CALIBRATE: WARNING !!! because a dark should always contain the entire bias signal plus the dark current and possible amp glow signals
09:54:22 - 2) CALIBRATE: WARNING !!! some CMOS sensors however exhibit this behaviour due to CMOS technology.
Details of the DSLR raw files are:
40 x 240 second Lights, 20 x Flats, 20 x Darks, 50 x Bias. Everything was shot at iso800 and same sensor temperature
Anything I should be doing different during the calibration or is this message fairly typical?
best regards
Kev
Hello.
Â
I have the same console message.Â
Â
MBP, OS Mojave
APP 1.075 beta4
Canon 60d, ISO 800
Lights 17x 360s
Darks 26x 360s
Bias 40x 1/125s
Flats 40x 1/13s
DarkFlats 40x 1/13s
Â
What is wrong?
Â
Best regards
Mariusz
Â
Â
Nothing, it is a warning, however the values are the same or very close to being the same. It shouldn't impact the result.
Nothing, it is a warning, however the values are the same or very close to being the same. It shouldn't impact the result.
Thank you Vincent. I'll continue to ignore it 🙂