Photo Supreme

I've purchased PS 7, too, but I won't deploy it until I buy a new Mac Studio. I expect that the base model with 32 GB of RAM should be fine to simultaneously run PS 7 and DXO Photolab 5. If anyone believes otherwise, then speak up. Future RAM upgrades are not an option.

It will be a month or two before I order a Mac Studio. But I am, of course, interested in testing and user experiences! I just purchased PS 7 - happy to help fund ongoing development and support.

My mid-2010 Mac Pro is long in the tooth. Apple no longer supports OS upgrades, so it's now a dedicated Win 10 machine. The new M1 Mac Studio looks interesting, but it may be too soon to cut over. I'm on Postgres 13, but I've seen reports of problems running Postgres on the ARM version of MacOS. Has ...

I use TrueNAS on a Xeon NAS that I built to store my photos. The pool consists of 4 drives, but PSU sees them as a single drive. I keep the PSU Postgres DB on a local SSD because the performance is much better than across the network, but I back it up to the NAS.

All seems to be back in order. Thank you, Hert!

Reinstall over what's on my machine? No need to uninstall my error?

I applied the latest Photo Supreme Server upgrade today, but I selected Postgres 12, which I had originally installed. But I'm now on Postgres 13. So what do I need to do?

I do have a time category that includes dates (actual or approximate), but mainly for objects photographed that have a particular date, rather for when images were taken.

Images are dated as part of my file name (see also folder and file names ). Those from digital cameras include the date within ...

I'm working to categorize old film scans - some as far back as the 1950's. So I've created a 'Time' category to label the year, when I know it, or the decade when that's the best that I can do. What I haven't figured out is how to integrate this with later images that are time stamped from digital ...

I have quite a few files to re-tag, but that's better than mis-tagged files. Progress.

This clean-up was going very slowly, so I updated the PostgreSQL config files based on Hert's recommendations (and to account for bumping up my RAM last week from 16 GB to 32 GB). What a difference! Cleaning up the tags is much faster now.

I did a quick category search and discover 4,206 mis-tagged files. They each have 109 tags. Could I not select all and remove one tag at a time for the group? And then write the metadata to the files?

I could restore a backup of my database and write out to the files. Or I may look at the tags of the over-tagged files and search the catalog to identify all of the errant tags. That may save some of the work that I've put in thus far. But I certainly will not write metadata back to files as a ...

I'm finding files far removed from where I was attempting to version that have over 100 incorrect tags on them. Is there a way to fix this? Do I need to go into the database tables and look for over-tagged records? I'd rather not throw out all of my work and restore all of my photos from backups ...

Then set the Offset Folder to "Parent folder". The parent includes the file's folder and all sibling folders.


That's what I tried, and I ended up with images in the versions that were children of the root. Not sure why that happened. I had moved a few folder in PSU, so maybe it hadn't caught up ...