Mac - Copying a Filled Layer from portrait to landscape image results in a non-scaled mask being applied
Implemented
Update 20th February:
This bug was fixed in 16.3.6.
See the release notes here.
Update 25th November:
There are specific cases in which this behavior still occurs when copying the filled mask from different camera models.
Our team is back on the case, and working on a new fix. Apologies for any inconvenience. Follow this post for the latest updates.
_________________
Update 19th September:
So we've received reports from several users regarding an ongoing issue with copying masks that is still present in the latest version, Capture One 16.2.4. We want to assure you that we are actively working on a solution to address this matter soon.
Keep an eye out for the upcoming updates!
------------------------------------
Result:
Screenshot provided by Gauthier Mignot.
#193473
#197909
-
Hello everyone.
The new update STILL HAS the same issue. This would be funny if it weren't a serious issue and a mockery.2 -
Did anyone who uses the new Version (16.3) report the issue? I didn't upgrade yet and therefore cannot report it. I sent a bug report yesterday for 16.2.5.9 but the support team didn't answer yet.
0 -
Hi Michael,
I wrote this morning that the new version 16.3 still has the same issue1 -
In my case, using v16.2.5 the problem was mostly gone. Most of the time C1 would copy the mask correctly, but every now and then it would fail (same error as in original version with mask ending in a solid edge). I was able to "live with that".
However, I made the mistake of upgrading my license to v16.3. The problem is now back in all its glory! Masks have become a pain again, they just stay in whatever orientation and size the image had when copying them. When you edit a long reportage, this mistake seriously renders C1 close to useless as it WILL slip into your delivered product. I use C1 commercially and had to already apologize to clients since on a few occasions that mistake went unnoticed. This is very bad news...
I really don't really care about all the AI shenanigans if this means that basic functionality got broken. Please fix this soon!0 -
Ok, at this point the problem is serious. At this point it is clear that Capture One cannot be used for work. I have a perpetual license and I have no intention of buying the current version. However, I expect that the previous version, for which I bought the perpetual license, will be fixed, and it still doesn't work.
The really annoying thing, and I find no justification for it, is that you release a new version when the old one has not yet been fixed in the most basic of functions. I find this behavior really difficult to tolerate.
What to do in the future? I have set up my entire workflow on Capture, especially for the functions connected to tethering. Changing makes me feel sick. But today you cannot use Capture versions after 16.2.2, which was released in June 2023.
I can only wish for three things: 1) that Capture One changes management 2) that a new company enters the market that makes the new Capture One, wishing that, once it has conquered the professional market, it does not start thinking about profit at the expense of the quality of its products. 3) that Lightroom introduces sessions and does decent tethering. At that point, since we pay for Lightroom without using it, goodbye Capture.
0 -
Helen. Hi, Helen. Are you still asking for additional examples of this?
Also, any chance we can get the tag changed from "Implemented" back to "In the works" as the issue persists into 16.3.0.76?
0 -
Hi all,
Has anyone tried 16.2.6 to see if it has solved this issue? I appreciate that I'm as able as anyone else, but I just can't bear the idea of having to upgrade/downgrade again!
What joy it is to have so little faith in one's professional tools! 🫠
1 -
I just downloaded v16.3.1.23 and the bug now seems to be fixed. Masks get correctly applied to images with a different orientation than the source image. Im on a 2019 Intel Mac Pro with Vega II GPU running Ventura 13.4.
The previous release of v16.3 still had the bug, so I'm relieved. Cannot comment on v16.2.X unfortunately.
1 -
Actually, scrap that! A few days into the latest release v16.3.1.23 makes it clear: C1 still has the problem. For some reason, just not all the time. Really frustrating.
0 -
Just wanted to chime in for some input. My issue actually went away on its own. Don't know why but the layer masks started working at some point after my last update to 16.2.5.9. Initially after the update the issue was gone, then it was back, and now for some months already it has been gone again. The version is very much usable now but I did develop some trust issues for C1. For one, the lack of responses from the developing team regarding this issue is just depressing. It would be very nice to get even a brief update on how they are at least trying to fix this.
0 -
I recently upgraded to the latest version (v16.3.1.23) after a three-month wait. While copying settings from the same camera model works flawlessly, issues arise when transferring settings between different models. For instance:
- Copying from Nikon D600 to Nikon Z7II results in a bug.
- Copying from Nikon D850 to Nikon D600 leads to a bug.
- Copying from Nikon D850 to Nikon Z7II also triggers a bug.
Surprisingly, copying settings from Nikon Z7II to D600 or D850 works fine.
It's frustrating to encounter these issues again after I upgraded all my Apple Scripts to the new version.
I hope a solution or fix is available in 2027.
How this bug is "Implemented"?
0 -
Same issue occurs on Windows while applying maks with a luma range. (16.3.3). Adjustments copied from one picture to another with different aspect ratio are not applied to the whole picture. It's a huge pain if you want to for example desaturate shadows across multiple pictures.
Are we really paying so much for a such poor support from you?0 -
Piotr, this is why this time, for the first time in years that I've been using Capture one for work, I haven't upgraded and I don't intend to.
1 -
Helen Brian Jordan may we get an update about this issue?
1 -
No information has been provided regarding this issue, leaving me uncertain about any potential resolution in the near future. The bug has persisted in the application since August 2023, marking a span of six months. Despite upgrading to the latest version, I am inclined to cancel my subscription, as this level of performance is unacceptable for a professional software product. The recent release, issued just a few hours ago, fails to address or acknowledge the ongoing problem in the release notes, which adds to my disappointment.
1 -
Dear CaptureOne team,
I'm posting to confirm that I am still dealing with this bug and am running the latest version 16.3.4.5, on macOS Venture 13.6.4.
The same exact issue of copying and pasting from one photo to another on photos taken two days ago with just 1 single camera. Am not copying between different models.
Is the development team still working to solve this?
Thanks1 -
You need to open a support case. This is a community forum. There is no "capture one team" here.
1 -
Mick Bowie, they're currently focused on developing new features and don't have the time to address this issue. I've decided to return to using Lightroom since it's conveniently included in my Adobe subscription.
0 -
Capture One Pro (16.3.6)
Date of release: February 20 2024
macOS
- Fixed a rare bug where copy and apply a Filled Layer from one photo orientation to another can break.
It seems that the issue is fixed but I will not upgrade today because something else might be broken :-(
1 -
OK, so what about on 16.2?
As there have been no updates since 16.2.6 (3 months ago), the implication is that it is now officially unsupported.
Seems a bit rude to not fix an issue that's a major pain for people, especially when you've expected them to stump up for a brand-new version (which still had the issue 🙄).
What I'm hearing is... 'we can't fix this issue, but buy the new version anyway' ...then once we do find the fix, we'll only apply it to the latest release, so now you have to buy an update if you want a working product.
Glad I use Blackmagic Resolve / Affinity / MacOS products for the rest of my workflow or I'd go completely mad!!
1 -
NB. Helen, I apologise for directing my ire at you, as I appreciate you're here to help on this forum/thread, but I'd be grateful if you could pass on my thoughts to the relevent people, as this issue seems indicative of the attitude of C1 is taking at the minute (re. failure to be proactive in bug fixing and lack of support for legacy users).
1 -
Brian Jordan Helen
I am still able to reproduce this issue with 16.3.6...1 -
Just fyi, I don't work for Capture One. Can't help you at all.
0 -
Pete Axford may I ask you to drop us a line at support.captureone.com, please? Just mention my name in the request, so I can jump into the conversation and see what we can do in your case.
0 -
Helen I have already ticket open: 220021
0 -
FirstName LastName thank you for getting back to me, Piotr. I responded to your message by email. Luma mask issue will be treated separately from this bug report.
0 -
FirstName LastName Have you opened a support ticket on how to reproduce this issue with version 16.3.6? I haven't upgraded yet myself because I'm concerned about encountering additional new bugs. I've already learned how to live with these known bugs.
0 -
Hi Helen,
I opened a ticket at the weekend (#224646) but haven't had a response. Could you chase it up please?
Many thanks,
Pete0 -
Pete Axford I'm on it ;)
0 -
It's been almost a year, and the bug is still present. Do you not have a testing department, or are your testers on vacation? I don't understand how this is possible.
0
Please sign in to leave a comment.
Comments
89 comments