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.
HI guys.
Does anyone know why I get this error? I recently got a new computer and I can't stack anything.
Â
What version are you using? And what kind of data and workflow do you use?
- @vincent-mod
- I'm using the latest version and normal workflow that I was using with my old computer and worked. On my old one I was using the 1.076.
- I'm using data from 2 setups, one with the extracted ha from an osc camera and one with the ha in mono but I've done it before on my old computer and 1.076 version and it worked just fine.Â
- Also it's sometimes freezing the computer to a state that I have to unplug it. I ran a stress test on the comluter and it passed just fine.Â
- I can't access app now as I'm running a memory test on the computer.Â
Trying to exclude any hardware issuesÂ
That is indeed sounding a bit like a hardware issue, but if all your tests don't reveal anything, I'll have to get a look at the data I think. Just to test if that isn't somehow also causing an issue now.
@vincent-mod
Finished all the tests, no errors at all so it can't be a hardware issue. I'll uninstall completely and reinstall the latest version.
I'll let you know if I still get the error.Â
Emil
Still not doing it.Â
It has something to do with the extracted Ha files from the OSC camera. If I remove them it seems to be working. But I don't know why it doesn't work as I've done it before on my old computer and it worked just fine. I've done 2 panels on a mosaic shot with both my setups. I shot with a Tri-band and a ha filter on the osc, I extracted the calibrated Ha from both of them and stacked them all together with the Ha subs shit with the mono camera.
If this was the first time I would do it, it would've been something else but I've done it before.Â
Can it be that the Ha from the osc camera was extracted on my old computer?Â
I had them all extracted before I got the new computer.Â
Emil
Â
- Trying to stack the files extracted on my old computer only to see if I'm still getting the error
I figured out what Ive done wrong. When I saved the calibrated frames to extract the Ha, I firgot to check the split channels box and that's why they couldn't be normalised.Â
Excellent research on your part Emil! Yes, that would be a problem as then it's still broadband data, combining that with narrowband for normalization is not possible. Mabula is working on making this a bit easier and even possible in a different way.
