Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.
May 27 2026 APP 2.0.0-beta45 has been released !
Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.
Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options
Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.
Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
I don't think this would work...(combining different image scales and pixel resolutions)
So, I've got this narrowband image shot on my tiny-sensored, high-pixel-count 183MM. I would like to shoot RGB stars and replace the whacko stars in the narrowband image.
The cropping is also actually a little too tight, so what I would really like to do is center the target and shoot the RGB frames with my APS-C DLSR. Bigger sensor, wider FOV. Register with NB with the RGB, save registered frames, run the NB through star elimination, integrate with MBB and LNC, boom, Astronomy Picture of The Day. (No, not really. I can dream.)
But I don't think APP will upscale the 16-megapixel APS-C image to match the 20-megapixel narrowband one when I register, or alternatively downscale the 20-MP one. Is that correct? (The respective image scales are about 0.6"/pixel and 0.3"/pixel). It would be really nice to just shoot OSC with a bigger sensor and have APP "make it so", but I suspect what I will wind up doing is either accept the too-tight cropping, or spend a lot of dark sky time on shooting a mosaic (and of course with all three broadband filters for each panel). I suppose I could also manually up- or down-scale one of the images to exactly correspond to the scale of the other -- assuming I could get the math right -- and import the result into APP for registration and continue that way.
If the DSLR thing could work, please let me know!
This topic was modified 3 years ago 2 times by Rick Wayne
APP is known to be able to register data that has a factor of 8x difference in imaging scale... your 0,6"/pixel with 0,3"/pixel is only a factor of 2, so I would think APP will do it without hesitation or problems 😉
So no need to do anything yourself. load the RGB data from your APS-c DSL and the 183mm data at the same time with their calibration data and set the registration engine to use dynamic distortion correction and disable same camera and optics, then it should work 🙂
Last year I made a mosaic of Orion + Flame and Horsehead. The combination was made with two different cameras, two different telescopes and a stupid overlap as the mosaic wasn't planned but more of a "hmm.. this could maybe work" thing.
The image consist of: Two sessions with an 80ED and a Canon EOS 5DMKII One session with an 80ED and a ha-modified Canon 700d (T5i) One session with a 2-panel mosaic using a Sharpstar 61EDPH and a ha-modified 700d (T5i)
Hey, that's brilliant! Thanks, nice to know not only that it should work but that it does.
I think I still might have to do a little fast shuffle to have the RGB image replace the stars in the narrowband one. But I could either register first, do star removal on the NB FITS, and then integrate normally.
Last year I made a mosaic of Orion + Flame and Horsehead. The combination was made with two different cameras, two different telescopes and a stupid overlap as the mosaic wasn't planned but more of a "hmm.. this could maybe work" thing.
The image consist of: Two sessions with an 80ED and a Canon EOS 5DMKII One session with an 80ED and a ha-modified Canon 700d (T5i) One session with a 2-panel mosaic using a Sharpstar 61EDPH and a ha-modified 700d (T5i)
The rejection-map was almost too funny:
Thanks @wheeljack for sharing this, that indeed looks funny 😉
@rickwayne, let us know if it works or need help 😉
