<?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>Tue, 16 Jun 2026 01:44:17 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>FOV Size Preventing Integration</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/ram-error-failure-on-integration/</link>
                        <pubDate>Mon, 15 Jun 2026 14:24:04 +0000</pubDate>
                        <description><![CDATA[Hi, complete non-tech savvy newbie here. 
I have a Vaonis Vespera Pro.
I attempted my first stack with APP and failed at the integration stage.  I received three consecutive error messages...]]></description>
                        <content:encoded><![CDATA[<p>Hi, complete non-tech savvy newbie here. </p>
<p>I have a Vaonis Vespera Pro.</p>
<p>I attempted my first stack with APP and failed at the integration stage.  I received three consecutive error messages all referrring to insufficient RAM.  I have 32 GB of RAM which I know ordinarily to be enough.  I tried reducing the scale right down but this did not solve the issue.  After the third error message there is a bell sound and the integration fails.  </p>
I then checked the FOV size and it was utterly ginormous, millions x millions, clearly hence the problem.<br />
<p>I then changed to a completely diffrent data set for a different target.  This time the FOV size was 10000 x 11000 and would have needed 805 GB of hard disk space to integrate.</p>
<p>I seem to have a problem with the FOV size post Registration.</p>
<p>Can somebody please help as I cannot get beyond registration currently due to the FOV size.</p>
<p>Thank you</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Philip Dicken</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/ram-error-failure-on-integration/</guid>
                    </item>
				                    <item>
                        <title>Total Beginner Question</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/total-beginner-question/</link>
                        <pubDate>Mon, 15 Jun 2026 10:25:33 +0000</pubDate>
                        <description><![CDATA[I&#039;m having a hard time finding my stacked/registered image. I&#039;ve managed to load the frames, set the &quot;save directory&quot; to a folder on my desktop, registered them, then APP makes the &quot;gong&quot; so...]]></description>
                        <content:encoded><![CDATA[<p>I'm having a hard time finding my stacked/registered image. I've managed to load the frames, set the "save directory" to a folder on my desktop, registered them, then APP makes the "gong" sound but no image shows in APP or is saved to the folder I set the save directory to. Where is the stacked/registered image? I've looked through a few tutorials but I think this question is so basic no one covers it. Thx for your help.</p>
10932
<p>&nbsp;</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>jay frontierro</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/total-beginner-question/</guid>
                    </item>
				                    <item>
                        <title>background green color</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/background-green-color/</link>
                        <pubDate>Sun, 14 Jun 2026 16:50:26 +0000</pubDate>
                        <description><![CDATA[Hi
&nbsp;

The attached stacked image is produced by stacking 60 frames with dark, bias and flat using an ASI 2600MC and Celestron edge 11&quot;. As you can see the image is dominated by an in...]]></description>
                        <content:encoded><![CDATA[<p>Hi</p>
<p>&nbsp;</p>
10931
<p>The attached stacked image is produced by stacking 60 frames with dark, bias and flat using an ASI 2600MC and Celestron edge 11". As you can see the image is dominated by an intense green color difficult rot remove in post processing. If I check the "neutralize background box , the background turns red. Can you please help?</p>
<p>sandro</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>sandro Gambarotta</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/background-green-color/</guid>
                    </item>
				                    <item>
                        <title>Allow the lights scheme to be saved</title>
                        <link>https://www.astropixelprocessor.com/community/rfcs-request-for-changes/allow-the-lights-scheme-to-be-saved/</link>
                        <pubDate>Sun, 14 Jun 2026 15:56:52 +0000</pubDate>
                        <description><![CDATA[Today it happened to me again: while I was integrating 2000 lights, the computer suddenly crashed, and I had to close the app. The problem does not rely solely on the crash, but there is no ...]]></description>
                        <content:encoded><![CDATA[<p>Today it happened to me again: while I was integrating 2000 lights, the computer suddenly crashed, and I had to close the app. The problem does not rely solely on the crash, but there is no option to save the scheme of lights, darks, and bias... then everything is lost. You should have the option to save the entire integration skeleton of the different sessions so that even if the APP is closed, only one can reopen it and everything is ready to reintegrate. I hope this option is taken into account.</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>hector Duran</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/rfcs-request-for-changes/allow-the-lights-scheme-to-be-saved/</guid>
                    </item>
				                    <item>
                        <title>Star shape and quality metrics aren&#039;t adjusted for different pixel size</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/star-shape-and-quality-metrics-arent-adjusted-for-different-pixel-size/</link>
                        <pubDate>Wed, 10 Jun 2026 22:29:01 +0000</pubDate>
                        <description><![CDATA[When combining images from different scopes, the images need to be combined with some magnification adjustments to match different scope focal lenghts. I think this also requires the star sh...]]></description>
                        <content:encoded><![CDATA[<p>When combining images from different scopes, the images need to be combined with some magnification adjustments to match different scope focal lenghts. I think this also requires the star shape and quality metrics to be adjusted accordingly.</p>]]></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/star-shape-and-quality-metrics-arent-adjusted-for-different-pixel-size/</guid>
                    </item>
				                    <item>
                        <title>NullPointerException in Batch Crop</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/nullpointerexception-in-batch-crop/</link>
                        <pubDate>Mon, 08 Jun 2026 16:13:28 +0000</pubDate>
                        <description><![CDATA[HelloI keep getting the following error when I batch crop images; typically they are normalized Broadband (OSC) and Narrowband (dual NB) Fit files. This started to occur at beta44 (wasn&#039;t a ...]]></description>
                        <content:encoded><![CDATA[<p>Hello<br /><br />I keep getting the following error when I batch crop images; typically they are normalized Broadband (OSC) and Narrowband (dual NB) Fit files. This started to occur at beta44 (wasn't a problem before) and it is still there in beta45. It occurs NOT during the crop but during the save... Here is the error in beta44:<br /><br />---<br />Astro Pixel Processor - 2.0.0-beta44<br />Oracle JDK 26.0.1 - Windows-64-bit<br /><br />Encountered error in module: <br />FileDetailListUpdater<br /><br />Error message: <br />java.lang.NullPointerException: Cannot invoke "String.equals(Object)" because "this.a" is null<br /><br />Cause: <br />Cannot invoke "String.equals(Object)" because "this.a" is null<br />astropixelprocessor@2.0.0-beta44/com.ariesproductions.frameDetails.t.a(FileDetailListUpdater.java:437)<br />astropixelprocessor@2.0.0-beta44/com.ariesproductions.frameDetails.t.doInBackground(FileDetailListUpdater.java:39)<br />java.desktop/javax.swing.SwingWorker$1.call(Unknown Source)<br />java.base/java.util.concurrent.FutureTask.run(Unknown Source)<br />---<br /><br />Please note, however, that as far as I can tell, the crops appear to have been successful. <br /><br />Here is the log portion (I added the "arrows"):<br />---<br />11:57:24 - Batch crop tool: processed frame 2 of 3 frames - W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\03 Crop\IC_5070_A-Multi-NB-Ha-02_graxpert_Prism-crop.fits<br />11:57:24 - Batch crop tool: processing frame 3 of 3 frames...<br />11:57:24 - GENERAL IMAGE LOADER: loading frame W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\02 Grax Prism\IC_5070_A-Multi-NB-O3-02_graxpert_Prism.fits<br />11:57:24 - FITS FRAME SAVER: W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\03 Crop\IC_5070_A-Multi-NB-Ha-02_graxpert_Prism-crop.fits : finished successfully<br />11:57:24 - GENERAL FRAME SAVER: null : finished successfully<br />11:57:25 - GENERAL IMAGE LOADER: frame W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\02 Grax Prism\IC_5070_A-Multi-NB-O3-02_graxpert_Prism.fits was loaded successfully<br />11:57:26 - GENERAL FRAME SAVER: file name: IC_5070_A-Multi-NB-O3-02_graxpert_Prism-crop<br />11:57:26 - GENERAL FRAME SAVER: directory: W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\03 Crop<br />11:57:26 - GENERAL FRAME SAVER: file type: FITS<br />11:57:26 - GENERAL FRAME SAVER: bit depth: 32 bits floats<br />11:57:26 - GENERAL FRAME SAVER: DPI (Dots Per Inch): 72<br />11:57:26 - GENERAL FRAME SAVER: ICC profiles: Linear Gray<br />11:57:26 - GENERAL FRAME SAVER: W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\03 Crop\IC_5070_A-Multi-NB-O3-02_graxpert_Prism-crop.fits : starting...<br />11:57:26 - GENERAL FRAME SAVER: performing bitdepth conversion if required...<br />11:57:26 - IMAGE CONVERTER: image conversion not needed, data is already normalized...<br />11:57:26 - GENERAL FRAME SAVER: W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\03 Crop\IC_5070_A-Multi-NB-O3-02_graxpert_Prism-crop.fits : starting FITS FRAME SAVER<br />11:57:26 - FITS FRAME SAVER: W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\03 Crop\IC_5070_A-Multi-NB-O3-02_graxpert_Prism-crop.fits : starting...<br />11:57:26 - FITS FRAME SAVER: W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\03 Crop\IC_5070_A-Multi-NB-O3-02_graxpert_Prism-crop.fits : constructing 32-bits FLOAT databuffer..<br />11:57:26 - FITS FRAME SAVER: W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\03 Crop\IC_5070_A-Multi-NB-O3-02_graxpert_Prism-crop.fits : creating FITS HEADER...<br />11:57:26 - FITS FRAME SAVER: W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\03 Crop\IC_5070_A-Multi-NB-O3-02_graxpert_Prism-crop.fits : writing to disc...<br />11:57:27 - Batch crop tool: processed frame 3 of 3 frames - W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\03 Crop\IC_5070_A-Multi-NB-O3-02_graxpert_Prism-crop.fits<br />11:57:27 - FITS FRAME SAVER: W:\AstroPhoto\IC5070 Pelican\Integrate\A+B\A\03 Crop\IC_5070_A-Multi-NB-O3-02_graxpert_Prism-crop.fits : finished successfully<br />11:57:27 - GENERAL FRAME SAVER: null : finished successfully<br />11:57:27 - FRAME DETAILS UPDATER: starting...<br />11:57:27 - FRAME DETAILS UPDATER: checking for duplicates in new frames...<br />11:57:27 - FRAME DETAILS UPDATER: adding 1 new frames...<br />11:57:27 - FRAME DETAILS UPDATER: encountered an execution exception &lt;==========<br />11:57:31 - SWITCH APPLICATION BUSY STATE : restoring imageviewer zoom factor to 1.00<br />11:57:31 - SWITCH APPLICATION BUSY STATE : restoring imageviewer splitpane position to 0.00<br />11:57:31 - SWITCH APPLICATION BUSY STATE : exiting busy state...<br />11:57:31 - SWITCH APPLICATION BUSY STATE : restarting image viewer mouse listener... <br />11:57:31 - SWITCH APPLICATION BUSY STATE : buttons are turned on.<br />11:57:31 - SWITCH APPLICATION BUSY STATE : enabling frame list table<br />11:57:31 - CONSTRUCT FRAME DETAILS LIST: starting...<br />11:57:31 - CONSTRUCT FRAME DETAILS LIST: finished<br />11:57:31 - FRAME DETAILS UPDATER: starting...<br />11:57:31 - FRAME DETAILS UPDATER: checking for duplicates in new frames...<br />11:57:31 - FRAME DETAILS UPDATER: adding 1 new frames...<br />11:57:31 - FRAME DETAILS UPDATER: encountered an execution exception &lt;==========<br />11:57:32 - SWITCH APPLICATION BUSY STATE : no change in busy state <br />11:57:33 - CONSTRUCT FRAME DETAILS LIST: starting...<br />11:57:33 - CONSTRUCT FRAME DETAILS LIST: finished<br />11:57:33 - FRAME DETAILS UPDATER: starting...<br />11:57:33 - FRAME DETAILS UPDATER: checking for duplicates in new frames...<br />11:57:33 - FRAME DETAILS UPDATER: adding 1 new frames...<br />11:57:33 - FRAME DETAILS UPDATER: encountered an execution exception &lt;==========<br />11:57:33 - SWITCH APPLICATION BUSY STATE : no change in busy state <br />11:57:33 - CONSTRUCT FRAME DETAILS LIST: starting...<br />11:57:33 - CONSTRUCT FRAME DETAILS LIST: finished<br />===</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Gilles Naud</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/nullpointerexception-in-batch-crop/</guid>
                    </item>
				                    <item>
                        <title>Problem setting save directory in APP 2.0.0 beta 45</title>
                        <link>https://www.astropixelprocessor.com/community/windows/problem-setting-save-directory-in-app-2-0-0-beta-45/</link>
                        <pubDate>Sun, 07 Jun 2026 01:33:15 +0000</pubDate>
                        <description><![CDATA[After having loaded files, any attempt to set a save directory sets that save directory to the last load directory used. For me, this behavior originated after an update from beta 41 to 45 i...]]></description>
                        <content:encoded><![CDATA[<p>After having loaded files, any attempt to set a save directory sets that save directory to the last load directory used. For me, this behavior originated after an update from beta 41 to 45 in windows11.<br /><br />The available workarounds are to set the save directories before loading any files or not attempt to set a save directory and allow files to be saved to the Work directory.</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Steve Teel</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/windows/problem-setting-save-directory-in-app-2-0-0-beta-45/</guid>
                    </item>
				                    <item>
                        <title>Normalization mode naming and default</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/normalization-mode-naming-and-default/</link>
                        <pubDate>Sat, 06 Jun 2026 06:58:01 +0000</pubDate>
                        <description><![CDATA[Hello,
IMHO, the new naming of Normalize modes is a bit confusing/counterintuitive...
&quot;overlap area&quot; - would be good for mosaics since the panels usually overlap 10-20%&quot;full image&quot; - would...]]></description>
                        <content:encoded><![CDATA[<p>Hello,</p>
<p>IMHO, the new naming of Normalize modes is a bit confusing/counterintuitive...</p>
<p>"overlap area" - would be good for mosaics since the panels usually overlap 10-20%<br />"full image" - would be good for regular integrations where panels fully overlap</p>
<p>But, regardless, currently the default mode is "full image" which is supposed to be for mosaics.<br />Please change the default to "overlap area".</p>
<p>Or I am wrong?</p>
<p>Thanks!</p>
<p>Max</p>
<p>&nbsp;</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>maxthebuilder</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/normalization-mode-naming-and-default/</guid>
                    </item>
				                    <item>
                        <title>my app wont work after update to latest version please help</title>
                        <link>https://www.astropixelprocessor.com/community/main-forum/my-app-wont-work-after-update-to-latest-version-please-help/</link>
                        <pubDate>Wed, 03 Jun 2026 22:29:08 +0000</pubDate>
                        <description><![CDATA[]]></description>
                        <content:encoded><![CDATA[10920]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Jeremychou</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/main-forum/my-app-wont-work-after-update-to-latest-version-please-help/</guid>
                    </item>
				                    <item>
                        <title>App 2.0.0 beta45 can&#039;t start</title>
                        <link>https://www.astropixelprocessor.com/community/windows/app-2-0-0-beta45-cant-start/</link>
                        <pubDate>Tue, 02 Jun 2026 18:30:01 +0000</pubDate>
                        <description><![CDATA[Hello, on Win10 I can&#039;t start the app.
Seem&#039;s running but nothing happens.
The JDK process is running.
Rolling back to beta44 works well.
Do you know the issue?
Best Regards]]></description>
                        <content:encoded><![CDATA[<p>Hello, on Win10 I can't start the app.</p>
<p>Seem's running but nothing happens.</p>
<p>The JDK process is running.</p>
<p>Rolling back to beta44 works well.</p>
<p>Do you know the issue?</p>
<p>Best Regards</p>]]></content:encoded>
						                            <category domain="https://www.astropixelprocessor.com/community/"></category>                        <dc:creator>Emmanuel Nunes</dc:creator>
                        <guid isPermaLink="true">https://www.astropixelprocessor.com/community/windows/app-2-0-0-beta45-cant-start/</guid>
                    </item>
							        </channel>
        </rss>
		