2.0.0-beta6 hangs on launch on macOS Ventura

Thanks for noticing that! That's annoying as that's my code. 🙂 Unfortunately I don't have the latest MacOS so I will ask Wouter on our team to have a look as well, of course we will try to address that.

let me know if you need any more info: I'm a Java developer myself so have all the tools you might want to diagnose problems 🤣 

Thanks, that's cool. 🙂 We do have the tools, but I don't have a Mac so that makes things a bit tricky with new releases sometimes. Mabula has all the machines (I'm not jealous...) so we will find out. I was already reworking the console window, so it must be something simple I think, it's just a frame basically.

FWIW 2.0.0-beta6 opens fine for me on my Intel MacBook with Ventura and with the console as a separate window in APP.

@alfogator I have enabled Stage Manager and started APP 2.0.0-beta6. As you can see, APP starts normally. I brought the console window to the front so you can see that it runs in a separate window.

Hi @wvreeven thanks for checking it out on a saturday.

I took a screen capture to show you the problem:

 and of course now that I have enabled the console in cfg to show you the problem it won't launch anymore with or without stage manager, as you can see in the short video. Beta4 launches without problems. 

Right now I'm stuck to beta4, is there a way I can disable the console option by editing a config file somewhere?

PS: I'm using a Apple M1 Max Macbook Pro 16.

Update: I tried downloading the intel version of beta6 and it launched fine, after that the arm64 version starts just fine (for now).

Update 2: still weird, tried launching APP again after a while and it was stuck at launch as before. Launched the x86 version again and it launched fine, afterwards the arm64 version launched just fine as well.

Very strange. I was wondering if it is an issue between M-processors and Intel somehow. But does APP now start with the M1 compatible version all the time? Or just once after going back and forth?

Posted by: @vincent-mod

Very strange. I was wondering if it is an issue between M-processors and Intel somehow. But does APP now start with the M1 compatible version all the time? Or just once after going back and forth?

not sure, it has been pretty random so far.

Just in case it might be useful this is how it started malfunctioning yesterday:

- launched APP, renter license expired

- went to website, saw beta6 was out so downloaded it

- bought a perpetual license (apparently it takes me 2 years of engagement before getting married to a piece of software)

- launched beta6, activated

- settings were to default so I went to the cfg button and enabled separated preview window, as I did that APP froze with spinning beach ball, so eventually I killed it

- relaunched and it got stuck at the console, like in the video

- this morning I went back to see if I could fix it and after trying several things I noticed the stage manager thing I wrote about, you know the rest

Thanks for the detailed history. 🙂 So a very important part there is this: "and enabled separated preview window, as I did that APP froze with spinning beach ball,". That means it's not specific to the console, but to any separated window. That might narrow it down a bit (hopefully).

Hi all,

We think that we might have a fixed Astro Pixel Processor version for macOS Ventura. Can you all try the following 2.0.0-beta7test version and let us know if this solves it and works properly?

intel hardware:

https://astropixelprocessor.s3.eu-central-1.amazonaws.com/astropixelprocessor_2.0.0-beta7test-x86_64-macOS.zip

new M1/M2/arm hardware:

https://astropixelprocessor.s3.eu-central-1.amazonaws.com/astropixelprocessor_2.0.0-beta7test-aarch64-macOS.zip

Release notes for this version:

https://www.astropixelprocessor.com/community/release-information/astro-pixel-processor-2-0-0-beta7-release-notes-preparing-next-release/

Looking forward to your feedback!

Mabula

Hi @Mabula,

I just loaded the beta7 test version and it launched successfully on MACOS 12.6.1 So if it fixes Ventura issue, it seems to remain backwards compatible.  I did not yet try any processing yet, though

Clear skies,

Jochen

Hi @mabula-admin , I did some tests on the beta 7 version and so far I have not experienced the issue that was reported.

Thanks for the update!

Hi @jochen-scharmann & @alfogator,

Thank you very much for your feedback, that is highly appreciated 🙂 !

I am very glad to hear all seems to work well now on macOS Monterey and Ventura !

Mabula