Capture One 21 (14.2.0) release notes

Comments

13 comments

  • James Grove

    Fantastic work, the M1 support is fantastic, a significant speed improvement. Great work!

    0
    Comment actions Permalink
  • Luka

    I have just updated to 14.2 under macOS 10.15.7 and what do I find? No more graphics support as in Version 14.1! And also no support for Metal under Catalina 10.15.7.

    CO-company, this is an impertinence, you have dropped the hardware acceleration with this update! Please remove this measure immediately by a new update and furthermore I ask for the support of the Metal hardware acceleration also under macOS Catalina 10.15.7.

    0
    Comment actions Permalink
  • Luka

    Open letter to CEO Rafael Orta

    Hi Rafael Orta,

    I recently read an interview you did with Jermey Gray. Some of your statements about the upcoming improved customer orientation not only caught my attention, but the statements in this regard made me happy and really hopeful that things will get better now.

    Since the interview, two updates of Capture One 21 Pro have been released and both updates have unfortunately disappointed me again, because contrary to the many wishes expressed in the "feature request" forum, only a few new lens profiles were delivered with the last two updates.

    Rafael Orta, this is the opposite of what you announced in the interview. Furthermore - and for a long time now - requests from customers are persistently igonored. I have been waiting for lens profiles for the new Canon RF lenses for almost two years, and so far only five have appeared. Unfortunately, profiles for the so important RF 24-70mm, Rf 70-200mm as well as RF 85mm are still missing.

    I therefore ask for your opinion.

    Regards
    Luka

    2
    Comment actions Permalink
  • DOC Hobel

    This is bad... macusers are waiting for metal support for years now. Now, because you had to move because of the apu-revolution at apple, you continue to ignore intel macs. I can't image it would be too hard to enable metal for intel-based macs. I' am not a developer, so maybe there are reasons for not releasing the update with metal for intel in the first place. Is there a timeline? Not everyone can switch this year!

    2
    Comment actions Permalink
  • Roderik Rotting
    • M1-macs only: Tethering does not work on Thunderbolt ports using USB3.x cables with some Canon cameras. Workaround is to use USB2 cables for the time being.

    Man was I waiting for my idle sitting M1 MacBook to finally become able to tether... But nope... What the hell have you been doing all this time? And why is abode able to handle this without a problem. Cmon guys!

    The silliest off all is to suggest a usb2 cable!! The MacBook only have usb3 ports.

    How long will it take you to solve this? 

     

    0
    Comment actions Permalink
  • James Grove

    So much moaning on here, it states in the release notes about the USB issues so why complain? As for Metal, and older Mac OS releases, Apple drops support and sometimes you can't keep legacy code as it will impact on other aspects of the software. 

    -3
    Comment actions Permalink
  • DOC Hobel

    Srsly? Older Macs? M1 MBP or MPs are not announced yet. We are talking about Macs bought weeks ago .. metal is out for ages. Ppl are changing systems once in 4-5 years. Metal support is way too late, but at least it has landed … so give it to everyone. Intel users pay the same fkg money. This is not a matter of some legacy weird stuff from decades ago.

    2
    Comment actions Permalink
  • Class A

    The keyboard shortcuts for "Increase Thumbnail Size" and "Decrease Thumbnail Size" are still broken in the Windows version. They have some very, very limited effect, but do not work as intended.

    The respective bug report was submitted over a year ago. This update saw only four (4) bug fixes for the Windows version but there are so many more issues to address. 

    While fixing something trivial like broken keyboard shortcuts would take less than an hour, it would have a very positive impact on user productivity.

    I could expand this into a long list of bug reports / feature requests that, when addressed, would go a long way to make C1 a much better software, but unfortunately, since quite a while every update and every upgrade embodied some different (mostly unrequested) ideas about how development resources should be spent. Of these, only the "style brushes" (=better access to brush presets + saving brush parameters) where really useful. The "speed edit" approach was not bad, but does not help those who were working with consoles already.

    1
    Comment actions Permalink
  • kai

    On my MBP 2019; 16"; macOS 10.15.7 the hardware acceleration finally is running well. C1 offers a work around for those having trouble and at least this works fine for me.

    0
    Comment actions Permalink
  • DOC Hobel

    Ok, but just imagine they would use metal api instead of the „ancient“ open gl on intel too. Can’t tell the difference in percentage, but at least I guess it could be 30-50% performance increase. There has to be a reason.

    0
    Comment actions Permalink
  • Jia-Hui Zhang

    where is the Canon RF 24-70mm, RF 70-200mm Lens support....

    1
    Comment actions Permalink
  • Maryna Sopilniak

    Hi Jia-Hui,

    Thank you for your comment.

    I have taken your request on board to consider those lens profiles support in the future release versions of Capture One.

    Hopefully, your feedback contributes towards a future version of Capture One.

    -1
    Comment actions Permalink
  • Dan Martin

    Let's talk about how dumb it is that:

    -- When the location of images changes, your software is not smart enough to comprehend the new location for all images in a catalog; you have to manually relocate dozens or hundreds of images by right-clicking "Locate" over and over and over and over and over. 

    -- That you even have to waste time moving the mouse to the photo in the catalog to right click every single image over and over instead of binding the context-menu key to the context menu, which is why that key exists on the keyboard!

    -- That even though I've bound "Q" to spot removal, every single time I start Capture One the Q key will never work. I have to find the spot-removal tool with the mouse and select it. In fact, when testing whether this bug still exists in the latest version, I started it and "Q" selected the CROP feature! 

    -- That frequently there is a tendency for no keys at all to work because the menu bar is somehow activated. The solution is to move the mouse to the menu bar (where a menu will drop down without even clicking) and to click to dismiss the condition.

    -- That you repeatedly ignore requests to have Photo Mechanic crops read and applied in Capture One.

    -- That CONTROL-TAB is supposed to move from module to module and half the time fails to do so while half the time working.

    -- That you fail to allow small-step distortion adjustments in the Lens Correction module, and fail to allow them to go negative when needed

    -- That you fail to have the Nikkor 200-500 in the lens profiles.

    -- That one can select an "Output Location" in watermarks and still have the output sent somewhere else based on "Process Recipe --> File"

    -- That you must waste my time when I click a Process Recipe and miss the check box, because I hit CTRL-D and you insist on putting up a dialog box saying that a process recipe hasn't been selected. Of course one is selected. It's just not checked.  

    -- That you further waste everybody's time by having no undo ability in places such as after deleting an image, which in that case forces users to disrupt their workflows by switching modules, digging through trash, finding the deleted image, restoring it, and hoping it shows up where it's supposed to. How insulting that you value our time like this.

    Yes, indeed. This is not great. You've excelled at making a speedier client than LightRoom by a blazing factor. You have these fixes to make for me to find the client remotely free of frustration.

     

    1
    Comment actions Permalink

Please sign in to leave a comment.