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.
What problem do you see this solving?
When working with images in a session I have the problem that I cannot see images with are located in sub folders. I do have a folder hierarchy and use a "dummy" session to browse and work with my images, so adding sub folders to the Favorites are using static albums is not a viable solution nor a good workaround for this case.
Even with "normal" sessions I tend to add a hierarchy to the Capture folder (which I then preserve when copying the images incl. CaptureOne cache and settings folders into my final destination folders hierarchy.
The search in sub folders should be configurable so that users have a choice to use the current behaviour.
When was the last time you were affected by this lack of functionality, or specific tool?
Every time I work with my images in a session, so, 99% of the time I work with Capture One.
|
Current workaround
Are you using any workarounds or other solutions to achieve your goals in Capture One? Almost never. Albums and Favorites are not a viable workaround, maybe there were a if I was using "normal" sessions exclusively, but I work with a session as a browser, as explained by David Grover in a webinar a couple of years back. |
Absolutely, it should be configurable, maybe the same way as with catalogs. I have added this to the first post.
This idea would probably benefit from an approach that asks, every time, whether subfolders are to be made visible.
Since C1, using a session, assumes that the user will want to see any "supported images files" in any folder accessed, it will automatically assess the contents and start creating .cos files, thumbnails, previews, etc. for any files discovered. Inadvertently discovering a large folder and subfolders of all sorts of "image file" detritus that system create these days for caching purposes and so on, might be unhelpful.
Since I use the Session concept frequently for "Events" - more or less the self-contained shoot concept for which sessions developed - I also (usually) store my output processed files within the session. Maybe elsewhere as well for sharing purposes, but certainly with the session. The last thing I would want, in that situation, would be for an accidental opening of a higher level folder to automatically open subfolders looking for anything it can find and discovering several thousand tiffs and jpgs, each with multiple outputs of different sizes and resolutions, that it would then proceed to treat as editable images.
So, I have nothing against the concept, if that is the way that people wish to work, but the way it should be implementad and the controls made available to the users, need to be carefully thought through. Preferably avoiding complexity without compromising usability for the "average" user.
Upvoted, would love to see something like this so I don't need to keep a seperate folder with all my edited output photos.
Hi Benjamin,
Can you please upvote my request then?
Thanks
BeO
I have the same request this would be very helpful!