SharpCap Forums

I don't know if it's a SharpCap or Astap problem

I use a B/W ASI 294MM camera to photograph an asteroid and set a time of 15s that then in livestacking I will add up to total of 3 or 5 minutes
To be safe, before starting the capture, in LIVE mode, non-livestacking mode, I save an image with the SNAPSHOT button in FIT format that I then pass to Astap to check if I centered the asteroid.
So far so good
The strange thing is that only in this case, that is with the photo saved with the SNAPSHOT button, Astap recognizes the photo as if it were in color.

Even stranger, this only happens during the active session with the camera connected that continues to shoot every 15s.
The same FIT photo taken, checked again the next day, with only Astap open is recognized well in black and white.

Carlo

Hi,

that's weird, particularly that the behaviour was correct when tested later.

Astap should be using the FITS headers to determine whether colour or mono, and those will be written when the file is saved and not changed after that. In particular, the COLORTYP and BAYERPAT headers should be there for a RAW colour image and absent for mono.

There is a section in the Astap settings (in 'Stack Method') where you can specify an override of this and force mono images to be treated as raw colour. I could imagine this being the cause of your problem if it kept happening, but why would it be set one way initially and then another way the next day without you changing it?

So far, a mystery as far as I can tell!

cheers,

Robin

No mystery!
I had left the automatic RGB correction set on Astap
Everything works fine!
Thanks and sorry for the report

Carlo