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.
Good morning I updated the other week to version 1.082 and I'm not sure if that is the problem but since then whenever I upload a set of files at the end of the integration I'm left with a completely dark file. I have tried different sets of lights, Darks, Flat and Flatdarks with different exposures times and even completely different sets from another camera and it all leads to the black frame at the end. Anyone know if this is a fault with 1.082 as it has never happened before.
It shouldn't be the case no, so this never happened with the earlier version? Could you try switching off OpenGL (green GL button on top of APP)?
I'm also guessing that "DDP" on the right hand side is switched on (should be, as that's standard)?
@vincent-mod
- hi, Yes DDP is ticked. No it never happened before. I was in openGL4 I believe. Do you want me to run it all again in CPU or just click the button to change to that?
Just click the button and load in the image, just to see if something may have changed on your computer (maybe an update) that is messing with the graphics driver.
Hi
no that didn’t change anything. Strangely I have just run again with darks and it loads as normal. This I find very strange because like I said I have tried it with 4 different targets which had 4 different exposure times all with the core that matching frames and it hasn’t worked. This is on two different camera sets. I can’t believe for one minute all of a sudden my darks for each exposure time and each camera have mysteriously stopped working????
No that wouldn't make sense. Did you restart APP when it started working again? It could be there was a setting that interfered somehow.
No that wouldn't make sense. Did you restart APP when it started working again? It could be there was a setting that interfered somehow.
Hi, Yes tried it after a restart and a power down but still the same. Maybe I should try deleting APP and reloading again?
We do have 1.083beta which is working for many as well if you want to update to that, though I haven't seen this particular issue with 1.082. Maybe worth a try anyway.
We do have 1.083beta which is working for many as well if you want to update to that, though I haven't seen this particular issue with 1.082. Maybe worth a try anyway.
What I am also going to try is on my other computer I have V1.081 so will try the same set of files on that and see what happens
So I have ran it all on Version 1.081 on my other computer and all is fine. So will delete version 1.082 and try either the new beta or the older 1.081
A good test would also be to see if 1.081 runs on this computer, just to see if it's a computer issue somehow.
A good test would also be to see if 1.081 runs on this computer, just to see if it's a computer issue somehow.
Right Now I'm confused. the set of frames runs perfectly fine on my other iMac on V1.081 so I then deleted the Version 1.082 from this computer and re-installed version 1.081 and tried again and I still get the black frame at the end of integration.
Is there a proper way to completely uninstall APP , or do I just delete the App and empty the trash?
@richardhurst How do you exactly start APP? Do you go to Launchpad and start APP from there? Or do you open Finder, go to the Applications folder and double click the APP app? If the first, can you try the second way? Perhaps Launchpad got confused somehow.
Removing APP indeed is as simple as removing the app folder and emptying the Bin.
@richardhurst How do you exactly start APP? Do you go to Launchpad and start APP from there? Or do you open Finder, go to the Applications folder and double click the APP app? If the first, can you try the second way? Perhaps Launchpad got confused somehow.
Removing APP indeed is as simple as removing the app folder and emptying the Bin.
Hi I always just open the applications folder and then open APP. I have deleted it again and then re-installed but its still doing it. Th only other thing I have done on the computer is a time machine restore but I cannot see who that would effect things as I only restored to a previous state two days ago
If it only happens on that computer, it must be something on the system itself causing an issue. It's however very difficult in such a situation to figure out why unfortunately. Maybe some system setting was not recovered properly by the time machine... can be a lot of things.
@richardhurst Would you be willing to try and install 1.082 on the other computer and see if you get the black integration there as well?
@richardhurst Would you be willing to try and install 1.082 on the other computer and see if you get the black integration there as well?
I can do, will do it now and fingers crossed i don't lose the use of that one as well 🙂
@richardhurst Would you be willing to try and install 1.082 on the other computer and see if you get the black integration there as well?
Hi right i have updated to 1.082 and now this has also given me the black frame at integration also. Just to confirm it worked fine on 1.081 on this computer
Could it be you, maybe, used different calibration data at first when it did work on that computer? (what happens when you integrate without any calibration data)
Could it be you, maybe, used different calibration data at first when it did work on that computer? (what happens when you integrate without any calibration data)
No I have used the exact same data through out. working fine on 1.081 and then upgraded as suggested to 1.082 and now same result as other computer
Could you try without calibration data? If that also doesn't work we'd like to take a look ourselves a the dataset, might be something we could fix.
Could you try without calibration data? If that also doesn't work we'd like to take a look ourselves a the dataset, might be something we could fix.
If I run just a set of lights it loads fine
Will now try Lights, Dark Flats, Flats and see what happens
@richardhurst So, what happens when you only integrate the lights and don't use the calibration data?
EDIT: sorry, I didn't see your earlier reply. Yes please try without darks and/or bias and let's see what happens.
@richardhurst So, what happens when you only integrate the lights and don't use the calibration data?
It loads an image fine after integration
Could you try without calibration data? If that also doesn't work we'd like to take a look ourselves a the dataset, might be something we could fix.
If I run just a set of lights it loads fine
Then we might have the issue. Must be a calibration problem, usually this happens with the darks. Could you run everything without the darks?
Could you try without calibration data? If that also doesn't work we'd like to take a look ourselves a the dataset, might be something we could fix.
If I run just a set of lights it loads fine
Then we might have the issue. Must be a calibration problem, usually this happens with the darks. Could you run everything without the darks?
Yes It again works with Lights, Flats, dark Flats
Excellent, so we don't know exactly why it first did work. But pretty sure the darks are having an issue. Many times, when people re-shoot those, it works again. Thanks for all the tests!
Excellent, so we don't know exactly why it first did work. But pretty sure the darks are having an issue. Many times, when people re-shoot those, it works again.
Hi, But why did the darks work an hour ago in 1.081?
