Menu

Astap and macos M processor

Mariusz
2025-03-04
2025-03-11
1 2 > >> (Page 1 of 2)
  • Mariusz

    Mariusz - 2025-03-04

    I bought a new MacBook with an M4 Pro processor. When trying to install Astap, the system prompts me to install Rosetta. Isn’t this a native application for Apple Silicon? I tried the latest M1 version as well as an older M1 version. Both also asked for Rosetta. Why?

     

    Last edit: Mariusz 2025-03-04
  • Mariusz

    Mariusz - 2025-03-05

    Can someone help?

     
  • han.k

    han.k - 2025-03-05

    Hi Mariusz,

    Have you codesign the program? See below

    Han

    MacOS 64 bit version (Apple silicon processor, M-types cpu). Code signing of the executable is required. Instructions:

    1) Download
    https://sourceforge.net/projects/astap-program/files/macOS%20installer/astap_M1.pkg/download

    2) Make sure the ASTAP program is not running. Place the mouse cursor on the pkg file and install using the right mouse button popup menu.

    3) Open a terminal windows and copy paste and execute the following command:
    codesign --force -s - /Applications/ASTAP.app/Contents/MacOS/astap

    The code signing is required only once. An update doesn't require code signing.

     

    Last edit: han.k 2025-03-05
  • Mariusz

    Mariusz - 2025-03-05

    Yes I have done everything as above and still program ask to install Rosetta first. I installed it on another MacBook with an old M1 processor with allready Rosetta installed, and here’s the situation:
    The program installed successfully, and I checked in the Activity Monitor—it’s indeed running natively in Apple mode. Maybe it’s just the installer that requires Rosetta?

     

    Last edit: Mariusz 2025-03-05
  • han.k

    han.k - 2025-03-05

    This is new for me. I have only an old Mac with an Intel processor, so I can not test it. The installer PKG file is only a compressed package but yes maybe there is somewhere a flag indicating Intel.

    I will investigate further but not have a solution yet. Is installing Rosetta 2 a major step you want to avoid?

    Cheers, Han

     
  • han.k

    han.k - 2025-03-05

    I assume I know the cause. There are two other command-line programs included in the package which do not run natively using an M processor.

    unprocessed_raw : this one is used to convert dslr raw to fits.
    fpack & funpack: there are used for un/compression of fits files.

    I assume if I upgrade these command-line programs the pkg installer will work. Compiling unprocessed_raw for the M processor should be doable. The ohers fpack/unpack I could leave out of the package..

    Han

    Some info:
    https://www.codejam.info/2022/04/repackage-macos-app-m1-support-without-rosetta.html

     
  • Mariusz

    Mariusz - 2025-03-05

    This link is quite complicated for me. Is there a chance for an installation package without Rosetta?

     
  • han.k

    han.k - 2025-03-05

    If you do not have DSLR images, I could just remove the intel programs and it will work for you. I will make such a package.....

     
  • Mariusz

    Mariusz - 2025-03-05

    I own seestar s50 now. Thank you very much.

     

    Last edit: Mariusz 2025-03-05
  • han.k

    han.k - 2025-03-05

    Tell me if this works for you.

    Han

     
  • han.k

    han.k - 2025-03-05

    After installing you also have to codesign it

     
  • Mariusz

    Mariusz - 2025-03-05

    YES!!!! Now its working perfectly! Thank you very very much! Nice job!
    After coding, I received the following feedback:
    /Applications/ASTAP.app/Contents/MacOS/astap: replacing existing signature
    /Applications/ASTAP.app/Contents/MacOS/astap: resource fork, Finder information, or similar detritus not allowed

    Is this ok?

    Program is working ok but I get an error every time I close the application:
    The ASTAP application unexpectedly crashed.

     

    Last edit: Mariusz 2025-03-05
  • han.k

    han.k - 2025-03-05

    The cause of the crash is unclear to me. I need an Mac with an M processor to test the program in the compiler& debugger to find the cause. I need a volunteer to allow me to remote login in his Mac and install the compiler & debugger and run the program to trace the cause of the error. Taking maybe 2 hours

    Does the crash also happen in the older M1 Mac?

    I put a link on my webpage page to this ASTAP stripped version. More users will have the same problem.

    Han

     
  • Mariusz

    Mariusz - 2025-03-05

    Yes, this error also occurs on M1 when close app.

     
  • han.k

    han.k - 2025-03-05

    I see the same error on my Mac with an intel processor. Okay I will fix it....

     
  • Mariusz

    Mariusz - 2025-03-05

    Great support. Thank you very much!

     
  • Mariusz

    Mariusz - 2025-03-06

    OK, I have tested:
    1. The program installs correctly without Rosetta - OK
    2. The program closes properly without crash - OK
    3. The program loads an image from a link - OK

    Is there anything else I can do for you?

    I have only one sugestion. In stack menu then I click brows to add fits files keyboard shortcut "cmnd A" to select all is not working. Also then I view list of files shortcut to rename "cmnd backspace" also not working. Is this normal?

     
  • han.k

    han.k - 2025-03-06

    Good news. Thanks for the feedback.

    About the keyboard commands. I do not know at this moment. Often these commands are programmed with CTRL instead CMND. My source can be compiled to Windows, Linux and Mac. I will check the new weeks. First some other things to do here.

    Cheers, Han

     
    ❤️
    1
  • han.k

    han.k - 2025-03-07

    Please upgrade to ASTAP version 2025.03.07. The previous version has a bug in sigma clip stacking of OSC images.

    Cheers, Han

     
    👍
    1
  • han.k

    han.k - 2025-03-07

    No should be fully M processor unless i made a mistake. So no Rosetta required.

     
  • Mariusz

    Mariusz - 2025-03-08

    Something must have gone wrong. Unfortunately, it’s calling for Rosette now when I wanna start instalation.

     

    Last edit: Mariusz 2025-03-08
  • han.k

    han.k - 2025-03-11

    I think it is all fixed now in version 2025.03.11. Can you check?

    1) The threads where running on a single processor because the number of available CPU detection's did not work for MacOS.
    2) I did by mistake put the X86_64 version in the M package.

    Cheers, Han

     
1 2 > >> (Page 1 of 2)

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.