Post

capture one file management is an absolute mess

or rather: my use case is poorly covered by it

i want to: 1. copy on import into an capture-time ISO8601 dir structure of my choosing, so all my masters go into iCloud 2. cull into long-running sessions that reference the masters, but keep outputs local iCloud/Photography/ ./RAWS/YYYY/MM/DD/raw+xmp ./Sessions/<name>/{selected,outputs}

#1 right now catalogs would either reference files (so i have to manually copy them from the SD cards) or manage them inside the .cocatalog file (which is massive and supposed to be opaque) a session always copies and you can do is8601 BUT it won't *see* the files below the first folder

this means i can import into asession from my sd card, and on disk it'll look like ./Sessions/{name}/Captured/YYYY/MM/DD/raw which is very close to what i want but the session browser doesn't see pictures in child dirs of Captured! so i gotta manually create favorites or tag 'em which is ugh

what sessions do *great* is being self contained: captured, selected, and outputs are all within the same folder (so yay i won't lose those exported JPEGs anymore!)

the recommended flow is to create sessions for every day/shoot/whatever you do, and then once you're done editing and outputting things for it, import a session into your catalog and then use the catalog as an archive. BUT then you can't re-edit the session and have it sync

lightroom would handle this for you, so i never saw my raws on disk they were cloud sync'd by adobe. that was great! in fact, these past few days trying to find a reasonable way to impoirt and cull a 30,000 picture catalog have made me miss lightroom catalog management (for my use case)

that said, culling, editing, and exporting in capture one feel great! just gotta figure out how to do this workflow in a multi-device friendly way (i often import on my laptop)