Menu

Error with final stacked image / Access violation / 2nd+ run of stacking

16 hours ago
15 hours ago
  • Meister Eder

    Meister Eder - 16 hours ago

    Hi Han,

    im am using the latest Mac M1 version ASTAP version 2026.05.19, ARM 64 bit

    Actual i have the behavior, when stacking, the 1st run has no problems to create the final stacked image. But when i continue with stacking another images / session, the final stacked image gets an Access violation Error / Dialog.

    I could recreate the error, when just running the 1st stacking successful, and click just again on the Stack Button with no settings changed. In the 2nd round, the error dialog is coming in the end.
    The interim single R / G / B stacks are created as normal.

    The last logfile lines are

    18:36:16 Correcting the number of pixels added together.
    18:36:16 Applying black spot filter on the interim RRGGBB image.

    The images are on an external disk. The path length should not be an issue, right?

    The path to the interim stacks are
    '/Volumes/Extern 2TB - Astro/Astro/ASIAIR/Plan/Light/NGC7023_Iris-Nebula/WO81GT_ZWO1600MM/stacked01/NGC 7023, 2026-05-23, 54x180R 48x180G 51x180B, ZWO AM5, (R G B), ZWO ASI1600MM-Cool_stacked.fits'

    After clicking "OK" on the Dialog, further Stacking is not possible and i have to restart the program.

    Perhaps you have some ideas?

    Greetings
    Rolf

     
  • han.k

    han.k - 16 hours ago

    Hi Rolf,

    Yes, I like to investigate what is happening. A long path has never been a problem, but you path is long. External drives could be tricky.

    Can you share the images (Google drive?), So I can experiment here.

    I will first try a long path here.

     
  • han.k

    han.k - 15 hours ago

    Hi Rolf,

    I tried in Linux an even longer path at an external drive and it worked. I can access an Mac M4 remotely for testing. But can you first try to move some images to a shorter path at you external drive? If that still fails, try to copy some to your main drive and try again.

    cs, Han

     

Log in to post a comment.

MongoDB Logo MongoDB