Astroart Forum

See also the post “32 vs 64 bit” in this forum

LAA is the large memory access Version.
They all run very stable. What is the problem?

There are actually 3 versions of AstroArt, a 32-bit , a 64-bit and a "LAA" version.
Only the 32bit and the LAA version are showing the plugins (camera control etc).
The 64bit version is limited to image processing (see also in the help file).
I hope this helps
Clear skies
Bernd

Thanks Fabio for the quick and comprehensive reply. I will focus on the respective dark frames first and also double check where I have “real” flats.

Thanks Fabio,
Looking forward to the fix.

I am taking images with a C11 Schmidt-Cassegrain in Hyperstar configuration. So, i do have quite some vignetting plus a relatively large central obstruction. When i try to correct the images for vignetting, i am ending up most of the time with a donut shaped background in the middle of my images. He...

When using the "Profile Mode", i am sometimes seeing a strange behavior when updating the profile: In Profile Mode, after drawing a line with the cursor across the whole image from upper left to lower right (example attached), Profile error 1.png when clicking "Change Profile", the profile resets to...

Fabio, thanks for your quick reaction. I agree, the added latency added by the ASCOM driver doesn't sound like a lot and is not bad, BUT if the native driver downloads up to 6fps full frame in 1x1, it is still more than an order of magnitude slower. Yes, the QHY268C and the corresponding ASI ZWO 260...

This is about the different behaviors of the drivers supplied by camera manufacturers: First, i have taken Rudi's calculation (see below) for the QHY268C (APS-C, 16bit, 26.8MPixel) and get a max theoretical frame rate per sec(fps) on USB3 (max 5GBit/s) of: 6280 x 4210 pixels @16BPP = 423,020,800 (43...

I fully agree, Rudi, no big deal for deep sky images, but a lot of possible “unproductive “ time saving.