- Welcome to Code Obsession Forum.
Code Obsession Forum
https://codeobsession.com
Recent posts
#21
Bug Reports / Re: Obs v2.1 QuickLook Install
Last post by fsantore - November 06, 2024, 01:57:45 PMOK, I've now found the appropriate Discussions topic. I'll start by refreshing my knowledge there.
#22
Bug Reports / Obs v2.1 QuickLook Install
Last post by fsantore - November 06, 2024, 01:53:26 PMHi Sanders- could you please remind me. . . does installing v2.1 install the extension? It seems to have stopped working under MacOS 15.1. I'm also about to install the current 15.2 beta, but would like to retain the QuickLook functionality. Thank you. -Frank
#23
Announcements / Re: Ready for macOS Sequoia
Last post by fsantore - September 16, 2024, 10:05:30 AMHi Sander-
Thanks for keeping current with the MacOS's, and special thanks for the v2.1 release.
-Frank Santore
Thanks for keeping current with the MacOS's, and special thanks for the v2.1 release.
-Frank Santore
#24
Announcements / Ready for macOS Sequoia
Last post by Sander Berents - September 16, 2024, 12:19:14 AM #25
Announcements / Observatory 2.1
Last post by Sander Berents - September 05, 2024, 01:40:47 AM #26
Announcements / Farewell Observatory 1
Last post by Sander Berents - September 05, 2024, 01:38:26 AM #27
General Discussion / Re: QL FITS etc not working
Last post by Tailspin45 - July 25, 2024, 03:35:58 PMJust loaded 105.8Gb in two folder, 8315 images in 3233.8 seconds. So it definitely solved the problem (avoided the glitch).
Set CPU Core allocation midway and it seems to be loading a new batch of folders, this time over 300Gb. However, it popped up a window with a progress bar but it disappeared so fast I couldn't get a screen grab. Activity shows it is working, though.
No crash reports for any Import attempt. Apparently when it hangs and I cancel the process it just politely quits.
And yes, another "duh-o" event. Of course the Import is a background event. And of course you can't create a background process for a background process.
I have a vague recollection, though, that a UNIX daemon can fork a child and grandchild...but those neurons last fired maybe a half century ago so I'm not sure it's even relevant.
Set CPU Core allocation midway and it seems to be loading a new batch of folders, this time over 300Gb. However, it popped up a window with a progress bar but it disappeared so fast I couldn't get a screen grab. Activity shows it is working, though.
No crash reports for any Import attempt. Apparently when it hangs and I cancel the process it just politely quits.
And yes, another "duh-o" event. Of course the Import is a background event. And of course you can't create a background process for a background process.
I have a vague recollection, though, that a UNIX daemon can fork a child and grandchild...but those neurons last fired maybe a half century ago so I'm not sure it's even relevant.
#28
General Discussion / Re: QL FITS etc not working
Last post by Sander Berents - July 25, 2024, 01:43:46 PMGreat! Please email a crash report for that 65 GB folder when using the default core allocation setting.
Import is already a background task. Observatory needs this information, and a background task of a background task is a bit too much.
Import is already a background task. Observatory needs this information, and a background task of a background task is a bit too much.
#29
General Discussion / Re: QL FITS etc not working
Last post by Tailspin45 - July 25, 2024, 12:15:12 PMQuote from: Sander Berents on July 25, 2024, 11:31:24 AMWhat dimensions and size are your images usually, and what format
I have five cameras that capture only FITS files
ASI462MC 2.1Mb 1920x1080
ASI533MC 9.05Mb 3008x3008
ASI294MC 11.7Mb 4144x2822
ASI678MC 8.29Mb 3840x2160
ASI120MM 1.2Mb 1280x 960
QuoteWhen you import, Observatory doesn't just create a thumbnail and add it to the library. It also computes image statistics, the average HFD of stars, tags plate solved images, etc. For large images, that just takes time.
Do that in the background after import is complete?
QuotePlease try to import the 65 GB folder with the core allocation set to its minimum value. There used to be a bug that could result in a crash when importing, and I found its cause after introducing the core allocation setting. Maybe you are hitting another concurrency bug.
That appears to be the case. With core set to minimum value the 63.15Gb folder with 1015 files loaded in 989.9 seconds
#30
General Discussion / Re: QL FITS etc not working
Last post by Sander Berents - July 25, 2024, 11:31:24 AMGood to hear that the Quick Look extension works now. But it's weird because Observatory doesn't need full disk access, and the Quick Look extension runs in its own sandbox. I have that turned off and it works fine for me.
The selection beachball I have resolved already for the next update. It was caused by excessive UI updates for things that weren't even displayed.
I have tested Observatory with folders larger than 65 GB, so the size is not the cause of the crash. What dimensions and size are your images usually, and what format? When you import, Observatory doesn't just create a thumbnail and add it to the library. It also computes image statistics, the average HFD of stars, tags plate solved images, etc. For large images, that just takes time.
Please try to import the 65 GB folder with the core allocation set to its minimum value. There used to be a bug that could result in a crash when importing, and I found its cause after introducing the core allocation setting. Maybe you are hitting another concurrency bug.
The selection beachball I have resolved already for the next update. It was caused by excessive UI updates for things that weren't even displayed.
I have tested Observatory with folders larger than 65 GB, so the size is not the cause of the crash. What dimensions and size are your images usually, and what format? When you import, Observatory doesn't just create a thumbnail and add it to the library. It also computes image statistics, the average HFD of stars, tags plate solved images, etc. For large images, that just takes time.
Please try to import the 65 GB folder with the core allocation set to its minimum value. There used to be a bug that could result in a crash when importing, and I found its cause after introducing the core allocation setting. Maybe you are hitting another concurrency bug.