Future improvements of C1
Implemented
I’ve been using Capture One since version 5, and it’s been my 100% RAW converter since version 10.
Here are some improvements I’d like to see in future C1’s
- When I crop an image and then use the Healing brush, C1 will often select the target point outside of the crop, which I can’t see and can’t change. Using Heal before crop seems to be a dog’s dinner approach to fixing this, so please change C1 Heal so that the target point always starts from inside a crop.
- I would like to be able to choose to have more information in the Browser, especially current image size in MB. But other metadata details are often useful, so being able to choose what is in the browser under a thumbnail (like in Bridge) would be of great benefit to me.
- In the Naming Format token box there need to be instant additional information that explains what a specific token will do. Many tokens are self-explanatory, but many – even common ones – are not. For example Document Name makes more sense as “Keep the same name as it is.” than Image Name. Please explain, as the tokens can be cryptic.
- When a custom Process Recipe is set up to create a sub folder, after processing that sub folder should be instantly visible in Capture One’s Library. Having to drag or paste sub folders onto the C1 output folder in Windows explorer is time consuming, confusing and unnecessary. It should be: Create a sub folder, See the sub folder.
-
David,
Your first point,
I would prefer that we are allowed the flexibility to use any point available in the RAW data - not just somewhere in the (current) crop area.
I disagree with your last point unless it is an option set as a default using specific criteria. I have no interest in making output files an automatic edit candidate. In most cases is I should use a round-tripping process to permit external editing using the original image folder for the interim file location makes sense and that will more often than not in most workflows already be known to C1.
I offer these observations with a view to avoiding changes that might disrupt some workflows with no options available to choose to retain existing functionality.
1 -
1) Using any point in the RAW data would be great if you could access those points. You can't. If I could see the entire image (with a crop just drawn) and then the anchor point was outside of that crop then that would be fine. Right now if the Heal picks the wrong anchor point outside of the crop there's no way to fix it unless you completely back out of the layer. Right now it's Heal first Crop second, and for me Heal is often a lot later in my post production.
2) I'm not really sure if I understand your second point. If I set up a custom Process Recipe to include making a new sub folder (eg: Large Jpegs) I just want to see it. That sub folder is there as soon as I run that Recipe, C1's Library just doesn't show that it's there. That's what I want automated. Not the creation of a sub folder, just the recognition and visibility of the sub folder. I would think the creating or not creating a sub folder makes it an option already. To be clear when I create a folder I want to see it so that I'll know that the output files are correct and where they should be, and I'd like to have that done without having to go through that kludgy dog and pony show that C1 requires now. Right now I have to have Adobe Bridge opened to provide this feature.
0 -
Hi David,
Thank you for the feedback on Capture One.
I have forwarded your comments to the Product Management team for consideration in the future versions of Capture One.
As for tokens, here is a page Tokens and their definitions which you may find useful. Also, more articles on tokens will be added onwards.
Thanks,
Lily
0 -
Regarding bullet #4, I agree with SFA. Not every user should be forced to find output files automatically added to their catalogue. Could be an optional feature, but clearly the default should be that output directories are not automatically added to a catalogue.
Including output files will make catalogues larger, including additional needs for preview generation.
0 -
David,
The point is that any file types that are editable in C1 that appear in associated folders are automatically assumed to be targets for editing.
On that basis C1 will establish its control files, thumbnails and previews.
This is perhaps more obvious when using Sessions than it would be for Catalogues.
I really don't want C1 to establish those entries for Output files that I do not expect to edit - certainly not using C1. And since a folder (the identification for editing potential is at folder not file level) might contain several thousand images I would like to be sure that the current principle of NOT automatically adding the Output folder's contents to the Catalogue or Session database is retained.
When I output files I check them in applications outside C1 since any other eventually viewing the files are unlikely to be doing so in C1. More likely they will use an internet browser or perhaps am Image viewer tool like Faststone or similar.
Therefore it is much better to use something along those line to check the results. IMO.
0 -
I don't use or care about catalogues. I use file trees and I just want to see these created folders. THEY ARE THERE on the hard drive, and I haven't added any thing to the storage. It doesn't make any sense to me that a third party program would be needed to view them. And you can view them once C1 is properly instructed to look. In any case C1 could easily mandate that none of these output files go into a catalog. That would make me happy and hopefully everyone else.
0 -
David,
This has nothing to so with catalogues per se.
I don't use them either.
However the principle is much the same whether you use a catalogue or a session as you do.
When you output images to you always send them to the same folder?
If so you can simply make the folder a Favourite in your session, the session will then have a permanent note to always look at it and when ever you add something to it and open the session any additional files will appear.
C1 will assume that the file might be something you want to edit and so with make preparations accordingly for possible future editing activity and visibility in the viewer/browser of your C1 session.
If that suits you that's fine.
When I export a jpg most of the time I have no expectation of making further edits in C1 so I really do not want C1 to prepare for a potential edit activity. I often do ant to see the files, instantly and quickly, in a Viewer program of some sort. Windows standard viewer perhaps for many people but I prefer others. That shows me what people are likely to see if they look at the images on their machines or via a browser.
Either way is OK. All you need to do is make your session manage database aware of the existence of your output folder.
HTH.
0 -
One of the strengths of Capture One over Lightroom is that I don't have to play the Catalog/Collections game. I use nothing but sessions and even then I only use parts. I import using PhotoMechanic as it has a much better culling and captioning capability. The only thing that Capture One ever sees are one star RAW files and they go into the Capture Folder. Since they ARE Selects the Select Folder is never used, nor is Trash since deleting files is something that I'll do much (weeks) later.
Under Output I create as many sub folders as I'll need based on the type of file (psd,jpg, et al) and size (small, medium jpg, and so forth) that I'll write a Process Recipe for. Each Session is likely to be outputted differently depending on the client. Some will want psd files, some tiffs. Many want three sizes of jpgs. Some require custom sizes (how's this: 200 dpi and 15inches on the long side. Ever get a request for that size?) In any case I may have one or five different output folders. I used to use Bridge + Photoshop to do this by using Image Processor. Capture One is better because I don't have to leave the program.
Now if there's something that I could check that says "Make Output sub folders visible to Library" I would just check it and I would be happy. You wouldn't check it and you would be happy. That's all I want.
0
Post is closed for comments.
Comments
8 comments