When cloning variants or importing including adjustments, AI Masks may be empty
Implemented
Affects Capture One Pro (16.3.4)
Fixed in Capture One pro (16.3.5)
When cloning a variant with subject/background masks, the new variant will have the correct layers but with an empty mask. The same happens when importing images with AI masks including adjustments - layer(s) are present but no mask.
We are close to finding a fix and will keep you posted.
-
HI Jack, did this appear in the latest release? I haven't experienced this with 16.3.3.6. I would be helpful if "Known Bugs" included the release number it refers to, or say if this is for all versions with this feature.
Thanks.
0 -
Yes, this bug is introduced with the newest release 16.3.4.
0 -
Ric Cohn I have updated the post. Good point and sorry for missing it initially.
1 -
Hi Jack, when will there be a solution? I cannot continue working with the sessions in which I used AI masking. That is a big problem. Also: I didn't even get an answer to my support request.0 -
Axel, while waiting you could go back to the previous version, which works perfectly for me. When updating I try to keep the last version, but there is a link to previous versions on the website.
1 -
Does 16.3.5 fix this bug?
0 -
Read the release notes.
-2 -
Walter, as a moderator do you work for Capture One? Just trying to see who the unhelpful person is. BTW I did look it up. The link to Bugs is broken. Did you look to see or is this just a RTFM message?
0 -
Scroll down the page?
-1 -
This is not the first set of release notes where one of the links doesn't work.
Fortunately, as Walter Rowe points out, you can just scroll down manually.
And although we are moderators, neither Walter or I work for Capture One.
Ian
0 -
Walter, are you a troll?
For those who are suffering from this, I do not see a fix listed so I assume it is not fixed. Jack W has been helpful and said he would post when it was fixed.
0 -
- Kindly behave courteously in the forum.
- Here is what the 16.3.5 release notes say under bug fixes for Windows. (If you scroll down, as I suggested above.)
Is this the issue you are concerned about?
Ian
0 -
Hi Walter,
I have read of course the release notes!
But the bug is STILL marked as "in work" here.
Please explain...0 -
Peter Meyer - the crucial thing is whether the bug still happens, or is it OK now?
Ian
0 -
Hi Ian,
this is the "official page" of Capture One.
In the known bug list the bug is STILL marked as in work.
Before installing a new version I wanted to know if the bug is solved.
It was just a simple question!
The answer can be just ONE word!0 -
Peter Meyer - I don't know, so I am unable to give a yes or no answer. It isn't a bug that I have been affected by so I am unable to say from personal experience. As I pointed out above, the release notes show it as a bug for Windows that has been fixed. (Whether that means it is still a bug on Mac, I have no idea. Did it affect Macs too?) I would suggest that there is no particular downside to going for the update and trying for yourself.
Ian
0 -
Peter Meyer
I can confirm that this bug is solved with the v16.3.5 update, at least under Windows which is my OS.
And it makes no sense to insist that this post is still labelled as "in the works". it was probably simply forgotten to change the status. It would have been easier to ask those who have already installed the update about their experiences. Walter and Ian and the other moderators are users like you and me and cannot change the thread status.0 -
Why is it not possible for CO to change the status?
I want to trust the statements of the vendor of the software I bought...
0 -
Same issue
I want to trust the statements of the vendor of the software I bought...
0 -
hey everyone, updated the post
i'd say that the main source of information should be the release notes, because it can take some time to update community posts
0 -
@Ric
Thank you, Ric!
Axel
0
Please sign in to leave a comment.
Comments
22 comments