Creating Masks BUG
This issue began with Version 14.4 and continues with the latest update (14.4.1). Previously C1 would automatically create an adjustment layer upon selecting one of the tools below the Layers Tool window (linear gradient, radial, et al). Subsequent/separate parametric layers could be added similarly. The background layer needed to be selected for this to work, otherwise any currently selected parametric mask would be overwritten by the new tool. This was normal behavior, no problem, except for the user forgetting this would happen on occasion. Now, however, I'm noticing that from time to time new adjustment layers are not being created by C1 and existing parametric masks are being overwritten, even when the background layer is selected. Also, on occasion, my own custom Style Brushes no longer create their own layers when the tool is put to use.
Example:
New image with only a background layer. I select the radial gradient tool and a new adjustment layer is created automatically, when I begin using the tool (Adjustment Layer 1). I then switch back to the background layer and choose, say, to create a linear gradient by clicking the tool below in the Layers window. This time, however, no new layer is created when I begin using the tool (no Adjustment Layer 2) but rather C1 switches automatically to the existing adjustment layer and overwrites it, since it's a parametric mask (only one tool allowed at a time). Otherwise, if it were a normal raster layer, the parametric mask is simply added, capturing and using any exisiting adjustments which, indeed, is what first alerted me to the problem.
I'm surprised there are no posts mentioning this already. Am I the only one to observe it so far? I am an experienced C1 user of some years and noticed this unusual behavior almost immediately. It is somewhat erratic and inconsistent but is happening more often than not.
Anyone else?
-
I know that on Paul Reiffer's (excellent) YouTube videos, he says it works like you describe - if you have no adjustment layer at all yet, then selecting any mask-making tool such as brush, gradient or radial mask, will create a new layer. But once you have any adjustment layer, he warns us to be sure to create a new layer before using the mask-making tool. I think that this has been the default behaviour (so a feature not a bug) ever since they changed the way that Heal and Clone layers work (so as to allow more than one heal or clone source on the same layer). Can't remember which version that came with, but earlier than 14.4, I think.
(Sorry if I have misunderstood what you say the issue is!)
Ian
0 -
Ian, I think this has been the weird behaviour since they introduced this weird brush types and "brush creates a layer" "feature". Since then, I have to double check each time I switch brush type or layer in order to be sure not to make a mistake, something which was not needed in the old, simple but straight-forward implementation with only on universal brush and no auto-create or auto-jump to layers, simply create or select a layer then the brush, never ever did the layer change automatically.
Even super pros like Paul R. speak out warnings, this says much... (although he also advertised the drop of the processing tools and the new export window, this probably also says much...)
Randall, I tried 14 and later also beta-tested v14.4 but I am still on 13, so I cannot give it a quick try.
0 -
Guys, I'm a great Paul Reiffer fan, David Grover too, and religiously watch all their videos, some more than few times. Their videos are one of the best reasons to use Capture One, in my opinion, because no other vendors or bloggers come close to offering online tutorials of this caliber. (I've only discovered one other, Kasia Zmokla, from Poland, particularly excellent when it came to color grading, but she stopped making videos some months ago unfortunately.)
I'm perfectly aware of all the gottyas when it comes to masking, plus a few other far more subtle ones that David and Paul have pointed out when it comes to using Capture One.
What I'm seeing now, or attempting to describe, departs from the norm I've grown accustomed to over the years. I'm not inadvertently overwriting masks because of user headspace; Capture One is doing it all by itself for no apparent reason. I would know, if the fault were mine. Would that that were the case!
As I mentioned earlier, the behavior is erratic and unpredictable (which to me suggests a bug), but then I no longer waste time testing things to exhaustion myself because I've grown accustomed to Capture One's buggy behavior. They never seem to smooth out all the glitches and I've stopped bothering with support requests. Nor is it my computer. Now they're hot on Capture One 22, with some really big additions, along with the promise of even more inevitably quirky behavior. I wasn't doing much editing with version 14.3 but am doing a lot now with the latest one. This started with 14.4.0 and continues with 14.4.1. The introduction of the Magic Brush may be related perhaps but, frankly, I'm weary of testing-debugging things for the developers of this otherwise superb software. As I wouldn't use any other software, I'm a captured audience (pun intended) and Capture One knows that. So, I guess I/we will just have to wait until more people notice the same quirk or inconsistency, until it finally gets resolved (most likely by accident).
0 -
Yeah, don't get me wrong, I like Paul's and David's videos too. I am not a fan of some recent user interface design decisions of C1 though, I praise C1 where it deserves it and I critizise C1 by a fair amount where it (imo) deserves it too, knowing that there is no black and white in most cases. But it doesn't end here for me, only critizising is easy, so I am trying to support them e.g. requesting features, reporting bugs and participating in beta testing when it fits my personal schedule and motivation.That's because I like many aspects of C1.
For what they don't do (noticable performance increases, adaption to reasonably spec'ed hardware, better quality releases, improvements in the user interface) their price level has risen too much for me to just update every time a new major release comes out, contrary to the past I think at least twice before I upgrade now.
To the actual problem you described, I wish C1 would go back to a regular release schedule, new major version once a year with new features and minor versions for user support, bug fixing and new camera/lens support.
But both of my posts here in this thread don't really help anybody, I noticed this by myself, I usually don't like ranting posts of others but I am not free of faults by myself; my apologies.
0 -
We're on the same sheet, BeO, and I agree that it's counterproductive to rant and criticize. C1 will often simply ignore you thenceforth (I know). So I don't log in here very often (even the forum itself is somewhat buggy) but this time it really was frustrating. My problem is real; it occurred again today. Sooner or later others will detect the odd behavior and some might even have the patience to diagnose it sufficiently so that C1 developers can replicate it consistently. I no longer have the patient and already know how to work around it. It seems to be work-flow dependent and seems to be related to the Magic Brush somehow. Oh, well, so much for the Magic Brush!
I agree also on the pricing issue, as have a ton of other users, but I doubt that will change either. Besides, we're a captive clientele, as I suggested earlier. So C1 needs to know that we don't come here to help make them feel warm and fuzzy about their product; we're here to help make it better.
All I've ever asked them for is auto-hide Tools and Browser panels for Windows, like Mac users enjoy. Now how hard would something like that be to implement? Not very, I suspect. Oh, well. I will be thinking hard about the next upgrade too.
0 -
The new brush/layer implementation is more complex for the user but also more complex for the developers, so it literally "begs" for bugs.
When I (and others) have tried to get back the universal brush without auto selection of layers, in other words the straight-forward old style (and C1 can keep the new brushes, it is unrealistic to ask to remove this stuff again), we have not fully been understood or heard by C1.
The upcoming new features in v22 are interesting to me, if done right, so I'll give it a try.
0
Post is closed for comments.
Comments
6 comments