Share:
Notifications
Clear all

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.

[Solved] What is this?

3 Posts
3 Users
0 Reactions
4,669 Views
 Arie
(@arie)
Molecular Cloud
Joined: 9 years ago
Posts: 1
Topic starter  

I just installed APP and am trying to create a stack of 100 subs.

At the integration phase I get this:

 

APP errorscreen

 

Arie


This topic was modified 8 years ago by Mabula-Admin

   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

Seems like a Java error. I notice you're using a temp directory, is this located somewhere with limited space? If so, could you try it on a different location and with the latest APP 1.072 version?



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 10 years ago
Posts: 5468
 
Posted by: Arie

I just installed APP and am trying to create a stack of 100 subs.

At the integration phase I get this:

 

APP errorscreen

 

Arie

Hi @arie & @vincent-mod,

Thank you Arie for reporting the issue.

Please check the release notes of APP 1.072 ;-), this bug mainfests itself on integration on certain external drives and it is apparantely caused by IO errors on the Operating System level. In APP 1.072 this bug is caught so it should not happen again.

https://www.astropixelprocessor.com/community/release-information/astro-pixel-processor-1-072-ready-for-download/

FIXED, Integration MemoryToFileMapper, in some cases, a Buffer Underflow exception could occur while integrating frames. This seemed to happen only very infrequently, mostly with very large datasets (100s of frames)  and usually an external harddrive was involved. It was reported to happen on both MacOS and Windows, not on Linux as far as I know. I have made several adjustments now to prevent the exception from happening and if it still does happen (due to an Operating System level IO error), it will be caught cleanly now so the integration can still continue. The issue was reported recently here : https://www.astropixelprocessor.com/community/main-forum/what-is-the-best-way-to-combine-multiple-sessions-over-time-other-then-redoing-all-every-time/#post-4991 Theoretically, there is also the possibility of a BufferOverflow Exception, but that never happened as far as I know, anyway, if it does happen, it will also be  caught cleanly now so the integration can still continue. Both exceptions should never occur again while integrating.

 

Kind regards,

Mabula


This post was modified 8 years ago by Mabula-Admin

   
ReplyQuote
Share: