<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Astro Pixel Processor Forum - Recent Topics				            </title>
            <link>https://www.astropixelprocessor.com/community/</link>
            <description>Astro Pixel Processor Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Sun, 26 Apr 2026 15:32:03 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>APP 2.0 beta 41 Registration error?</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/app-2-0-beta-41-registration-error/</link>
                        <pubDate>Sun, 26 Apr 2026 14:24:11 +0000</pubDate>
                        <description><![CDATA[What worked with beta39, seems not to work now.
Simple uncalibrated Sony a7RV file do not register right. A meridian flip happened inbetween. As can be seen of the reg. error in the screens...]]></description>
                        <content:encoded><![CDATA[<p>What worked with beta39, seems not to work now.</p>
<p>Simple uncalibrated Sony a7RV file do not register right. A meridian flip happened inbetween. As can be seen of the reg. error in the screenshot belwo, something is not good. When I tried to display a sub as registered, the below error message occured. Guess I will go back to version 39, where this did not matter</p>
10839
<p>&nbsp;</p>
<p>&nbsp;</p>
10840]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>elgol</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/app-2-0-beta-41-registration-error/</guid>
                    </item>
				                    <item>
                        <title>Still need to crop, if I use crop mode in integration?</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/still-need-to-crop-if-i-use-crop-mode-in-integration/</link>
                        <pubDate>Sun, 26 Apr 2026 10:22:05 +0000</pubDate>
                        <description><![CDATA[Hi all @mabula-adminNormally I use „full mode“ in 6)Integration, and subsequently crop the edges away to eliminate the dither/drizzle artefacts.Now I needed to use „crop mode“, to reduce the...]]></description>
                        <content:encoded><![CDATA[<p>Hi all @mabula-admin<br /><br />Normally I use „full mode“ in 6)Integration, and subsequently crop the edges away to eliminate the dither/drizzle artefacts.<br /><br />Now I needed to use „crop mode“, to reduce the TeraBytes of work files needed for my 1028 frames at drizzle scale 2.0 ;-)<br />--&gt; Question: are the edges clean, or do I still need to crop the artefacts away?<br />(I checked visually: looks as if there are no artefacts)<br /><br /></p>
<p>Thank you and best regards.</p>
<p>Michael </p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Michael Becker</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/still-need-to-crop-if-i-use-crop-mode-in-integration/</guid>
                    </item>
				                    <item>
                        <title>APP Beta 41 crashes on Windows 11.</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/app-beta-41-crashes-on-windows-11/</link>
                        <pubDate>Sun, 26 Apr 2026 07:43:17 +0000</pubDate>
                        <description><![CDATA[I purchased a set from Insight Observatory: 58 Red, 58 Green, 58 Blue, 58 Luminance Master flats and master bias. APP Beta 41 shut down whilst at 71% during the integration phase. When I tri...]]></description>
                        <content:encoded><![CDATA[<p>I purchased a set from Insight Observatory: 58 Red, 58 Green, 58 Blue, 58 Luminance Master flats and master bias. APP Beta 41 shut down whilst at 71% during the integration phase. When I tried a second time, it shut down at 63%. I installed Beta 39 and tested it; it worked normally.<br /><br />Windows 11 Pro 25H2<br />13th Gen Intel Core i7-13700H (2.40 GHz)<br />64-bit operating system, x64-based processor<br />Storage 2.73TB<br />RAM 64GB<br /><br /></p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Volkan ÖVÜN</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/app-beta-41-crashes-on-windows-11/</guid>
                    </item>
				                    <item>
                        <title>Beta39-Beta41 Failing - errors, warnings, blank result</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/beta39-beta41-failing-errors-warnings-blank-result/</link>
                        <pubDate>Sat, 25 Apr 2026 19:38:38 +0000</pubDate>
                        <description><![CDATA[Wow, this is the first time I&#039;ve run across a processing problem with APP and its no fun. I&#039;m trying a stack of 13 of 66 lights and got numerous messages and the final stack was blank. I&#039;ve ...]]></description>
                        <content:encoded><![CDATA[<p>Wow, this is the first time I've run across a processing problem with APP and its no fun. I'm trying a stack of 13 of 66 lights and got numerous messages and the final stack was blank. I've attached the series of screens to show what happened. I believe the last beta I tried that worked was Beta38. I tried trashing the old app and re-install Beta41 and these are the results - I have 50GB free space on my drive - all APP settings have been reset to default - Macbook Air on OS26.3.1 (Tahoe).</p>
10832
10833
10834
10835
10836
10837]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>astrogee</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/beta39-beta41-failing-errors-warnings-blank-result/</guid>
                    </item>
				                    <item>
                        <title>Star Colour saving causes computer freeze.</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/star-colour-saving-causes-computer-freeze/</link>
                        <pubDate>Fri, 24 Apr 2026 16:21:24 +0000</pubDate>
                        <description><![CDATA[Hi, When calculation of new star colour calibration is ongoing, pressing &quot;OK &amp; SAVE&quot; causes the computer to freeze and inevitably have to restart APP. It happens already a long time (pre...]]></description>
                        <content:encoded><![CDATA[<p>Hi, When calculation of new star colour calibration is ongoing, pressing "OK &amp; SAVE" causes the computer to freeze and inevitably have to restart APP. It happens already a long time (previous versions too)</p>
10830
<p>and when you know it you just wait for APP to finish the calibration before saving the result. I think it can be simply circumvented by disabling the key until the program is ready. I am using APP version 2.0.0 beta 41 on a Mac mini M2-Pro processor.</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Mario Pinto</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/star-colour-saving-causes-computer-freeze/</guid>
                    </item>
				                    <item>
                        <title>error message during integration</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/error-message-during-integration/</link>
                        <pubDate>Fri, 24 Apr 2026 15:09:11 +0000</pubDate>
                        <description><![CDATA[I am trying to stack a very wide field of M42 region with a 135 mm lens.  To that, I have included an already stacked b33 and m42 for increased detail.  My system s super slow so I did not u...]]></description>
                        <content:encoded><![CDATA[<p>I am trying to stack a very wide field of M42 region with a 135 mm lens.  To that, I have included an already stacked b33 and m42 for increased detail.  My system s super slow so I did not use "mosaic mode" in register.  Actually the registration process went without a hitch but I got this message during integration (see attached).  FYI I'm using a Linux system (Mint).  Happy to include more information if that helps.  Thanks for your help!  Richard</p>
10829
<p>&nbsp;</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Richard Konrad</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/error-message-during-integration/</guid>
                    </item>
				                    <item>
                        <title>AstroPixelProcessor 2.0.0-beta41 Linux DEB did not start. These were the errors I encountered and how I fixed them</title>
                        <link>https://www.astropixelprocessor.com/community/linux/astropixelprocessor-2-0-0-beta41-linux-deb-did-not-start-these-were-the-errors-i-encountered-and-how-i-fixed-them/</link>
                        <pubDate>Thu, 23 Apr 2026 18:11:17 +0000</pubDate>
                        <description><![CDATA[Edit by Mabula: this is not a supported solution. If you have trouble installing on Linux, please first remove the old APP version and make a clean installation. The below issue is caused by...]]></description>
                        <content:encoded><![CDATA[<p><em>Edit by Mabula: this is not a supported solution. If you have trouble installing on Linux, please first remove the old APP version and make a clean installation. The below issue is caused by conflicting 3rd party libraries in the installation /libs directory.</em></p>
<pre contenteditable="false"># java.lang.module.FindException: Two versions of module jogl.all found in libs (jogl-all-2.4.0.jar and jogl-all-2.4.0-natives-android-aarch64.jar)
sudo rm /opt/AstroPixelProcessor/libs/jogl-all-2.4.0-natives-android-aarch64.jar \
        /opt/AstroPixelProcessor/libs/jogl-all-2.4.0-natives-linux-aarch64.jar \
        /opt/AstroPixelProcessor/libs/jogl-all-2.4.0-natives-linux-armv6hf.jar \
        /opt/AstroPixelProcessor/libs/jogl-all-2.4.0-natives-macosx-universal.jar \
        /opt/AstroPixelProcessor/libs/jogl-all-2.4.0-natives-windows-amd64.jar \
        /opt/AstroPixelProcessor/libs/jogl-all-2.6.0.jar
sudo mv /opt/AstroPixelProcessor/libs/jogl-all-2.4.0-natives-linux-amd64.jar \
        /opt/AstroPixelProcessor/libs/jogl-all-natives-linux-amd64-2.4.0.jar

# java.lang.module.FindException: Two versions of module gluegen.rt found in libs (gluegen-rt-2.4.0-natives-macosx-universal.jar and gluegen-rt-2.6.0.jar)
sudo rm /opt/AstroPixelProcessor/libs/gluegen-rt-2.4.0-natives-android-aarch64.jar \
        /opt/AstroPixelProcessor/libs/gluegen-rt-2.4.0-natives-linux-aarch64.jar \
        /opt/AstroPixelProcessor/libs/gluegen-rt-2.4.0-natives-linux-armv6hf.jar \
        /opt/AstroPixelProcessor/libs/gluegen-rt-2.4.0-natives-macosx-universal.jar \
        /opt/AstroPixelProcessor/libs/gluegen-rt-2.4.0-natives-windows-amd64.jar \
        /opt/AstroPixelProcessor/libs/gluegen-rt-2.6.0.jar
sudo mv /opt/AstroPixelProcessor/libs/gluegen-rt-2.4.0-natives-linux-amd64.jar \
        /opt/AstroPixelProcessor/libs/gluegen-rt-natives-linux-amd64-2.4.0.jar

# java.lang.module.FindException: Two versions of module ejml.all found in libs (ejml-one-0.44.1-SNAPSHOT.jar and ejml-all-0.41.jar)
sudo rm /opt/AstroPixelProcessor/libs/ejml-all-0.41.jar \
        /opt/AstroPixelProcessor/libs/annotations-23.0.0.jar \
        /opt/AstroPixelProcessor/libs/nom-tam-fits-1.16.0.jar

# java.lang.module.ResolutionException: Modules java.annotation and jsr305 export package javax.annotation to module ejml.zdense
sudo rm /opt/AstroPixelProcessor/libs/jsr305-3.0.2.jar \
        /opt/AstroPixelProcessor/libs/javax.annotation-api-1.3.2.jar

# java.lang.module.ResolutionException: Modules ejml.simple and ejml.all export package org.ejml.equation to module astropixelprocessor
sudo rm /opt/AstroPixelProcessor/libs/ejml-cdense-0.41.jar \
        /opt/AstroPixelProcessor/libs/ejml-core-0.41.jar \
        /opt/AstroPixelProcessor/libs/ejml-ddense-0.41.jar \
        /opt/AstroPixelProcessor/libs/ejml-dsparse-0.41.jar \
        /opt/AstroPixelProcessor/libs/ejml-fdense-0.41.jar \
        /opt/AstroPixelProcessor/libs/ejml-fsparse-0.41.jar \
        /opt/AstroPixelProcessor/libs/ejml-simple-0.41.jar \
        /opt/AstroPixelProcessor/libs/ejml-zdense-0.41.jar

# WARNING: OpenGL initialization failed with exception java.lang.UnsatisfiedLinkError: 'boolean jogamp.opengl.x11.glx.GLX.initializeImpl()'
sudo sed -i 's/-Djogamp\.gluegen\.UseTempJarCache=false/-Djogamp.gluegen.UseTempJarCache=true/' /opt/AstroPixelProcessor/AstroPixelProcessor</pre>
<br />
<p>&nbsp;</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Hans</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/linux/astropixelprocessor-2-0-0-beta41-linux-deb-did-not-start-these-were-the-errors-i-encountered-and-how-i-fixed-them/</guid>
                    </item>
				                    <item>
                        <title>LNC2FirstDegree Error</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/lnc2firstdegree-error/</link>
                        <pubDate>Wed, 22 Apr 2026 17:21:46 +0000</pubDate>
                        <description><![CDATA[Hello everyone, I am new to APP. I am using the latest beta release to stack a 2 panel mosaic with 50 lights per each panel, master flat, master dark and master bias.
I enabled LNC in the s...]]></description>
                        <content:encoded><![CDATA[10827
<p>Hello everyone, I am new to APP. I am using the latest beta release to stack a 2 panel mosaic with 50 lights per each panel, master flat, master dark and master bias.</p>
<p>I enabled LNC in the settings and the integration method used is 'average', local normalization rejection is enabled.</p>
<p>How can I resolve it without turning off LNC?</p>
<p>&nbsp;</p>
<p>Thanks,</p>
<p>Adi</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Manoj Venkata Aditya Vempati</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/lnc2firstdegree-error/</guid>
                    </item>
				                    <item>
                        <title>APP 2.0.0-beta41 crashes with Sony A7 IV .ARW on macOS 26.4.1 — native crash in arm_libRawConverter (getRawData)</title>
                        <link>https://www.astropixelprocessor.com/community/macos/app-2-0-0-beta41-crashes-with-sony-a7-iv-arw-on-macos-26-4-1-native-crash-in-arm_librawconverter-getrawdata/</link>
                        <pubDate>Mon, 20 Apr 2026 01:49:55 +0000</pubDate>
                        <description><![CDATA[Hi all,
Getting a reproducible hard crash in beta41 on my Sony A7 IV .ARW files. JVM aborts and the window just disappears. Wanted to flag it here in addition to the email I sent to support...]]></description>
                        <content:encoded><![CDATA[<p class="font-claude-response-body break-words whitespace-normal leading-">Hi all,</p>
<p class="font-claude-response-body break-words whitespace-normal leading-">Getting a reproducible hard crash in beta41 on my Sony A7 IV .ARW files. JVM aborts and the window just disappears. Wanted to flag it here in addition to the email I sent to support (with the .ips files attached).</p>
<p class="font-claude-response-body break-words whitespace-normal leading-"><strong>Setup:</strong> macOS 26.4.1, Apple Silicon (MacBook Pro 18,3), APP 2.0.0-beta41 on GraalVM 24.0.1+9.1. Shot on Sony A7 IV, 14-bit ARW, ISO 8000, 4 s subs. 51 lights / 15 darks / 16 flats of comet C/2025 R3 (PanSTARRS).</p>
<p class="font-claude-response-body break-words whitespace-normal leading-"><strong>What I've tried:</strong></p>
<ul class=":mb-0 :mt-1 :gap-1 :pb-1 :pb-1 list-disc flex flex-col gap-1 pl-8 mb-3">
<li class="whitespace-normal break-words pl-2">Full set (lights + darks + flats), defaults on 2) CALIBRATE → "create Masters &amp; assign to Lights" → crash every time, 5-10 s in.</li>
<li class="whitespace-normal break-words pl-2">Lights-only (no darks/flats). Got past master generation / assign a couple of times, but then crashed at 3) ANALYSE STARS instead. Same signature.</li>
<li class="whitespace-normal break-words pl-2">RAM slider at default (512 MB) and at max — same crash either way, so it doesn't look memory-related.</li>
<li class="whitespace-normal break-words pl-2">Cmd+Q and relaunch between attempts.</li>
</ul>
<p class="font-claude-response-body break-words whitespace-normal leading-"><strong>Crash signature</strong> (from the .ips):</p>
<ul class=":mb-0 :mt-1 :gap-1 :pb-1 :pb-1 list-disc flex flex-col gap-1 pl-8 mb-3">
<li class="whitespace-normal break-words pl-2">Exception Type: EXC_BAD_ACCESS (SIGABRT)</li>
<li class="whitespace-normal break-words pl-2">Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000008188</li>
<li class="whitespace-normal break-words pl-2">Triggered by Thread 75 (Java: pool-91-thread-1)</li>
<li class="whitespace-normal break-words pl-2">Crashing frame: <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded- px-1 py-px text-">arm_libRawConverter.jnilib  Java_com_ariesproductions_rawConversion_LibRawConverter_getRawData + 344</code></li>
</ul>
<p class="font-claude-response-body break-words whitespace-normal leading-">The crash is in the native raw decoder (<code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded- px-1 py-px text-">getRawData</code>), and the fact that it also crashes at analyse-stars with lights-only lines up — star analysis re-reads each light through the same decoder. Looks like a null-pointer deref at a small struct offset (0x8188), which feels like a header/metadata parsing issue specific to these ARWs.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-">Anyone else seeing this? Happy to send sample .ARWs if it helps repro.</p>
<p class="font-claude-response-body break-words whitespace-pre-wrap leading-">Thanks, Gwen</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Gwen Cruise</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/macos/app-2-0-0-beta41-crashes-with-sony-a7-iv-arw-on-macos-26-4-1-native-crash-in-arm_librawconverter-getrawdata/</guid>
                    </item>
				                    <item>
                        <title>Beta-41 Comet Registration Issues</title>
                        <link>https://www.astropixelprocessor.com/community/comet-registration-and-integration/beta-41-comet-registration-issues/</link>
                        <pubDate>Sun, 19 Apr 2026 20:57:51 +0000</pubDate>
                        <description><![CDATA[First of all, my hat is off to all of those at Aries who have made beta-41 so fast and efficient.  I am amazed at how much faster it runs as compared to earlier versions. Well done!
I have ...]]></description>
                        <content:encoded><![CDATA[<p>First of all, my hat is off to all of those at Aries who have made beta-41 so fast and efficient.  I am amazed at how much faster it runs as compared to earlier versions. Well done!</p>
<p>I have a question and potential bug (or user error) when attempting to stack comets near dawn, when there are precious few stars peeking through the morning sky.  I imaged the comet Saturday morning April 18 2026.  APP Star Analysis indicated 8-20 stars available depending upon the frame - a very low star count, I know.  When I forged ahead to Registration using Comet mode or Normal mode, it completed 35 of 36 registration tasks and just hung there.  For hours.  In Comet Mode, it never even moved on to selecting the comet nucleus.</p>
<p>Am I doing something incorrect, process-wise?  Is this too few stars for APP to even attempt it?  Or is this a potential software issue?  This may not be the world's best comet data, but I'd like to see what I can make of it.  At the very least, it would be useful to get a warning error if this is something APP cannot complete.  I attach a screen shot and logs.  Thank you for your consideration and keep up the excellent work!</p>
<p>Regards, Martin Jordan </p>
<p>San Diego, California</p>
10822
10821
<p>&nbsp;</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Martin Jordan</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/comet-registration-and-integration/beta-41-comet-registration-issues/</guid>
                    </item>
							        </channel>
        </rss>
		