Performance, storage space, bugs

[msw.photo]

Hi all,

I don't know why my former post has been deleted (reason The message contains links to illegal or pirated software..). I have a real problem with Photo Supreme and I expect appropriate support here.

I started with Photo Supreme 2024 (always latest updates, but none of the following problems changed) some weeks ago and so far it has been very sobering.

I have 295k photos imported. Meanwhile, the import was interrupted countless times. Sometimes the app did not respond because it was using over 82GB - yes, gigabytes - of memory and had to be closed and restarted immediately. Sometimes the status display did not continue. How can I be sure that all images have been imported? And why does the app have such lousy memory management?

And while we're on the subject of storage: 29.3 GB database file, thumbnails excluded? That's an average of just under 100 kB per image. A well-filled XMP file has approx. 10-16 kB. That can't be right, can it?

Now, after dozens of catalogue compressions (I think I've compressed more than I've imported), I still see the Mac beachball for about 40 seconds after launching Photo Supreme. Is a Mac Studio M2 Max with 32 GB RAM and 12-core CPU, 30-core GPU, 16-core Neural Engine too weak?
The next message after starting Photo Supreme is always that the creation of 84 thumbnails is still in progress.
In the meantime, I have had the thumbnail database completely recreated (which was only possible with dozens of interruptions, as was already the case with the import). Nothing has changed.

And there are thousands of little things that are simply wrong or don't work. One example: if I rotate an image in Photo Supreme and use the small symbols at the bottom of a thumbnail (not working shortcut [ and ] ), then this information about the rotation is not saved in the XMP file? I then found the drop-down menu for the orientation in the shooting data. But the description is the other way round: clockwise it rotates counterclockwise and vice versa. How can that be?
Also, you really have to manually trigger the thumbnail creation again after setting the alignment via the dropdown menu, it really doesn't even update the thumbnail after you have applied the alignment setting.

I'm really lost for words right now. I mean, this software is being sold for money and it's already failing in its basic purpose? Surely this is an impossible scenario and there is a solution that I just can't find, right? I hope you will be kind enough to put me on the right track.

[Hert]

First of all a warm welcome to the forum.

I don't know why my former post has been deleted (reason The message contains links to illegal or pirated software..).

Running a forum anno 2024 is outdated. Forums are spammed massively, hence why the first post on this board is moderated. This way many spam posts are being deleted every day. On top of that the Spammers gets smarter every day and nowadays they use AI techniques to generate topics and posts that are very hard to determine if they are from real people or not...they generate real questions that often make sense. That increases the chance of a valid post to get deleted in the process.
Luckily the spammers still make small mistakes that give away their intensions but as they get better in the future it will likely become impossible to identify real posts from fakes.

I have a real problem with Photo Supreme and I expect appropriate support here.

As explained in the forum rules, this is a user-to-user forum. Expect help from other users here.

I have 295k photos imported. Meanwhile, the import was interrupted countless times. Sometimes the app did not respond because it was using over 82GB - yes, gigabytes - of memory and had to be closed and restarted immediately. Sometimes the status display did not continue. How can I be sure that all images have been imported? And why does the app have such lousy memory management?

Please report this as a support question if this continues.

And while we're on the subject of storage: 29.3 GB database file, thumbnails excluded? That's an average of just under 100 kB per image. A well-filled XMP file has approx. 10-16 kB. That can't be right, can it?

A DAM (regardless which one) stores more than just a simple XMP block.

Now, after dozens of catalogue compressions (I think I've compressed more than I've imported)

I assume you mean compacting instead of compressing. When a compact of the catalog is needed then you'll be notified on startup. No need to manually compact unless you see reason to do so, which would be incidently.

I still see the Mac beachball for about 40 seconds after launching Photo Supreme. Is a Mac Studio M2 Max with 32 GB RAM and 12-core CPU, 30-core GPU, 16-core Neural Engine too weak?

On startup, PSU checks for missing thumbs and files that are not fully imported. In a "complete" catalog that should never take more than a blink of the eye.

The next message after starting Photo Supreme is always that the creation of 84 thumbnails is still in progress.

You probably have some files that cannot have their thumbs created. There are several topics about that. Here's a very recent one.
viewtopic.php?t=35290

One example: if I rotate an image in Photo Supreme and use the small symbols at the bottom of a thumbnail (not working shortcut [ and ] ), then this information about the rotation is not saved in the XMP file? I then found the drop-down menu for the orientation in the shooting data. But the description is the other way round: clockwise it rotates counterclockwise and vice versa. How can that be?
Also, you really have to manually trigger the thumbnail creation again after setting the alignment via the dropdown menu, it really doesn't even update the thumbnail after you have applied the alignment setting.

PSU is completely metadata driven and whenever there is something wrong in the metadata then you will be confronted with this in PSU. The positive thing is that PSU typically allows you to fix such omissions.
How you describe the rotation behavior typically indicates that the orientation tag of the metadata doesn't correctly reflect the orientation of the image pixels. In the Details panel you can check or change the orientation setting.

It could also be that you have discrepancies between Exif and XMP where the Exif orientation and the XMP orientation arte not in-sync. This happens a lot when using tools that don't update all levels of metadata (eg they update Exif but don't update XMP when there). First thing I would do is to make sure that Exif and XMP are in sync. Do that with right click on the thumb -> Metadata -> Convert metadata to XMP.
Then use the Details tab to correct the orientation tag to reflect the original image pixel data.

Hope that helps.

[msw.photo]

Thanks a lot for your really long answer, Hert!

I will work on it step by step. If there are any further questions, I allow myself to write them here.