The UI fixes I'm waiting for since years (2018 ?)
[Long post]
Hi,
Here is my list of UI problems reported (case created) since 2015 and still waiting to be fixed :
=====================================================================
12-26-2015 - External editors setup
In Lightroom, you can define the external editors independently so they always appear in the Edit in... menu. You don't have to actually Edit in... an image to define an external editor and once defined, the external editor will be available for all images.
Unless I missed something, if I Edit in... a given image in an external editor that is not initially recognized by C1, this editor will not be available in the Edit in.. or Open with... menu for other images, which is rather surprising to say the least. The newly defined editor should be recorded by C1 and made available for all other images instead of C1 relying on information provided by the OS.
Actually, the newly defined external editor is not even available in the Edit in... or Open with... menus for the image for which I defined it. The only thing that it remembers are the export settings for external editing.
This is neither practical nor logical and should be fixed, IMHO. When a user specifies an external editor once, he's very likely to do that again with the same external editor for other images.
=====================================================================
12-31-2015 - Editable color labels
In Lightroom and other software from competitors, the color tag labels are editable, so the user can define more meaningful labels than red, orange, yellow, etc. For example, in my LR setup, the red tag is labeled "To be processed in PS". In C1, this doesn't seem to be possible, unless I missed something.
=====================================================================
01-08-2016 - Print settings not sticky
The print settings for a given image are not sticky. Assuming you open the Print dialog, modify the default settings (including the printer) and you suddenly realize that you have to modify something in the image before printing. You hit Cancel, make the desired modifications and then open the Print dialog again : no luck, all your settings are lost and you have to start again from scratch. Even the target printer is not remembered. Extremely irritating.
=====================================================================
02-19-2016 - Assigning a recipe to a specific file
Currently, C1 does not allow to assign a particular process recipe as a default for a given image (or did I miss something ?). This is rather annoying because the user might forget to activate the correct process recipe when working on a particular image. This will impact some editing tools and especially the information displayed in the crop panel. This may lead to wrong decisions. Other C1 users in my environment have already expressed the same remark.
If assigning a default process recipe to an image was possible, this would be much more comfortable for the user. This process recipe would be automatically activated when selecting that image. If no default process recipe has been specified for a given image, then the current active (global) process recipe would apply. If multiple images are selected and all these images have the same default process recipe, that process recipe would apply. If they have different default process recipes, then the global active process recipe would apply.
Implementing this feature doesn't involve much coding, I think, and this would avoid many problems or mistakes.
=====================================================================
12-04-2016 - Grid overlay type in Preferences (odd)
I'm wondering why the grid overlay type (3x3, 4x3, golden ratio, etc.) must be set in the Preferences dialog. This just doesn't make sense and is a loss of time. Each image requires a different composition and the grid type that can be used to help during this process vary from image to image. So this setting should be "local", that is, it should be easily set while using the Crop tab. This would be much more consistent. Why force us to open the Preferences dialog each time ? Probably the person who made this design decision has never used the grid overlay on a regular basis. In Lightroom there a shortcut to quickly cycle among the grid overlay types.
=====================================================================
UI font size
Still not editable
=====================================================================
Better dual monitor support (Windows)
Still impossible to have the main window on the main monitor (the one that usually has the best quality) and the tools + the browser on the secondary monitor.
Thanks in advance to the UI development team for making the coming year better when using the C1 UI.
Hi,
Here is my list of UI problems reported (case created) since 2015 and still waiting to be fixed :
=====================================================================
12-26-2015 - External editors setup
In Lightroom, you can define the external editors independently so they always appear in the Edit in... menu. You don't have to actually Edit in... an image to define an external editor and once defined, the external editor will be available for all images.
Unless I missed something, if I Edit in... a given image in an external editor that is not initially recognized by C1, this editor will not be available in the Edit in.. or Open with... menu for other images, which is rather surprising to say the least. The newly defined editor should be recorded by C1 and made available for all other images instead of C1 relying on information provided by the OS.
Actually, the newly defined external editor is not even available in the Edit in... or Open with... menus for the image for which I defined it. The only thing that it remembers are the export settings for external editing.
This is neither practical nor logical and should be fixed, IMHO. When a user specifies an external editor once, he's very likely to do that again with the same external editor for other images.
=====================================================================
12-31-2015 - Editable color labels
In Lightroom and other software from competitors, the color tag labels are editable, so the user can define more meaningful labels than red, orange, yellow, etc. For example, in my LR setup, the red tag is labeled "To be processed in PS". In C1, this doesn't seem to be possible, unless I missed something.
=====================================================================
01-08-2016 - Print settings not sticky
The print settings for a given image are not sticky. Assuming you open the Print dialog, modify the default settings (including the printer) and you suddenly realize that you have to modify something in the image before printing. You hit Cancel, make the desired modifications and then open the Print dialog again : no luck, all your settings are lost and you have to start again from scratch. Even the target printer is not remembered. Extremely irritating.
=====================================================================
02-19-2016 - Assigning a recipe to a specific file
Currently, C1 does not allow to assign a particular process recipe as a default for a given image (or did I miss something ?). This is rather annoying because the user might forget to activate the correct process recipe when working on a particular image. This will impact some editing tools and especially the information displayed in the crop panel. This may lead to wrong decisions. Other C1 users in my environment have already expressed the same remark.
If assigning a default process recipe to an image was possible, this would be much more comfortable for the user. This process recipe would be automatically activated when selecting that image. If no default process recipe has been specified for a given image, then the current active (global) process recipe would apply. If multiple images are selected and all these images have the same default process recipe, that process recipe would apply. If they have different default process recipes, then the global active process recipe would apply.
Implementing this feature doesn't involve much coding, I think, and this would avoid many problems or mistakes.
=====================================================================
12-04-2016 - Grid overlay type in Preferences (odd)
I'm wondering why the grid overlay type (3x3, 4x3, golden ratio, etc.) must be set in the Preferences dialog. This just doesn't make sense and is a loss of time. Each image requires a different composition and the grid type that can be used to help during this process vary from image to image. So this setting should be "local", that is, it should be easily set while using the Crop tab. This would be much more consistent. Why force us to open the Preferences dialog each time ? Probably the person who made this design decision has never used the grid overlay on a regular basis. In Lightroom there a shortcut to quickly cycle among the grid overlay types.
=====================================================================
UI font size
Still not editable
=====================================================================
Better dual monitor support (Windows)
Still impossible to have the main window on the main monitor (the one that usually has the best quality) and the tools + the browser on the secondary monitor.
Thanks in advance to the UI development team for making the coming year better when using the C1 UI.
0
-
Especially the non-sticky print settings. Very irritating..... ditto
Chris0 -
[quote="Samoreen" wrote:
C1 would be a top notch application if the UI had been better designed. I'm very surprised by the number of people singing songs of praise about the C1 UI. The design is just plain wrong (talking here as a former developer and software development consultant).
I can't exactly sing its praises. The best I can do is learn it. For a long time I found the UI too frustrating to bother with. In time I couldn't stand using Lightroom any longer (not with Fujifilm "x-trans" files). DxO having drawn a line in the sand about never supporting Fuji's raw files, I decided I must learn Capture One. But if it hadn't been for David Grover's excellent webinars I would never have been willing to keep at it. (I hope they pay that guy well. He deserves it.)
Some features are mysterious. Capture One has a good output recipe system (albeit kind of confusing at first). So many possible recipes, each with its own settings — yet there's at least one that persists in all. For example, if you add custom text in an output naming pattern, that same text is immediately applied to every other recipe.
Baffling. Why would anyone find this not-changeable "sticky" behavior useful? Why provide recipes with unique settings and yet force the output file name's pattern to be the same in all?
I went around and around with Tech Support about it. They told me the dev team says: It's just how it goes. We're not changing it. I even threw myself on Tech Support's mercy and asked: "Can you at least understand why an end-user would not want to be stuck with this kind of program behavior for all process recipes?" The tech I was corresponding with acknowledged — a bit grudgingly, it seemed to me — that yes, he could sort of understand why a person wouldn't like that...but the dev team has said No to changing it (etc. etc. etc.).
What am I missing here? If I want the string “_test†in the output filename for only one recipe, is there some reason I should want it to appear in all of them? Should I be putting on the hair shirt and abasing myself? “Ignorant peasant! Of course it's what Saint Ansel would have wanted!†For now I'm stuck with it. So I rolled my own script providing batch-renaming at the command line that's way better than the standard crude cmd.exe "ren" command. Not ideal, but it works.0
Post is closed for comments.
Comments
32 comments