Astro Pixel Processor Forum - Recent Topics

Feature request, Ability to set the default file type in the open file dialogs.

cjdawson — Wed, 27 May 2026 10:23:01 +0000

As an avid APP user I would like to be able to set the default filetypes to filter on on the open dialog, so that I can simply open the folder, select all, and press enter making my life easier.

I keep every file that is produced by my astro gear, So this means that my AsiAir creates fits, and jpg's, as does my Seestar. When start to add lights, darks, etc. I have to manually change the filetype from all, to fits, to filter out the jpgs, and I have to do this every time I open the dialog.

I would love to be able to setup my own list of custom filters, as a default, so that I don't have to do this every single time. Personally, for my needs I would like to be able to select *.fits, *.cr2, *.dng and that would cover me completely, pretty sure that others would want to request something else which would create a whole debate and endless back and fourth. So, my thought is add a filter to the Licence & settings dialog, that if you fill it in, it becomes the default selection when importing files. When importing files, a "custom" option is added to the file type list, as defined by the setting, and selected by default. Users can then change this as desired.

Should be a fairly simple change that will allow people such as myself to be a little bit lazier, and happier at the same time.

Probleme bei der Verarbeitung von Flatframes mit den 2.xxx-Versionen

Dietmar Stache — Tue, 26 May 2026 14:05:42 +0000

Seit ich der Installation der APP-Versionen 2.x.x habe ich nach dem Stacken meiner Aufnahmen einen großen violetten Fleck in der Bildmitte, wenn ich Flats und Darkflats hinzugefügt habe, unabhängig von der Updateversion. Ohne die Kalibrierungsaufnahmen ist der Fleck nicht vorhanden.

Nachdem ich eine alte Installation der 1.x.x -Version von APP installiert hatte, ist diese Aufnahmeserie mit den zugehörigen Flats bzw. Darkflats einwandfrei verarbeitet worden, so dass die Updates der Serie 2.x.x einen Fehler bei der Verarbeitung von Kalibrierungsaufnahmen zu haben scheinen.

Die Flats bzw. Darkflats wurden ohne eine Änderung der Einstellungen (Fokussierung, Verdrehung, etc.) am nächsten Morgen aufgenommen.

Die Aufnahmen sind mit einem 10" Newton mit 0,75x-Nexus-Reducer, einer PlayerOne-Poseidon C OSC-Kamera und einem Optolong L-eNhance HaOIII-Filter gemacht worden. Der Fehler ist bei allen Color-Bearbeitungsroutinen aufgetreten.

10901

LRGB is not working in RGB Combine

Skye Goodrich — Mon, 25 May 2026 22:53:13 +0000

When I use the RGB Combine tool, for LRGB its treats L as a white layer of 4 layers, forcing the result to white. This is not correct. L is the intensity to which you take the RGB intensity, ... you compute the amount R contributes (say 23%) to a particular pixel, then multiply that times the L amount to get the new intensity for R, etc. Each color is painted onto L proportionately. The results should not be White but boosted colors, based on their proportion to each other multiplied by the Luminance level, give it an even strong intensity than it would have had without the L. Its completely not working as is, since its treating a 4 (LRGB) as equal layers. For example let's say your Luminance is 200 for a pixel, and you compute the RGB (based on RGB not LRGB) percentages for that pixel based on your data, let say that comes 37%/44%/19% (you throw away the old RGB intensity from the individual files and replace it with the intensity you compute here), so then you would end up with 200x.37 = 74 RED, 200x .44 = 88 GREEN, and 200 x .19 = 38 BLUE. Instead you're just giving us white. Its not about moving the slider down so white is not there revealing the color its about recomputing the intensity of each pixel based on L values as percentage of RGB, its a new intensity.

For example, here is APP on the LEFT; and ASIStudio on RIGHT (same FITS files as input). Yes I pushed recalc after selecting files on APP using LRGB formula.

10900

Extracting OIII on Dual Narrowband Filter

Leonard Libbey — Sat, 23 May 2026 21:52:33 +0000

I have several one shot color cameras and sometimes use my L-Extreme to capture faint OIII and HA signal. I am thinking about getting another dual narrowband filter for OIII and SII. My question is, will I be able to process both the OIII/HA group and the OIII/SII group at the same time in APP to create a single OIII channel/fits file, or will I have to process each separately and end up with two separate OIII fits files?

Beta 44 memory issues

John Connor — Sat, 23 May 2026 00:17:09 +0000

Mabula (@mabula-admin)

It looks like there are still issues with APP not releasing memory in beta 44 - at least on Linux. My computer has 96GB of ram, and APP is maxing it out.

I did a simple integration. 100 aps-c frames, colour camera. The OS ram just kept climbing until it was close to maximum (see below). After the process finished the OS ram slowly decreased over several minutes.

Also, the ram claimed by APP seemed unusually high. I'm used to an integration like this using less than 10GB, but it claimed about 31GB.

I am on Linux Mint 22.3, Cinnamon DE, X11.

(Edit - after rereading the release notes I see that the 'soft limit' of 32GB is intended to speed up processing and does not represent a problem)

10899

Flats don't work right all of a sudden

maxthebuilder — Fri, 22 May 2026 05:44:55 +0000

Hello,

This is not necessarily APP issue since I got the same result with Siril.
I decided to post here nonetheless since I didn't get anything helpful at Cludynights.

Got a new ASI2600MC camera to replace the one which just died (also ASI2600MC).

Collected Bias, Dark and Flat correction frames and composed Masters (in APP).

Used those correction Masters for 3 targets over four nights.

Worked OK.

With the 4th target I decided to collect new Flats.

To my surprise they didn't work right.

Old Flats still work OK.

New flats don't work with any of those 4 targets.

Same software (APP), same scope (RC6), same flat panel and brightness, same exposure time.
Same everything but the result is very different.

Tried different exposures, new Bias and even DarkFlats - same outcome.

The only peculiar thing about this: everything is 2x2 binned.
I don't normally do this but had to match binning with the Splinter galaxy I shot in 2023.

Integration with old flats:

10896

Integration with new flats:

10897

Stretched in APP (15% BG, 3 sigma, 2.5 base).

Any ideas?

Thanks!

Max

Behaviour of Back Point Slider

John Connor — Mon, 18 May 2026 01:07:50 +0000

Mabula (@mabula-admin)

I have recently switched from Windows to Linux and I can no longer change the black point by clicking left or right of the button on the slider. The image redraws but the BP value is unchanged. I can change the BP by grabbing the button, but this is very imprecise. I can no longer make small repeatable changes by clicking the slider. Other sliders are also affected.

I have tested this in beta40 and beta44. I am on Linux Mint 22.3, Cinnamon DE, X11.

It may be that this was a designed change that happened some time ago, as on Windows I was still using the last production version of APP (I know that's ancient history 🙄 ). Or alternatively this may be a minor, Linux only bug. Either way I would like to have the ability to make small repeatable adjustments restored.

thanks

Lost License Code

Jonathan Penny — Sun, 17 May 2026 16:05:10 +0000

Hello, sorry if this is the wrong area to post this .. I ordered the Owner's License back in 2022 and it shows on my account, but I must have deleted the email with the code sometimes between then and now as I can no longer find it. I did sent an email to the support email a few weeks ago and have not had a reply. Just hoping the owner / admin sees this and is able + willing to resend my activation email. Thank you :)

Issue in beta 44 with mosiac registration

Christian Gow — Sat, 16 May 2026 04:45:01 +0000

I am currently running the new Beta 44 and having issues with correct mosiac registration.

DDC is on. Even with quick projection preview it does not show up correctly. Registration mode is mosaic, registration model is projective.

I have tried default stars 500, 1000 and now 3000 (300 gives the closest result).

Any insight? I have not had this type of mosaic issues in the past few years so bit of a suprise.

10893