Microsoft Windows - Astro Pixel Processor Forum https://www.astropixelprocessor.com/community/windows/ Astro Pixel Processor Discussion Board en-US Sat, 13 Jun 2026 02:10:44 +0000 wpForo 60 Problem setting save directory in APP 2.0.0 beta 45 https://www.astropixelprocessor.com/community/windows/problem-setting-save-directory-in-app-2-0-0-beta-45/ Sun, 07 Jun 2026 01:33:15 +0000 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.

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.

]]> Microsoft Windows Steve Teel https://www.astropixelprocessor.com/community/windows/problem-setting-save-directory-in-app-2-0-0-beta-45/ App 2.0.0 beta45 can't start https://www.astropixelprocessor.com/community/windows/app-2-0-0-beta45-cant-start/ Tue, 02 Jun 2026 18:30:01 +0000 Hello, on Win10 I can't start the app.

Seem's running but nothing happens.

The JDK process is running.

Rolling back to beta44 works well.

Do you know the issue?

Best Regards

]]> Microsoft Windows Emmanuel Nunes https://www.astropixelprocessor.com/community/windows/app-2-0-0-beta45-cant-start/ APP 2, Beta 43 -- works great https://www.astropixelprocessor.com/community/windows/app-2-beta-43-works-great/ Sun, 03 May 2026 06:27:09 +0000 Just tried Beta 43 on Windows, works flawlessly.  Stacked 120 RGB lights of Leo Triplet on ASI533MC Pro (98% moon), and the result is beautiful.  

]]> Microsoft Windows Skye Goodrich https://www.astropixelprocessor.com/community/windows/app-2-beta-43-works-great/ Windows crash during integration on latest version https://www.astropixelprocessor.com/community/windows/windows-crash-during-integration-on-latest-version/ Sun, 26 Apr 2026 17:11:21 +0000 Hi Mabula,

I’ve been testing APP 2.0 latest release on a new system and wanted to report a consistent issue.

System:

  • Windows 11
  • i7-11850H (16 threads)
  • 64GB RAM
  • RTX A4000 laptop GPU

Dataset:

  • ~400 light frames
  • 16-bit, ~49MB each

Behaviour:

  • 2.0.0-beta41 (Oracle JDK 25.0.2)
    → crashes during integration and drizzle (javaw.exe faults)
  • 2.0.0-beta38 (GraalVM 24)
    → same dataset completes integration and drizzle successfully

Notes:

  • No issues on older laptop (32GB RAM) with earlier 2.0 builds
  • Reducing threads did not prevent crashes in beta41
  • Beta38 runs stable even with 10 threads

It seems related to the newer Java runtime / memory handling in beta41.

Happy to provide logs if useful.

Thanks for all your work on APP.

kind regards 

Bryan 

P.s. had some help from AI solving this problem and when I asked if I should report my findings back to you it strongly recommended this and composed the above message 😊

]]> Microsoft Windows Astr0dude https://www.astropixelprocessor.com/community/windows/windows-crash-during-integration-on-latest-version/ APP won't remember the Integrate Percentage Slider https://www.astropixelprocessor.com/community/windows/app-wont-remember-the-integrate-percentage-slider/ Sat, 21 Mar 2026 13:46:04 +0000 Although most settings are stored between sessions, APP won't remember the integration percentage "lights to stack" such as if I set it on 90% one session, it forgets and goes back 100%.   Suggest have it remember what I set last time.  

]]> Microsoft Windows Skye Goodrich https://www.astropixelprocessor.com/community/windows/app-wont-remember-the-integrate-percentage-slider/ APP 2.0.0 Beta 39 Cannot Save Calibrated Light Frames With Align Channels Selected https://www.astropixelprocessor.com/community/windows/app-2-0-0-beta-39-cannot-save-calibrated-light-frames-with-align-channels-selected/ Sat, 14 Mar 2026 14:16:05 +0000 APP 2.0.0 Beta 39 Cannot Save Calibrated Light Frames With Align Channels Selected

APP stops processing after 3 files processed. If I deselect Align Channels files will process.

10:13:16 - GENERAL IMAGE LOADER: loading frame D:\HAL2024 Astro\Work\lights\2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits
10:13:16 - 2) CALIBRATE: Adaptive Data Pedestal: disabled
10:13:16 - 2) CALIBRATE: performing calibration in 32bits normalized floats...
10:13:16 - 2) CALIBRATE: converting data to 32bits normalized floats...
10:13:16 - FITS FRAME SAVER: D:\HAL2024 Astro\Work\APP\2026-03-10-0157_6-M82_533_60s_101g_-10d_d_00003-cal.fits : finished successfully
10:13:16 - GENERAL FRAME SAVER: null : finished successfully
10:13:16 - 2) CALIBRATE: starting Cosmetic Correction...
10:13:16 - 2) CALIBRATE: Cosmetic Correction: hot pixel correction enabled with kappa 3.0
10:13:16 - 2) CALIBRATE: Cosmetic Correction: cold column correction enabled with kappa 8.0
10:13:16 - 2) CALIBRATE: Cosmetic Correction: hot column correction enabled with kappa 8.0
10:13:16 - 2) CALIBRATE: Cosmetic Bad Column Correction: CFA data
10:13:16 - 2) CALIBRATE: Cosmetic Correction: number of cosmetically corrected hot columns: 0
10:13:16 - 2) CALIBRATE: Cosmetic Correction: number of cosmetically corrected cold columns: 0
10:13:16 - 2) CALIBRATE: Cosmetic Correction: number of cosmetically corrected bad columns: 0
10:13:16 - 2) CALIBRATE: Cosmetic Hot Pixel Correction:: Bayer CFA data
10:13:17 - 2) CALIBRATE: Cosmetic Hot Pixel Correction: creating cosmetic Hot Pixel Map...
10:13:17 - 2) CALIBRATE: Cosmetic Hot Pixel Correction: number of cosmetically corrected hot pixels: 13958
10:13:17 - 2) CALIBRATE: Cosmetic Correction: finished...
10:13:17 - Channel Aligner: starting for frame 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits
10:13:17 - Channel Aligner: performing star analysis on frame 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: starting...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: color data
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: getting channel 1
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: creating star map...
10:13:17 - GENERAL IMAGE LOADER: frame D:\HAL2024 Astro\Work\lights\2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits was loaded successfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates: initial FWHM estimate: 7.20 +- 1.80 pixels
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates: target noise level is at kappa 1.0
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates: target luminosity of stars is 1.622E-03
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates: initially identified 27 of possible star candidates
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: star map created successfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identified star candidates successfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probing star positions and luminosities...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probing local background, noise and FWHM for all stars...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: estimated Full Width at Half Maximum (FWHM) of star profiles : 7.20 +- 1.80 pixels...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: analysing all stars candidates with star size areas equal to or larger than 20 pixels...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: performed & collecting 2D general gaussian star profile regression and IW centroiding on all stars successfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: removed 5 star candidates stars from the initial star candidates
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: 22 star candidates left
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: removed stars that are too close to each other successffully: 0 stars removed
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: correcting star map and star list for possible bad star detections...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: number of removed duplicate stars 1
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: final number of identified and fully analysed stars 21
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: receiving final details...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: closed
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: starting...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: color data
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: getting channel 2
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: creating star map...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probed star positions and luminosities successfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probed local background, noise and FWHM for all stars successfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: got all star details succesfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probed local background, noise and FWHM for all stars successfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: star map created successfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates: initial FWHM estimate: 10.44 +- 2.61 pixels
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates: target noise level is at kappa 1.0
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates: target luminosity of stars is 3.185E-04
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates: initially identified 96 of possible star candidates
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probing star positions and luminosities...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probing local background, noise and FWHM for all stars...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identified star candidates successfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: estimated Full Width at Half Maximum (FWHM) of star profiles : 10.44 +- 2.61 pixels...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: analysing all stars candidates with star size areas equal to or larger than 20 pixels...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probed star positions and luminosities successfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: performed & collecting 2D general gaussian star profile regression and IW centroiding on all stars successfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: removed 11 star candidates stars from the initial star candidates
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: 76 star candidates left
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: removed stars that are too close to each other successffully: 0 stars removed
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: correcting star map and star list for possible bad star detections...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: number of removed duplicate stars 2
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: final number of identified and fully analysed stars 74
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: receiving final details...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: closed
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: starting...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: color data
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: getting channel 3
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: creating star map...
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probed local background, noise and FWHM for all stars successfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: got all star details succesfully
10:13:17 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probed local background, noise and FWHM for all stars successfully
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates...
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: star map created successfully
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates: initial FWHM estimate: 10.51 +- 2.63 pixels
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates: target noise level is at kappa 1.0
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates: target luminosity of stars is 3.473E-04
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identifying star candidates: initially identified 83 of possible star candidates
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probing star positions and luminosities...
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probing local background, noise and FWHM for all stars...
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: estimated Full Width at Half Maximum (FWHM) of star profiles : 10.51 +- 2.63 pixels...
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: analysing all stars candidates with star size areas equal to or larger than 20 pixels...
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: identified star candidates successfully
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probed star positions and luminosities successfully
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probed local background, noise and FWHM for all stars successfully
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: performed & collecting 2D general gaussian star profile regression and IW centroiding on all stars successfully
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: removed 5 star candidates stars from the initial star candidates
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: 67 star candidates left
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: removed stars that are too close to each other successffully: 0 stars removed
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: correcting star map and star list for possible bad star detections...
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: number of removed duplicate stars 1
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: final number of identified and fully analysed stars 66
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: receiving final details...
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: closed
10:13:18 - Channel Aligner: received star analysis results for frame 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits
10:13:18 - Channel Aligner: starting registration for Red and Blue channels with Green Channel for frame 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits
10:13:18 - Channel Aligner: received pattern recognition descriptors for Green Channel for frame 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits
10:13:18 -
10:13:18 - 4) REGISTER: triangles descriptors: start expansion of registration hypothesis for frames 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits-Red-channel with reference -Green-channel with 18 star pairs
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: got all star details succesfully
10:13:18 - 3) ANALYSE STARS: 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits: probed local background, noise and FWHM for all stars successfully
10:13:18 - 4) REGISTER: RANSAC: testing registration hypothesis for frames 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits-Red-channel and reference -Green-channel
10:13:18 - 4) REGISTER: RANSAC: no DDC performing RANSAC # 18 pairs
10:13:18 - 4) REGISTER: RANSAC: no DDC after RANSAC # 18 pairs with RMS 1.09
10:13:18 - 4) REGISTER: RANSAC: Is homography nearly identity matrix: true
10:13:18 - 4) REGISTER: RANSAC: DCC disabled at startup: true
10:13:18 - 4) REGISTER: RANSAC: choosing noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: initial RMS 1.094 on 18 star pairs
10:13:18 - 4) REGISTER: RANSAC: number of pairs after RANSAC: 00019 - RMS 1.07 - noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: number of pairs after RANSAC: 00019 - RMS 1.07 - noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: limiting hypothesis using no DDC
10:13:18 - 4) REGISTER: RANSAC: number of pairs after RANSAC: 00005 - RMS 0.18 - noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: number of pairs after RANSAC: 00006 - RMS 0.28 - noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: number of pairs after RANSAC: 00007 - RMS 0.40 - noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: number of pairs after RANSAC: 00008 - RMS 0.42 - noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: number of pairs after RANSAC: 00009 - RMS 0.44 - noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: number of pairs after RANSAC: 00010 - RMS 0.64 - noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: number of pairs after RANSAC: 00011 - RMS 0.88 - noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: number of pairs after RANSAC: 00012 - RMS 0.99 - noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: number of pairs after RANSAC: 00013 - RMS 1.11 - noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: number of pairs after RANSAC: 00013 - RMS 1.11 - noUndistortionModel
10:13:18 - 4) REGISTER: RANSAC: frames 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits-Red-channel and reference -Green-channel finished - number of pairs 13 RMS 1.11
10:13:18 - 4) REGISTER: triangles descriptors: finished expansion of registration hypothesis for frames 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits-Red-channel with reference -Green-channel
10:13:18 - 4) REGISTER: triangles descriptors: number of accepted star pairs for frames 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits-Red-channel with reference -Green-channel = 18
10:13:18 - 4) REGISTER: triangles descriptors: found at descriptor scale 1
10:13:18 - 4) REGISTER: triangles descriptors: hypothesis gives number of starPairs: 13
10:13:18 - 4) REGISTER: triangles descriptors: stopping at scale 1
10:13:18 - 4) REGISTER: triangles descriptors: number of final star pairs for frames 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits-Red-channel with reference -Green-channel = 13
10:13:18 -
10:13:18 - Channel Aligner: received registration results for Red Channel for frame 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits
10:13:18 -
10:13:18 - 4) REGISTER: triangles descriptors: start expansion of registration hypothesis for frames 2026-03-10-0158_6-M82 533 60s 101g -10d d_00004.fits-Blue-channel with reference -Green-channel with 30 star pairs

]]> Microsoft Windows Vincent Laine https://www.astropixelprocessor.com/community/windows/app-2-0-0-beta-39-cannot-save-calibrated-light-frames-with-align-channels-selected/ 2.0.0.39 will not start - .38 is fine. https://www.astropixelprocessor.com/community/windows/2-0-0-0-39-will-not-start-38-is-fine/ Sat, 06 Dec 2025 16:27:27 +0000 Hi, I've recently installed the latest windows version 2.0.0.39. It will not start. Even if I go to the installation folder and double click the .exe it does not run. After trying to start it Task Manager does not show it as a process or an APP. (I've also tried running it as administrator)
2.0.0.38 ran/runs with no issues. I have tried .39 as an install over .38 and also as a fresh install (I used windows uninstall to remove .38) but it simply does not start. I'll just carry on using .38 for the time being but as I have a fairly mainstream system and OS I thought I'd flag it as a possible problem.

Edition Windows 10 Pro
Version 22H2
Installed on ‎23/‎04/‎2023
OS Build 19045.6466

Processor Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz 4.00 GHz
Installed RAM 32.0 GB (31.9 GB usable)
Storage 932 GB SSD CT1000MX500SSD1, 932 GB HDD ST1000DM010-2EP102, 1.82 TB HDD TOSHIBA HDWD120
Graphics Card NVIDIA GeForce GTX 1060 3GB (3 GB), Intel(R) HD Graphics 4600 (113 MB)
Device ID 7F44AC26-B736-4623-82E1-2761FB32C0DC
Product ID 00330-50000-00000-AAOEM
System Type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

 

]]> Microsoft Windows tonygibbons55 https://www.astropixelprocessor.com/community/windows/2-0-0-0-39-will-not-start-38-is-fine/ Windows 11 crash at final integration step APP 2.0.0 beta 38 https://www.astropixelprocessor.com/community/windows/windows-11-crash-at-final-integration-step-app-2-0-0-beta-38/ Tue, 10 Jun 2025 20:17:50 +0000 APP 2.0.0 beta 38 crashes midway the final integration step after LNC Integration on my Windows 11 PC

]]> Microsoft Windows Andreas Riegler https://www.astropixelprocessor.com/community/windows/windows-11-crash-at-final-integration-step-app-2-0-0-beta-38/ Remote Desktop Connection (RDP) causes APP to silently fail/close https://www.astropixelprocessor.com/community/windows/remote-desktop-connection-rdp-causes-app-to-silently-fail-close/ Thu, 22 May 2025 04:58:35 +0000 I run APP (2.0.0-Beta36) on a Windows 11 PC. Historically I Remote Desktop (RDP) into this machine to use APP and check on progress bars.  Starting at or around Beta35, when I RDP into the machine the running instance of APP seems to have crashed.  I'm having trouble consistently reproducing the issue, but it has happened during various stages of processing, and more frequently in the last month or so.  Other open programs are still running, only APP seems to have failed.  Has anyone seen this issue?

I rarely seem to get a log file when this happens, the few I see point to a JRE crash.

#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fffa761bdf1, pid=27520, tid=11780
#
# JRE version: Java(TM) SE Runtime Environment Oracle GraalVM 23.0.2+7.1 (23.0.2+7) (build 23.0.2+7-jvmci-b01)
# Java VM: Java HotSpot(TM) 64-Bit Server VM Oracle GraalVM 23.0.2+7.1 (23.0.2+7-jvmci-b01, mixed mode, tiered, jvmci, jvmci compiler, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

]]> Microsoft Windows Jonathan Schwab https://www.astropixelprocessor.com/community/windows/remote-desktop-connection-rdp-causes-app-to-silently-fail-close/ Automating APP workflow with n8n/scripts: seeking solutions https://www.astropixelprocessor.com/community/windows/automating-app-workflow-with-n8n-scripts-seeking-solutions/ Thu, 08 May 2025 13:20:16 +0000 Automating APP workflow with n8n/scripts: seeking solutions

Hello APP community,

I'm looking to automate my astrophotography processing workflow with Astro Pixel Processor and would like to share my thoughts and get your suggestions.

Context

I have a folder structure organized as follows:

  • Main folder: Astro
  • Image type subfolders: Lights, Flats, Darks, Bias
  • Organized by session date: ///

I want to automate the entire processing workflow, from initial stacking to final integration.

What I've explored so far

I've started working with n8n (a node.js-based automation tool) to create a workflow that:

  1. Detects new acquisition sessions
  2. Prepares destination folders for results
  3. Launches APP with appropriate configurations
  4. Processes different types of images (calibration, stacking, etc.)

Questions and challenges

  1. Command line options: Does APP support any command line options to directly load .apdx profiles or execute specific operations?
  2. API automation: Is there an accessible or planned API that would allow direct interaction with APP from a script or tool like n8n?
  3. Profile loading: How can I automatically load .apdx profiles for different image types (lights, flats, etc.)?
  4. Folder monitoring: Is the folder monitoring feature mentioned in other discussions available? How can it be configured?
  5. Alternative solutions: Have you implemented other automation solutions with APP (AutoIt, PowerShell, shell scripts, etc.)?

My current approach

At the moment, I need to manually launch APP and load profiles manually, but I'd like to automate further. I've created an n8n workflow that:

  • Prepares source/destination folders
  • Launches APP
  • Guides me through the necessary manual steps

If any of you have developed effective automation solutions with APP, I would be very interested to learn about your approach!

Thanks in advance for your advice and suggestions.

Kind regards, Thibaud

]]> Microsoft Windows thibaud lefort https://www.astropixelprocessor.com/community/windows/automating-app-workflow-with-n8n-scripts-seeking-solutions/