Selective adjustments, album names and metadata handling
I'm having a real struggle with C1. It seems to want to fight me every step of the way no matter what I do.
1) I want to set the "Diffraction Correction" on all images. I select all images, check the box. Nope. It didn't set it for the selected images, only for the one having the cursor. OK, let's copy that adjustment then. Nope. When I copy/apply adjustments I can't choose which adjustments to copy/apply, so it'll just overwrite all adjustments I've made. Dunno, I give up.
2) Maybe I can change the Lens profile at least, since for some reason C1 defaults to "Manufacturer Profile" instead of the one for my lens. So I create a smart album with all images taken by, say, my 45/1.8 lens. I can choose a lens criteria, great, but of course it won't suggest either of the 2 lenses present in all the pictures.. So I go to copy the lens details from the metadata tool. Nope. Can't copy. So you won't suggest the name and you won't let me copy it. Thanks a lot... I have to write it down somewhere else, then copy that and go back to the smart album editor and paste it there. Argh!
3) OK, so I name my smart album "45/1.8". Nope. Can't have such a name. It won't even say what's wrong with the name, because, hey, we've already decided we want to make things as difficult as possible for the user, right? So I finally figure out that an album name can't contain "/". WHYYY??? What on earth could compel a developer to forbid one of the most common characters in photography from a name in a photography app?!?!? If it's because you chose to translate the name directly to a folder in the underlying filesystem (which is the only thing I can think of even though that would be incredibly stupid) then that's your idiotic decision, so why do I have to suffer from that? I could expect this level of careless stupidity from a single teenager developer publishing his first app on google play for free, but never from a big product people actually have to pay for.
1) I want to set the "Diffraction Correction" on all images. I select all images, check the box. Nope. It didn't set it for the selected images, only for the one having the cursor. OK, let's copy that adjustment then. Nope. When I copy/apply adjustments I can't choose which adjustments to copy/apply, so it'll just overwrite all adjustments I've made. Dunno, I give up.
2) Maybe I can change the Lens profile at least, since for some reason C1 defaults to "Manufacturer Profile" instead of the one for my lens. So I create a smart album with all images taken by, say, my 45/1.8 lens. I can choose a lens criteria, great, but of course it won't suggest either of the 2 lenses present in all the pictures.. So I go to copy the lens details from the metadata tool. Nope. Can't copy. So you won't suggest the name and you won't let me copy it. Thanks a lot... I have to write it down somewhere else, then copy that and go back to the smart album editor and paste it there. Argh!
3) OK, so I name my smart album "45/1.8". Nope. Can't have such a name. It won't even say what's wrong with the name, because, hey, we've already decided we want to make things as difficult as possible for the user, right? So I finally figure out that an album name can't contain "/". WHYYY??? What on earth could compel a developer to forbid one of the most common characters in photography from a name in a photography app?!?!? If it's because you chose to translate the name directly to a folder in the underlying filesystem (which is the only thing I can think of even though that would be incredibly stupid) then that's your idiotic decision, so why do I have to suffer from that? I could expect this level of careless stupidity from a single teenager developer publishing his first app on google play for free, but never from a big product people actually have to pay for.
0
-
1) Make sure "Edit All Selected Variants" is on (icon in the tool bar, or Edit menu). To select adjustments to copy/paste, open the "Adjustments Clipboard" tool.
2) Try the "Filters" tool, maybe?
3) Seems dumb, I agree.0 -
[quote="John Doe" wrote:
1) Make sure "Edit All Selected Variants" is on (icon in the tool bar, or Edit menu). To select adjustments to copy/paste, open the "Adjustments Clipboard" tool.
I already made sure the "Edit All Selected Variants" was checked, although if I've understood the concept correctly I only have 1 variant.
I knew I had seen the checkbox list of adjustments somewhere, I just couldn't find it from any action in any menu. Didn't think to look for it as a separate tool. Thanks!
Earlier I spent some time learning OpticsPro, which took about 30 minutes because everything in it is so well thought out and logically structured that there was virtually no learning curve at all, at least for me. Then coming to CaptureOne has been a huge challenge. Neither because things are different, nor because it's more powerful, but simply because of inadequate UI design. As if they decided that the one thing to copy from adobe was the lack of proper UI design. (But no, C1 is not nearly as horrible as anything by adobe. Fortunately. Could still be better, though.)[quote="John Doe" wrote:
2) Try the "Filters" tool, maybe?
Ah, from the Filters' ...-menu I can add a lens filter. Awesome! Thanks, man!!!
I still think one should be able to copy anything that one can select, and that includes metadata values.[quote="John Doe" wrote:
3) Seems dumb, I agree.
Hopefully they will fix it in a future version.0 -
In addition to John Doe's observations.
1) You can select an individual tool and apply changes to multiple images for that tool only.
If you select an image and all its adjustments you can continue via the Clipboard to select only those adjustment you wish to apply (although not always specific sub-adjustments within a tool).
In general if an adjustment simply means writing a value to a file (rating, colour tag, keyword, and similar) all selected variants will be updated as you apply the change.
If you are making an adjustment that will cause C1 to recalculate the image significantly and variably image by image, for performance reasons in general the concept is to make the changes to one image and then apply in a batch to the others.
BTW, for diffraction correction, since you mentioned it, there is a general recommendation not to apply it unless you know you need to. There is a performance overhead which may or may not matter to your workflow/hardware but in general is probably worth avoiding.
2) "Manfacturer Profile" will be the Manufacturer's own profile, if there is one, for the lens you have used (where identified).
If C1 has a Phase created profile as well and you prefer that profile you should be able to set it as the default for that lens. Bear in mind there may, on some occasions, be problems identifying the correct lens based on the information made available from the camera.
Like John Doe I would also suggest the Filters tool (there are many options available for which fields you wish to have available for filtering) but in addition. However you can also create a filter once and save it as a User Preset filter for repeated use. This you could filter to Lens identification and a specific aperture for example. You probably do not need to be too specific unless you use a lot of similar lenses with nearly identical names.
3) As a Windows OS user a do not seem to have any problems using "/" in a Smart Album name. The machine I am using currently has V9 running but I would not anticipate a difference with V10.
That said one wonders if using it awkwardly somewhere else in a string (Applescript for example?) might understand 45/1.8 as a mathematical instruction to divide 45 by 1.8
That said my personal opinion is that using "/" in a naming convention offers enough potential unexpected problems with code in other applications and for other purposes that I would try to avoid it. For naming an Album it is eminently avoidable, IMO.
I think you might benefit from stepping back and considering things afresh. I discovered a lot by doing that after several months of C1 usage a few years ago. C1, being an inanimate "thing" was not fighting me. I was fighting C1 and I discovered there was no need to.
Of course you may have a different experience.
HTH.
Grant0 -
About the / in the album names:
A possible issue may arise if you use the name of the album as a folder in a process recipe; on the Mac, the / stands for a subfolder, so your 45/1.8 album name would result in a folder "45" which would then contain a subfolder "1.8". Presumably, they chose to avoid these kinds of issues by not allowing such "special characters". On a PC, that would mean you wouldn't be able to use a \ (or "c:" ?).
But indeed it's a bit silly to forbid the use of such characters in album "just in case". It's easy enough to replace such characters by say an _ when you actually need to write a file. You would then get a folder named "45_1.8".
I don't think that users should be concerned about the way they name their albums or other stuff. It's up to the app to handle it gracefully (and I do know what that involves).
Cheers,
Peter.0 -
[quote="SFA" wrote:
for diffraction correction, since you mentioned it, there is a general recommendation not to apply it unless you know you need to. There is a performance overhead which may or may not matter to your workflow/hardware but in general is probably worth avoiding.
Usually I don't care about performance at the export stage, unless it gets ridiculously slow. I can just leave it running over night. But you're probably right that I can have it turned off at least while editing the image, and then possibly enabling it selectively for certain apertures just before exporting. It would be really nice if this was a 3-state value: yes/no/auto, where the latter would choose to use it automatically based on your lens, aperture and sensor.[quote="SFA" wrote:
2) "Manfacturer Profile" will be the Manufacturer's own profile, if there is one, for the lens you have used (where identified).
If C1 has a Phase created profile as well and you prefer that profile you should be able to set it as the default for that lens. Bear in mind there may, on some occasions, be problems identifying the correct lens based on the information made available from the camera.
Hmm.. I see.. Do you have any idea where this manufacturer profile comes from? If the manufacturer profile is better then why would Phase create their own? And do you know how I can set it to use Phase's profile by default?[quote="SFA" wrote:
As a Windows OS user a do not seem to have any problems using "/" in a Smart Album name. The machine I am using currently has V9 running but I would not anticipate a difference with V10.
That's interesting. If different platforms have different limitations it means I can't move from one platform to another. That's very, very bad. Not only do I need to move between platforms, I need to do it continuously while editing the same pictures from different platforms.[quote="SFA" wrote:
That said one wonders if using it awkwardly somewhere else in a string (Applescript for example?) might understand 45/1.8 as a mathematical instruction to divide 45 by 1.8
That said my personal opinion is that using "/" in a naming convention offers enough potential unexpected problems with code in other applications and for other purposes that I would try to avoid it.[quote="peter.f" wrote:
A possible issue may arise if you use the name of the album as a folder in a process recipe; on the Mac, the / stands for a subfolder, so your 45/1.8 album name would result in a folder "45" which would then contain a subfolder "1.8". Presumably, they chose to avoid these kinds of issues by not allowing such "special characters". On a PC, that would mean you wouldn't be able to use a \ (or "c:" ?).
A string should be handled as a string, not as code/instructions. Any and all user input should be considered malicious by the developer and be escaped/isolated. None of that should affect users. This is really, really basic development principles here.
As Peter says:[quote="peter.f" wrote:
But indeed it's a bit silly to forbid the use of such characters in album "just in case". It's easy enough to replace such characters by say an _ when you actually need to write a file. You would then get a folder named "45_1.8".
I don't think that users should be concerned about the way they name their albums or other stuff. It's up to the app to handle it gracefully (and I do know what that involves).
Indeed.[quote="SFA" wrote:
I think you might benefit from stepping back and considering things afresh. I discovered a lot by doing that after several months of C1 usage a few years ago. C1, being an inanimate "thing" was not fighting me. I was fighting C1 and I discovered there was no need to.
If I just pull down my pants and let C1 have its way with me it's all nice and dandy, it's considered raping only if I fight back?
I'm all for learning new and better way of doing things, but not pointless idiocies like not allowing me to use whatever characters I want in my own album name. Or forcing me to have pointless, empty subfolders in my session folder. (Capture? No, I've already captured what I want to capture! Selects? No, just keep everything in the same folder, please! Trash? No, just use the system trash. Output? OK, but let me specify its name and location, please.)0 -
[quote="peter.f" wrote:
About the / in the album names:
A possible issue may arise if you use the name of the album as a folder in a process recipe; on the Mac, the / stands for a subfolder, so your 45/1.8 album name would result in a folder "45" which would then contain a subfolder "1.8". Presumably, they chose to avoid these kinds of issues by not allowing such "special characters". On a PC, that would mean you wouldn't be able to use a \ (or "c:" ?).
But indeed it's a bit silly to forbid the use of such characters in album "just in case". It's easy enough to replace such characters by say an _ when you actually need to write a file. You would then get a folder named "45_1.8".
I don't think that users should be concerned about the way they name their albums or other stuff. It's up to the app to handle it gracefully (and I do know what that involves).
Cheers,
Peter.
Possibly right although I note that one difference on that technical front between Mac and Windows is that Mac offers Applescript more or less as an end user feature.
Equivalent tools for Windows are left for users with technical inclinations to go and discover.
Now I don't know and I'm no technical wizz for scripting but I do wonder whether Applescript would handle the "/" gracefully by itself rather than rely on a user, perhaps lacking a good level of proficiency, to deal with it.
At a guess the potential for a dodgy script to completely trash a large catalogue is might be significant. Not a nice idea for a "supported" feature (of a Mac OS) over which the original software developers for an application have no control when deployed by a user.
Purely guessing on my part - I assume someone from the Mac world will be able to comment appropriately.
Grant0 -
[quote="msundman" wrote:
[quote="SFA" wrote:
for diffraction correction, since you mentioned it, there is a general recommendation not to apply it unless you know you need to. There is a performance overhead which may or may not matter to your workflow/hardware but in general is probably worth avoiding.
Usually I don't care about performance at the export stage, unless it gets ridiculously slow. I can just leave it running over night. But you're probably right that I can have it turned off at least while editing the image, and then possibly enabling it selectively for certain apertures just before exporting. It would be really nice if this was a 3-state value: yes/no/auto, where the latter would choose to use it automatically based on your lens, aperture and sensor.[quote="SFA" wrote:
2) "Manfacturer Profile" will be the Manufacturer's own profile, if there is one, for the lens you have used (where identified).
If C1 has a Phase created profile as well and you prefer that profile you should be able to set it as the default for that lens. Bear in mind there may, on some occasions, be problems identifying the correct lens based on the information made available from the camera.
Hmm.. I see.. Do you have any idea where this manufacturer profile comes from? If the manufacturer profile is better then why would Phase create their own? And do you know how I can set it to use Phase's profile by default?[quote="SFA" wrote:
As a Windows OS user a do not seem to have any problems using "/" in a Smart Album name. The machine I am using currently has V9 running but I would not anticipate a difference with V10.
That's interesting. If different platforms have different limitations it means I can't move from one platform to another. That's very, very bad. Not only do I need to move between platforms, I need to do it continuously while editing the same pictures from different platforms.[quote="SFA" wrote:
That said one wonders if using it awkwardly somewhere else in a string (Applescript for example?) might understand 45/1.8 as a mathematical instruction to divide 45 by 1.8
That said my personal opinion is that using "/" in a naming convention offers enough potential unexpected problems with code in other applications and for other purposes that I would try to avoid it.[quote="peter.f" wrote:
A possible issue may arise if you use the name of the album as a folder in a process recipe; on the Mac, the / stands for a subfolder, so your 45/1.8 album name would result in a folder "45" which would then contain a subfolder "1.8". Presumably, they chose to avoid these kinds of issues by not allowing such "special characters". On a PC, that would mean you wouldn't be able to use a \ (or "c:" ?).
A string should be handled as a string, not as code/instructions. Any and all user input should be considered malicious by the developer and be escaped/isolated. None of that should affect users. This is really, really basic development principles here.
As Peter says:[quote="peter.f" wrote:
But indeed it's a bit silly to forbid the use of such characters in album "just in case". It's easy enough to replace such characters by say an _ when you actually need to write a file. You would then get a folder named "45_1.8".
I don't think that users should be concerned about the way they name their albums or other stuff. It's up to the app to handle it gracefully (and I do know what that involves).
Indeed.[quote="SFA" wrote:
I think you might benefit from stepping back and considering things afresh. I discovered a lot by doing that after several months of C1 usage a few years ago. C1, being an inanimate "thing" was not fighting me. I was fighting C1 and I discovered there was no need to.
If I just pull down my pants and let C1 have its way with me it's all nice and dandy, it's considered raping only if I fight back?
I'm all for learning new and better way of doing things, but not pointless idiocies like not allowing me to use whatever characters I want in my own album name. Or forcing me to have pointless, empty subfolders in my session folder. (Capture? No, I've already captured what I want to capture! Selects? No, just keep everything in the same folder, please! Trash? No, just use the system trash. Output? OK, but let me specify its name and location, please.)
For 2)
The manufacturer information, when available, comes from the lens via the camera. This is typically something that was introduced to allow lenses to be simplified and reduced in size and then take advantage of processing software in the digital world to "fix" the built in lens limitations. Ever more pixels available on digital sensors made this possible without compromising the eventual quality of the results for professional level expectations.
There are occasions when Phase may feel they can offer more, at least for use with Capture One, then the manufacturer delivers as their "default" corrections. Colour rendition and other aspects may be covered as well as distortion for example. So if they think they can offer a better alternative AND the lens usage profile justifies it (no point if there are very few users and a not so popular lens UNLESS it is something rather specific to high end Professional usage) then Phase may elect to undertake the work to offer their own corrections. For more info in that you would need to ask Phase.
For usage across platforms - most people have no problems. Or at least there are few reports of any problems at all on these User to User forums where people are working with both Mac and Windows.
There have always been different ways of doing things in each of the operating systems and although totally portable code can be written there are times when making use of code built in to the OS is the key for high performance and reliability. (There can also be times when the converse is true but they usually see quite rapid correction after a surprise appearance.)
It may be an oversight rather than a specific decision. Create a Support Case with the C1 Support Team and point out the problem and let them advise you accordingly.
As for you final comment, really I strongly suggest you step back and consider things from a different angle.
For example I lost interest in LightRoom because I was forced to use a catalogue structure. No option. I like options.
C1 provides options. It attempts to help out by offering some commonly used options but you can ignore them if you wish. The folder you mention are not used unless you choose to use them.
If you use a session the Selects, Output and Trash folder in the Session folders are specific to that session - easy management options if you want them. Just ignore them if you don't. You can also re-associate the links in the "Session Folders" part of the menu to other folders elsewhere on your system if you wish. (I hardly use catalogues but assume something similar is possible).
I hardly ever use Selects, sometimes use Trash and frequently use the Output folder with subfolders created during the output process as it makes life so much easier.
I think you may have missed the potential benefit of the Trash folder (intermediate between C1 activity and general system activity so things don't always get trashed unless finally committed to trash - many people seem to have workflows that may involve changing decisions later.) but if you want a delete to be permanent and instant you can make it so.
You also have have complete control over your outputs if that is what you want. For those that are less concerned and want the location specified to save them thinking about it a folder is provided and an option to make a virtual link to that folder point to any folder they choose.
We all have different workflows and C1 makes a great effort to cater for that and allow users to tailor what they see to what they want to see.
As I suggested previously the idea of stepping back and considering what really matters to your workflow and whether a few empty folders really are as big a problem as your florid description indicates may well provide you with a different perspective. I did not have the same concerns as you but, as mentioned previously, after a few months of use and some moments of puzzlement from time to time, I stepped back and re-discovered the concept behind the default functionality supplied alongside what I had learned up to that point and all became clearer.
HTH.
Grant0
Post ist für Kommentare geschlossen.
Kommentare
7 Kommentare