Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Unbelievable, after almost a year the bug - unable to load adjustment mask is still unsolved !!!

---
  • Edited

thought I read they fixed this with the latest release but this annoying bug is still there which leads to the question if they just don't care or have really bad software ingeniers unable to fix this. 

 

0

Comments

10 comments

Date Votes
  • Thomas Kyhn Rovsing Hjørnet
    Top Commenter

    I haven't had this issue after updating to the latest version. If adjustment masks created in previous versions were lost then, you may still get the error message in the latest version; I've seen this a few times.

    0
  • ---

    it appears random, just now I work with the same project without any issues. unfortunatly the masks have been created after the update. the problem appears only when a mask was altered or copied and when the files are stored on an external drive. this is frustrating because  they monitor us like lab rats but can't fix it.   so lets hope this was the last time..... it is also sad to see that the layer copy problem is also still not addressed. 

    0
  • Rob
    • Edited

    According to the release notes this bug has been fixed. But it wouldn't surprise me in the least to hear that it's still there.

    https://support.captureone.com/hc/en-us/articles/360014022217-Capture-One-20-13-1-3-release-notes 

    Bug Fixes Mac

    • Fixed an issue where masks could be saved incorrectly and fail to load at a later stage.

    • Fixed an issue where using Color Balance on a Layer could result in artifacts on the exported image.

    • Fixed an issue where touching the touch bar on Macbooks could crash Capture One.

    • Fixed an issue where Fujifilm X-T4 thumbnails were corrupted when shot with a Film Simulation.

    • Fixed various crashes and other issues.

    0
  • Thomas Kyhn Rovsing Hjørnet
    Top Commenter

    According to the release notes it was also fixed in the previous update.

    0
  • Rob

    Figures.

     

    0
  • ---

    lets hope this is now really solved and what I saw was only an exception caused by something else but this does not change  that it took them a year to fix it what is totally unacceptable in my view.  

    0
  • Rob
    • Edited

    There are so many unacceptable, many years unfixed bugs in this bizarre piece of software. I’m pretty sure Capture One is just one teenager in his parents’ basement writing, testing, coding and troubleshooting in his spare time. Ha!

    0
  • ---

    ....haha looks like.  

    but the very sad reality is that we as user are total transparent to them so what we experience is that they see no need based on the data they aggressively  collect to do better.  user which store their raw files on an external drives and also make use of layers are probably a very small groupe and and so no reason to hurry.  they had a chance to show us they are better than adobe but failed totally in very aspect.  when you compare the price increase to the improvements they delivered in the last years you can see a clear path.

    0
  • ---
    • Edited

    thanks god I´m not the only one running into this issue as one could get the wrong impression I'm just a troublemaker....

    but this people here really care more about pr and marketing than fixing this dam software.  I very much prefer the layer handling in CO over adobe but as a professional this benefit has no worth when I have  to spent hours of redoing things or have to deal with this insane layer copy behaviour they ignore. I'm  already doing more work in arc to be prepared when the next bugy version lands and it is time to say good bye.

    1
  • ---
    • Edited

    seems this is now the new welcome screen.....  

    0

Post is closed for comments.