Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.
It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
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.
Hi,
Â
I wonder if it is still the problem why I cannot process the stacks when having this error:
the data is big, HaLRGB each 1.4 billion pixels and the PC has 128gb RAM, so that should be enough...
Â
e.
Â
I don't think there is a size limit per-se no, but it does require more memory than just for the data itself, it also consumes some for the processing. Are you using beta 13? That at least uses less overall.
I don't think there is a size limit per-se no, but it does require more memory than just for the data itself, it also consumes some for the processing. Are you using beta 13? That at least uses less overall.
Mabula said sth like that a while ago. Sure beta13 it is. It are 5 files for HaLRGB combining about 6gb each file, about 1.4 billion pixels each... I had this topic up here before but having a new fast PC I thought give this monster mosaic another try
Â
Mm, I'll ask him then, it may be of course, let me check.
So, there actually isn't a real limit memory-wise (APP usually uses to 95% or so of total memory), but Java may have a limit on the amount of pixels. Can you tell me what kind of camera/sensor you're using? ps. to address this we are having this on our list of to-do items.
So, there actually isn't a real limit memory-wise (APP usually uses to 95% or so of total memory), but Java may have a limit on the amount of pixels. Can you tell me what kind of camera/sensor you're using? ps. to address this we are having this on our list of to-do items.
It's a 6200mm, but like I said it is a mosaic and the mono stacks APP did fine, just the RGB combine tool results in this error. Pixinsight does this job, but for example cannot export a tiff of this, since there seems to be a 4gb size limit to tiffs. looks like there is a lot still having to arrive to the 21st century
Â
Â
@vincent-mod any news here?
Hi @elgol & @vincent-mod,
We still have a limit due to a constraint in our development platform unfortunately. The limit is that a picture object can not have more than 2^31 pixels which is roughly 2 Giga pixels. This limit means that a monochrome image can be up to this limit in pixels. But for a multi-channel image, an RGB image, that limit must be divided over each channel, so each channel can then only have 2GB / 3 = roughly 700 Million pixels.
We have this on our ToDo list of course to fix and I hope to work on this soon after the 2.0 stable release in combination with an comprehensive update of the registration engine with better mosaic support.
Hope that clarifies it?
Mabula
Â
Hello everyone, Hello Mabula and Vincent.
I am currently working on a very, very large mosaic project as well. There are almost 2000 fields on an image the size of an AllSky.
The current state of APP does not allow to manipulate images with large dimensions without being blocked by software or hardware limitations, or without avoiding registration and assembly problems.
Like Elgol, the current hardware limitation is not systematically reached, I am - in the context of my project - rather limited by the software.
I am well aware that APP is already very good at handling relatively large fields, but it is not designed to handle so many fields. I currently have to "trick" and use other tools to achieve the desired level of objective for the project.
The arrival of a new version of registration and an increase in the maximum limit of image size could allow the field processing pipeline to be reviewed and further improved.
If APP can be a major tool in this project, I would be happy to let you know when it is published.
Do you have a rough estimate of when you would make this new feature available, as well as an estimate of the new maximum image size?
For Mabula: I sent you a private message in June 2022 on this forum, to tell you about the project. I remain available for discussion, if you would like to use my project data to help in the development of APP, if that would be useful, it would be my pleasure
