p.1 #1 · Mac + Windows photo organizer (FolioSort); just added people detection → XMP sidecars for Capture One — looking for fe
Upfront: I'm the developer, so read this as "here's what I built, tell me where it's wrong" rather than a recommendation
The new bit. Capture One has no people/face search, but it does read XMP sidecars and merge them into the catalogue. So I made the app do the auto face detection/grouping locally: point it at a folder, it groups the faces it finds, you name the groups, and it writes Photo.xmp next to each file with dc:subject + lr:HierarchicalSubject. The RAW is never touched. C1 or Lightroom picks it up on sync and you can then search the library by person.
What FolioSort actually does most days, and the reason I started it, is the unglamorous pile before the catalogue
- Reads the EXIF date, camera and GPS already in the files and builds the folder tree — 2024 › 06 › 14 › … — thousands at a time, with a live preview of the structure before anything moves. Copy mode by default, every copy checksum-verified, one-click undo.
- Batch rename from the same metadata, with templates.
- Finds exact duplicates, blurry frames and screenshots so you can clear them out.
- Un-breaks a Google Takeout export: dates buried in .json sidecars written back into the files, GPS restored, and it catches the Canon CR2/CR3 files Google silently renamed to .jpg.
- Mac (14+) and Windows, everything on-device, no account, nothing uploaded.
- other features available at www.foliosort.app
What I'd genuinely like to know from this board:
1. Flat keywords (Ana) or hierarchical (People|Ana)? I currently write both — does that make a mess in anyone's catalogue?
2. Does anyone here actually use MWG face regions (box + name), or are keywords enough in practice?
And if someone wants to throw a folder of NEFs or CR3s at it and tell me where it breaks, I'll fix it against real files
