30 July 2020 - APP 1.083-beta1 has been released introducing Comet processing! This 1st beta has comet registration. The stable release will also include special comet integration modes.
9 July 2020 - New and updated video tutorial using APP 1.081: Complete LRGB Tutorial of NGC292, The Small Magellanic Cloud by Christian Sasse (iTelescope.net) and Mabula Haverkamp
2019 September: Astro Pixel Processor and iTelescope.net celebrate a new Partnership!
Windows 64 bit - APP glitchy
I'm not able to use APP at all - I'm not sure why it does this but after a minute or so of the program being open it glitches like this. the screens just follow my mouse curser and make it impossible to use.
Interesting, I've not seen this before. What are the specs of your system, including the kind of gfx card?
I get this also after I created a folder on the desk top specifically to use pics for APP. The folder is empty so far as I have no data in there to use, bad weather so no astro. I did use another folder with data in it of older pics already processed and it did not screen duplicate. So maybe due to no data in the specified data may make a problem. I have a 1080 TI graphics card
I get this exact same behaviour (v1.082), makes the program unusable and evaluating the trial almost impossible 🙁
Win 10 64bit
NVidia RTX 2080 GPU
makes me wonder if it is going to do it after the trial period? Don't think I will trust that it won't. Probably won't get this and go for Pixinsight
@bluknght I think you are right when you say it is related to opening a folder (possibly an empty one) - every time this has happened it occurs as I am opening a folder to select files.
I think this is a problem with the the latest gfx cards, I believe the drivers, Mabula knows about it and is trying to fix it.
only got a few left on the trial, I tried again today using this program and still put up multiple screens. I think it's an open GL problem. Pitty as I was looking forward to using this. Back to using photoshop for now
Sorry for the inconvenience, please check back later as we’re hoping to solve this issue of course.