capture one workflow suggestion
Hi
as a capture one use I would like to suggest a local adjustments layers improvement -
when I work on a project that has for example 10 different photos but all with the same background I usually
mask the background and adjust it so it will be the same for all the photos but I have to go one by one and see
the details I used before , if it was possible to adjust all layers with the same name in working session
it would be a major upgrade
as a capture one use I would like to suggest a local adjustments layers improvement -
when I work on a project that has for example 10 different photos but all with the same background I usually
mask the background and adjust it so it will be the same for all the photos but I have to go one by one and see
the details I used before , if it was possible to adjust all layers with the same name in working session
it would be a major upgrade
0
-
It's in interesting idea for users to consider as this is a User to User forum.
However if you want to make an official Enhancement Request that the Capture One development team will register and consider the best thing to do is to create a Support Case and describe what you would like and how you would see it working.
I understand what you wish to do. I think something like that is a good idea and only somewhat possible at the moment if you already have the layers and edits applied to the images. (If you have not yet applied the adjustments it's a bit easier, maybe.)
However I suspect that for many people just using a common layer name as the basis for editing multiple images (presumably in a currently selected set of variants) might not give a strong enough relationship to both make the edits work AND avoid accidents with unintended changes.
Grant0 -
Sounds usable to me.
If you add layers with the same name and you know they're "connected" then there's nothing unintended about it, you just need to be smart / creative with layer names.0 -
WPNL wrote:
Sounds usable to me.
If you add layers with the same name and you know they're "connected" then there's nothing unintended about it, you just need to be smart / creative with layer names.
What occurred to me was the question about how smart the average person needs to be with simple names like "Sky" or "Face", etc.
Having the option to turn the grouping by name off might be OK but so many people have problems with the concept already (turning "Process all selected variants" on and off for example) that adding something simple without considering problems of simplicity (in this case) and assuming that everyone will always be in a totally layer name controlled mode of thinking .... seems to me to be a recipe to attract user opprobrium.
I suspect a very specific selection and confirmation system (even if based on just "name of layer" would be highly advisable.
Grant0 -
I don't see a problem, there might even be a toggle "linked layer styles" or whatever.
With the exception of the layer mask of course...0 -
WPNL wrote:
I don't see a problem, there might even be a toggle "linked layer styles" or whatever.
With the exception of the layer mask of course...
Not a problem if it's fully considered, totally defined as a process and comprehensive in functionality and presentation.
Taking into account all possible inputs and making clear decisions about any compromises required.
Getting it "right" as a well designed and controlled process in the eyes of all users may require some considerable effort.
Grant0 -
SFA wrote:
Getting it "right" as a well designed and controlled process in the eyes of all users may require some considerable effort.
Grant
That's the case with alle development and should not be a reason to consider implementation.
And... That's why there's a BETA program I guess.0 -
WPNL wrote:
SFA wrote:
Getting it "right" as a well designed and controlled process in the eyes of all users may require some considerable effort.
Grant
That's the case with alle development and should not be a reason to consider implementation.
And... That's why there's a BETA program I guess.
Theory and practise in a user driven development environment does not always (or even often?) result in a positive experience for absolutely everyone on a first pass.
This potentially mass process activity seems to have plenty of potential for making a big mess for the less aware (of the functionality) users to have to clear up.
But other than that we seem to be agreeing about the need for proper and full design considerations and concept testing.
Grant0 -
happy to read all your replies
I am finding myself working on a top view shots with the need to have the same background in all photos
and moving back and forth on the numbers to copy them
I think it is an advanced option for an advanced software like this
any idea on who and how to suggest?0 -
NNN634662846640277259 wrote:
happy to read all your replies
I am finding myself working on a top view shots with the need to have the same background in all photos
and moving back and forth on the numbers to copy them
I think it is an advanced option for an advanced software like this
any idea on who and how to suggest?
Create a Support Case.
All C1 support activities, including enhancement suggestions, are managed using their Support Case system.
Use the Contact Support link from the Help menu in C1.
Grant0
Post is closed for comments.
Comments
9 comments