Capture One 13 – wish list.
Maybe I'll start… 😊
1. Changing crop proportion by keyboard.
2. Ability to save (and auto load) noise reduction settings for different ISO values and a particular body.
3. Better effects of geometric correction and noise reduction.
4. Focus and HDR stacking (with auto-align).
5. Bigger area of white balance picker.
1. Changing crop proportion by keyboard.
2. Ability to save (and auto load) noise reduction settings for different ISO values and a particular body.
3. Better effects of geometric correction and noise reduction.
4. Focus and HDR stacking (with auto-align).
5. Bigger area of white balance picker.
0
-
5. Super dream tool but might not be practical. When working in layers, I can Edit in.... and then come back to CO natively. I have yet to understand the practicality of converting the image in CO into a TIFF or JPG and then edit it in the editor. I prefer to do what CO is capable and then edit in the editor.
Wouldn't that require the other app (Photoshop, Affinity Photo or whatever) to be able to read Capture One edits? Not something that Capture One could arrange for, I'd have thought.
Ian0 -
- Aggregate image count for any folder comprising subfolders with images in them.
MLi0 -
Some are already mentioned but to support the ideas, repeated again:
1. sidecar (edits) import/export
2. copy-paste selected adjustments between images (based on adjustment categories or layers)
3. sync/import folder images by including subfolders
4. option to export-overwrite
5. more skin retouching capabilities
6. improve the healing/cloning tool
------------------------
Other stuff:
* Make the catalogue rock solid no matter the size.
* Proper print module
* Web gallery export
Thanks.0 -
I'll repeat a few points to give them more importance:
1. Significantly improved noise reduction
2. Ability to save (and auto load) noise reduction settings for different ISO values and a particular body.
3. Edge sharpening (or do that already exist and I don't get it)
4. Bigger area of white balance picker
5. Publishing PlugIn: That nobody seems to have a commercial interest in a plugin for "Publishing", PaseOne has to program it itself.0 -
Why not solve/repair all known problems/bugs at first? 0 -
[quote="ex-ratt" wrote:
2. The luma-masking is really nice, and the logical next step would be to extend this to colors. Going through the color editor to create a mask based on a color is a bit cumbersome and does not allow for changing the mask while seeing how that would look with your edits. It would be great if this would work similar to the luma mask.
3. The ability to add or subtract a mask from another layer. Right now I might have one layer for a flower and another for a bee that hovers in front of the flower. Now if I want to have a layer that affects everything else, I cannot just add those two masks and invert the result. Instead, I have to draw a completely new mask (which costs a lot of time) or I have to think about this possibility from the very beginning and create both masks (flower and bee) in the same layer and separate them afterwards. This is probably a feature that is very simple to add - no need to wait for version 13 😉
This would be really really nice. I definitely would love those features. A Dehaze tool would be really spiffy as well.
Another feature that I would really like is the ability to nest layers. Lets say I want to edit a certain red object in a photo with a bunch of other red things... it'd be nice to be able to paint a mask and then do a color selection within that mask only.
If that's possible and I've just been to daft to realize it, can someone hit me with a guide/tutorial on it?
By biggest request would be triple monitor support though. I sent a ticket to Support about it including an example of how it could be done (Im a developer myself). I know its not a complicated task considering what is already in place. It's just a matter of getting the Product Manager to agree and assign developer time to it.0 -
[quote="NNN636228568741858362" wrote:
Another feature that I would really like is the ability to nest layers. Lets say I want to edit a certain red object in a photo with a bunch of other red things... it'd be nice to be able to paint a mask and then do a color selection within that mask only.
If that's possible and I've just been to daft to realize it, can someone hit me with a guide/tutorial on it?
Check out the section titled "Apply to layers"
https://learn.phaseone.com/capture-one/ ... itor-co11/
I think that's what you want it lets you pick a colour range but only for the part of the image you have masked for that layer.0 -
[quote="IanL" wrote:
[quote="NNN636228568741858362" wrote:
Another feature that I would really like is the ability to nest layers. Lets say I want to edit a certain red object in a photo with a bunch of other red things... it'd be nice to be able to paint a mask and then do a color selection within that mask only.
If that's possible and I've just been to daft to realize it, can someone hit me with a guide/tutorial on it?
Check out the section titled "Apply to layers"
https://learn.phaseone.com/capture-one/ ... itor-co11/
I think that's what you want it lets you pick a colour range but only for the part of the image you have masked for that layer.
Nice! Thanks for the info!0 -
1) API to allow photoshop plug ins (DXO nik effects, topaz, jsx actions) to work in C1
2) ability to use one image as a mask/layer in another image - or perhaps using one image as a clone/heal source to a target in another image0 -
1. Stacks, as in Aperture, to allow you to group related sets of images together
2. An easy way to do a side by side compare an image with and without soft proofing and also with different rendering intents0 -
- Add and substract masks from other layers
Let's say I have a portrait. I have 3 layers: skin, backdrop, clothes. I want to create a mask of the skin and backdrop together. It would be nice if I could create a new layer, and add masks from multiple other layers.0 -
1. Improve capture sharpening capabilities
2. Improve heal/clone tool.
3. Improve the Catalog/DAM
I'd be happy to start with these.0 -
Please can we have the ability to have different output naming formats for different Recipes. I want to output two sets of JPEGs to one folder. One Recipe will output fixed, 100% scaling, the other will output 1000px on the Long Edge. Here is a sample filename from the first Recipe:
[HEADLINE]_large_[2 DIGIT COUNTER]
And here is a sample filename from the second Recipe:
[HEADLINE]_small_[2 DIGIT COUNTER]
The square brackets indicate the use of tokens and are the same in both Recipes. However, at the moment this does not work. The filenames have to be the same in both Recipes. Why?
My workaround for now is to output the Recipes to two folders called 'large' and 'small', and then combine the files into one folder, after bulk renaming them, later. This is not ideal and wastes valuable time.
Thanks,
Daniel Harvard.0 -
[quote="Dan Harvard" wrote:
Please can we have the ability to have different output naming formats for different Recipes. I want to output two sets of JPEGs to one folder. One Recipe will output fixed, 100% scaling, the other will output 1000px on the Long Edge. Here is a sample filename from the first Recipe:
[HEADLINE]_large_[2 DIGIT COUNTER]
And here is a sample filename from the second Recipe:
[HEADLINE]_small_[2 DIGIT COUNTER]
The square brackets indicate the use of tokens and are the same in both Recipes. However, at the moment this does not work. The filenames have to be the same in both Recipes. Why?
My workaround for now is to output the Recipes to two folders called 'large' and 'small', and then combine the files into one folder, after bulk renaming them, later. This is not ideal and wastes valuable time.
Thanks,
Daniel Harvard.
Have you looked at using the Sub Name field in the File tab of the Process Recipe tool and then the Sub Name token in the Output Naming tool?
That should allow you to do what you want. I use it all the time although I prefer to keep different sized images in separate folders rather than combine them.
Grant0 -
[quote="SFA" wrote:
[quote="Dan Harvard" wrote:
Please can we have the ability to have different output naming formats for different Recipes. I want to output two sets of JPEGs to one folder. One Recipe will output fixed, 100% scaling, the other will output 1000px on the Long Edge. Here is a sample filename from the first Recipe:
[HEADLINE]_large_[2 DIGIT COUNTER]
And here is a sample filename from the second Recipe:
[HEADLINE]_small_[2 DIGIT COUNTER]
The square brackets indicate the use of tokens and are the same in both Recipes. However, at the moment this does not work. The filenames have to be the same in both Recipes. Why?
My workaround for now is to output the Recipes to two folders called 'large' and 'small', and then combine the files into one folder, after bulk renaming them, later. This is not ideal and wastes valuable time.
Thanks,
Daniel Harvard.
Have you looked at using the Sub Name field in the File tab of the Process Recipe tool and then the Sub Name token in the Output Naming tool?
That should allow you to do what you want. I use it all the time although I prefer to keep different sized images in separate folders rather than combine them.
Grant
To add to Grant's reply, have you seen the webinar from last week? David Grover covers this kind of thing in detail.
Ian0 -
Thank you Grant. That indeed does what I am looking for. I watched the two webinars on Recipes not once but twice. The use of the subname token was not made clear in either of them - at least not to me.
However, I would still like the naming format to be completely independent across Recipes. In my example, if I change the counter token from a two digit counter to a three digit counter in one Recipe, it is also changed in the other. Also, if I run the Recipes one after the other, the count continues on in the second Recipe from where the first Recipe left off. This happens even though I have reset the counters in each Recipe to zero before starting. Each Recipe should be totally independent of others.
Many thanks again.
Daniel.0 -
Daniel
Unless one of the videos you watched was the one I linked to (broadcast in the last few days) I think you would find it helpful. He did explain really well how to get round your difficulty, I think. If you have watched that one and did not find it answered your problem, then I apologise.
Ian0 -
[quote="SFA" wrote:
Have you looked at using the Sub Name field in the File tab of the Process Recipe tool and then the Sub Name token in the Output Naming tool?
The last time I looked the sub name field did not offer the full list of tokens. Did I miss something or am I out of date? I would like to have total control of the name in the recipe and therefore would put all my naming tokens (dates, metadata, counters etc.) in the sub name. If I missed something or they added support for that with out me noticing that would be awesome.0 -
[quote="IanL" wrote:
[quote="SFA" wrote:
Have you looked at using the Sub Name field in the File tab of the Process Recipe tool and then the Sub Name token in the Output Naming tool?
The last time I looked the sub name field did not offer the full list of tokens. Did I miss something or am I out of date? I would like to have total control of the name in the recipe and therefore would put all my naming tokens (dates, metadata, counters etc.) in the sub name. If I missed something or they added support for that with out me noticing that would be awesome.
I can't imagine how a Counter in a Sub Name field would make any sense and indeed some of the IPTC fields that ARE allowed could be ridiculously long for a file name but I can't think of any tokens I would be likely to use as a sub name text component in a field name that are missing. In fact there are far more (and far more ways to use them) than I would ever be likely to use.
I'm interested to know specifically what you think might be missing and how you would use it.
Are you looking at V12 or an earlier version?
Grant0 -
I thought I could solve my problem (2 Digit Counter on one Recipe, a 3 Digit Counter on another and perhaps no counter on a third) by using the Subname field. But when I tried I found that the Counter token is not available to the Subname field. For my workflow this causes quite a problem.
BTW, I am using version 12.0.2.
Daniel.0 -
In version 13, please can we have an image count next to each Smart Album, as appears next to ordinary Albums. I use Smart Albums extensively and, coming from Lightroom, find this an odd omission.
Thanks,
Daniel.0 -
Hi:
Please, posibility use only one cataloge that is able to save "settings" in the each diferents photos folders, (not in catalog folder without use sessions.
Thanks0 -
and select "favorites in styles 0 -
I'd like to see generic fisheye lens distortion correction option. Just like there is for generic pin and barrel distortion.
For that matter barrel distortion slider goes up to 120. If it went up to 180 it would better correct fisheye, although it is a different distortion type, so not as good a true fisheye correction would be.
As it is now I need to use external SW to correct fisheye which annoyingly takes it out of CO workflow0
Post is closed for comments.
Comments
54 comments