Why Don't Phase One Listen?
I'm a great fan of Capture One - it's definitely the best RAW convertor I have ever used. However, it does have a number of ergonomic/UI/UX challenges which persist across versions, and which could be easily resolved to the significant benefit of users, if only Phase One were minded to listen to their customer base. The resolution to most would be transparent to those who are not inconvenienced, but a significant aid to those who are affected. The product would just get better. Is there any way to get traction on these?
Here are my primary candidates.
Hotkeys for presets/styles
The concept of presets and styles is sound, and well executed. The problem is that it it's fiddly to find and apply them. For example, to apply my standard infrared black and white settings, I have to click on the "Select Styles" icon, then on "User Presets", then on "Black and White", and finally on the preferred preset, which is the same one almost every time. Four clicks, which can also be tricky if I'm working in an environment where navigating a deep menu is a bit hit and miss, such as on a train.
The solution is incredibly simple, and very well established in lots of other software I use, from word processors to software development IDEs. Add the ability to assign a keyboard shortcut to selected presets or styles. Why can't we do this?
Named Variants
Like the previous one, this has been a repeated request in the forum for as long as I've been using C1 (since about 2012), maybe longer. It would be great to be able to set a meaningful name on any image variant, and include this in the output filename via an appropriate token. Wouldn't it be better to automatically generate, for example, "G9_X12345.jpg" and "G9_X12345_BlackWhite.jpg", rather than having to rename one file manually before creating the second?
Yes, I know that there is at least now a token for "Variant Position", but a meaningless number doesn't help that much, and I can't believe that it's beyond the wit of the C1 developers to provide for a simple name string.
Scrolling File Menu
This is just bloody annoying. Run C1 on a laptop with a vertical resolution below about 1000 pixels, and the file menu doesn't display completely - it's just too long. Yes, there are little "scroll arrows" so you can move it up and down, but that means extra clicks to get to where you need which absolutely should not be needed. Having such a vast list in a single menu is pretty poor UI design anyway, so the simple solution is to move some of the items into a sub-menu. Are, for example, the EIP import/export functions in such constant use that they must be at the top level, resulting in general inconvenience for all users?
There's a degree of contradiction here as well. Phase One seem to be quite happy to condemn users to a deep menu tree to get at styles and presets, but don't seem to be able to accept that as a simple solution to sort out the unusable file menu.
If there's anyone from Phase One reading this, I'd appreciate a response on why these issues can't be fixed. If any of the other users have an idea on how to get them progressed, I'd be grateful.
Andrew
Here are my primary candidates.
Hotkeys for presets/styles
The concept of presets and styles is sound, and well executed. The problem is that it it's fiddly to find and apply them. For example, to apply my standard infrared black and white settings, I have to click on the "Select Styles" icon, then on "User Presets", then on "Black and White", and finally on the preferred preset, which is the same one almost every time. Four clicks, which can also be tricky if I'm working in an environment where navigating a deep menu is a bit hit and miss, such as on a train.
The solution is incredibly simple, and very well established in lots of other software I use, from word processors to software development IDEs. Add the ability to assign a keyboard shortcut to selected presets or styles. Why can't we do this?
Named Variants
Like the previous one, this has been a repeated request in the forum for as long as I've been using C1 (since about 2012), maybe longer. It would be great to be able to set a meaningful name on any image variant, and include this in the output filename via an appropriate token. Wouldn't it be better to automatically generate, for example, "G9_X12345.jpg" and "G9_X12345_BlackWhite.jpg", rather than having to rename one file manually before creating the second?
Yes, I know that there is at least now a token for "Variant Position", but a meaningless number doesn't help that much, and I can't believe that it's beyond the wit of the C1 developers to provide for a simple name string.
Scrolling File Menu
This is just bloody annoying. Run C1 on a laptop with a vertical resolution below about 1000 pixels, and the file menu doesn't display completely - it's just too long. Yes, there are little "scroll arrows" so you can move it up and down, but that means extra clicks to get to where you need which absolutely should not be needed. Having such a vast list in a single menu is pretty poor UI design anyway, so the simple solution is to move some of the items into a sub-menu. Are, for example, the EIP import/export functions in such constant use that they must be at the top level, resulting in general inconvenience for all users?
There's a degree of contradiction here as well. Phase One seem to be quite happy to condemn users to a deep menu tree to get at styles and presets, but don't seem to be able to accept that as a simple solution to sort out the unusable file menu.
If there's anyone from Phase One reading this, I'd appreciate a response on why these issues can't be fixed. If any of the other users have an idea on how to get them progressed, I'd be grateful.
Andrew
0
-
You should send this to the support team via the link in my signature. 0 -
I have done that, requesting that Phase One respond formally on each suggestion with whether they can and will act on it, or if not providing a reason why not. It will be interesting to see what the response is. 0 -
I wouldn't expect a response as to why certain features won't be implemented or when they may be implemented. We're definitely open to any/all suggestions, but we can't give a promise or timeline. That being said, requested features are weighted and prioritized by the number of users requesting the feature, as well as other factors; if anyone else supports these requests or has others, I highly recommend submitting a ticket to us via the link in my signature so we have an accurate measure of that demand. 0 -
Hi @Ben_US
Thanks. I have received an update to my email with acceptable interpretations of my suggestions to go on your feature list (although there does seem to be some resistance to supporting a simple name per variant, which I still think would be a good idea).
It would be good if any other readers of this topic could submit a ticket as you suggest, but could I also suggest that you take a minute to search through the forum, as most of my suggestions have been long-running requests since abut 2012, and doing such a search would confirm the numbers of users who would like to see them. A search on my posts will highlight a number of long discussions related to these features, and in some cases the previous tickets raised by myself and others.
Thanks
Andrew0
Post ist für Kommentare geschlossen.
Kommentare
4 Kommentare