Main Menu

Recent posts

#2
General Discussion / Re: Termination Reason: Nam...
Last post by Sander Berents - March 20, 2024, 10:11:50 PM
I cannot reproduce it. But Observatory 2.0.5 will contain two new settings that may solve the issue for you:

  • The ability to disable library versioning (the Time Machine integration);
  • Explicitly set the number of CPU cores to use for importing.

I am still working on a few other items before releasing it.
#3
General Discussion / Re: Termination Reason: Nam...
Last post by Tailspin45 - March 20, 2024, 12:00:14 PM
Are you actively working on the next update or should I look for another solution (Observatory is useless to me as things stand)?
#4
General Discussion / Re: Termination Reason: Nam...
Last post by Tailspin45 - March 13, 2024, 11:01:23 AM
Sounds like a plan. I look forward to the next update.
#5
General Discussion / Re: Termination Reason: Nam...
Last post by Sander Berents - March 10, 2024, 09:39:51 PM
All that seems to be Sonoma specific behavior, and document versioning related (Observatory's integrated Time machine support). I wonder if that is the underlying problem, that there is an obscure conflict going on with how Observatory handles versioning and some undocumented changes in Sonoma. I haven't touched that part of the code for years, so it is really a change in Sonoma that causes this.

The Observatory Demo has versioning disabled, but it doesn't allow saving libraries so we cannot test this theory with it.

I'll look into that and also add a few (hidden) settings to Observatory in the next update so that feature can be disabled and we can test if that "solves" it.

What's weird is that I have never seen this behavior myself on Sonoma. I have only been running Sonoma on an Apple silicon machine though, while you run it on an Intel machine. I have now upgraded one of my Intel machines to Sonoma as well, and maybe that allows me to reproduce it.
#6
General Discussion / Re: Termination Reason: Nam...
Last post by Tailspin45 - March 10, 2024, 09:27:20 AM
Successfully loaded several sessions, but when I tried to save, the error msg said the file couldn't be found, try saving a duplicate. When I tried that Observatory hung.

Tried renaming and saving the library, which seemed to work, but when I double-clicked on the file to launch Observatory, two windows appeared and the program crashed, no crash report.

Tried duplicating the file. When I double-click to launch nothing happens. When I tried Open With... two windows opened, then hang.

#7
General Discussion / Re: Termination Reason: Nam...
Last post by Tailspin45 - March 09, 2024, 03:46:33 PM
Quote from: Sander Berents on March 08, 2024, 07:48:51 PMThe current version of Sonoma is 14.4. Can you confirm you run the latest version?

As a matter of fact, it is not. It was 14.2.1 just as you said.

Auto update is on, and when I looked in the Settings, General, and Sysytem Update the OS told me it was up-to-date.

So I rummaged around, found Apple's swcdn, downloaded the 14.4 installer, and ran it.

Good news is, now I really am running the latest OS. Bad news is, Observatory still hangs or crashes.

And I still get a message that the library doesn't exist.
#8
General Discussion / Re: Termination Reason: Nam...
Last post by Sander Berents - March 08, 2024, 07:48:51 PM
I have not been able to reproduce any of these problems, and although the crash reports provide some hints, it is not clear to me yet what is the exact cause of the crash. The autosave issue may be permission or sandbox related, but that too I have not been able to reproduce. I'm trying to pinpoint the cause, but right now I do not seem to have enough information.

You are not doing anything "wrong". You are just running into an obscure Sonoma or Observatory bug. After all, it worked all this time, and now all of a sudden it doesn't. The bug reports I have received for this crash are all for macOS 14.2.1. The current version of Sonoma is 14.4. Can you confirm you run the latest version?
#9
General Discussion / Re: Termination Reason: Nam...
Last post by Tailspin45 - March 08, 2024, 11:09:14 AM
Quote from: Sander Berents on March 06, 2024, 08:44:47 PMDid you recently upgrade to macOS Sonoma?

No, I updated last September when it came out.

Having two windows open for the exact same library seems to be a macOS Sonoma-only regression. One that I have not been able to reproduce. It shouldn't be possible, but with Sonoma it apparently is. Observatory cannot work correctly in that state. Its library versioning (time machine) is supposed to help you restore an Observatory library to a previous state, but it sounds like it is in a state where that is not even possible.
[/quote]

That happened once and hasn't happened again. Timemachine did restore the 2023 library. But I still get the "can't autosave because library doesn't exist" message.

The larger problem is I can't import images without Observatory crashing.

I provided all the other details with the hope they, along with the crash reports, would help you figure out what's going on. As it stands, the program is useless.

To be clear, the problem may well be of my doing, and I love your program features and very much want it to do what it is supposed to do, but so far I don't feel any closer to a solution than I did when I started this thread over a week ago.
#10
General Discussion / Re: Termination Reason: Nam...
Last post by Sander Berents - March 06, 2024, 08:44:47 PM
Did you recently upgrade to macOS Sonoma? Having two windows open for the exact same library seems to be a macOS Sonoma-only regression. One that I have not been able to reproduce. It shouldn't be possible, but with Sonoma it apparently is. Observatory cannot work correctly in that state. Its library versioning (time machine) is supposed to help you restore an Observatory library to a previous state, but it sounds like it is in a state where that is not even possible.