Improve Capture One
Request a new feature, or support for a camera/lens that you would like to use in Capture One.
Request a new feature, or support for a camera/lens that you would like to use in Capture One.
I would strongly suggest that they implement an API that allows programs like Photo Mechanic to implement great integration.
Among other things, one should be able to view a fully rendered version of the image in Photo Mechanic (with Capture One doing the rendering which Photo Mechanic could probably cache), one should be able to open the image in Capture One (whether using sessions or catalogs in Capture One) for further editing and edited changes in Capture One should show up when viewing in Photo Mechanic. There should also be metadata syncing between the two programs. I'm sure those with more sophisticated needs could come up with a few more things the API should cover.
This would be a great way for Capture One to cover their bases with photo management without implementing the details themselves. Provide an API so third party tools can interface with sessions and catalogs.
|
Current workaround
The problem: when I open old RAWs from PM+ in Capture One, it either creates duplicates or, if I select “Do not import duplicates”, nothing happens — it doesn’t jump to the existing file in the catalog. With Sessions, it does jump correctly, but I’m not sure Sessions are practical for managing my whole library, and I don’t like how deleted files go into “Trash.” What I really want is a clean round-trip: Edit → show the existing photo in C1 (or LR) → export → close the editor → return to PM+ to keep managing everything. So now I need to work with sessions, Editing from Photo Mechanic opens capture one, editing the photo. The entire catalog I built is useless, Since editing a photo from Photo mechanic from Capture one, Just tries to re=import the same photo and doesn't even jump to its location in the catalog. |
