"Could not apply Layer" Error
Hello, I try try to copy adjustments from one photo to the next with layers but it does not allow me to copy anything if I have layers in the photo I am copying from. The event catalog pops up with the message: Could not apply layer.
-
Christos,
If you you have "Edit all selected variants" (or whatever it is now called) selected AND the source image of the copied data is included in the selection then the message is telling you that the layers will not be applied to that image - i.e. they will not be duplicated on that image.
You should find that they WILL be applied to all of the other variants selected.
That is the usual situation unless you have uncovered another warning or process that I have not previously found.
0 -
SFA,
I just copied from one photo and then select another photo with no edits on it to copy to. If I had made some healing on the primary photo then it did not allow me to copy to the new photo! If I just copy with no healing layer then its ok! If on the image I had various adjustments, a healing layer and a normal other layer it did allow me to copy to a new image! Then my pc crashed actually while using Cone and after it rebooted I now don't have this issue! The problem is that I had this same issue some time ago so go figure.
0 -
I’m quite sure your problem is related to your healing layer. There are a couple of issues related to healing already. It seems like the test of healing feature requires an update - and the code too.
0 -
I'm not at all convinced that there is a lot of value (except, perhaps, in some very specific use cases) for copying healing or clone tool activities between images.
Bear in mind that the tools, after the last revisions to the functionality, are not really layers in the way that they work when compared to the other layers - which is why they are handled separately after the last major revision of functionality.
0 -
Christos,
Based on your last post perhaps the problem you had might be related to some sort of issue with a temporary work file conflict where some left-over data from a previous activity that was not fully "cleaned" from storage (temporary or memory) was called up for the next process. At that point the data provided may be outside the parameters for the current image and the process fails.
After the crash the system cleans up (or has not retained the "wrong" data in memory) and the problem disappears - perhaps only until the next time something disrupts a similar process.
That's not to say there is not a possible weak point in the processing logic that, could be addressed once the problem has been clearly identified. But "Could not apply layer" is, to me, the default logic for most usage of healing and cloning. (See my previous comment).
Really the only way to analyze the problem when it occurs is to create a Support Case and provide the log files, etc., to the C1 Support team so that someone can take a look at the specific steps of the process that failed in order to identify why the process would not work (in the event of only the healing layer being copied).
Once the source of the problem is identified the developers could look at the options available for dealing with it. Maybe a better message explaining why settings for the healing cannot be applied or some sort of revision to how the process should work in the event that, for example, the paste is to a file of a different size form a different camera or some other setting that the healing process uses is being asked to use source data for the replacement sample that is so inappropriate that a different approach is required. Just two possibilities that come to mind.
However, if after the crash you cannot reproduce the problem with the same files and the same edits it probably suggests that some sort of data problem was the cause.
To be able to attempt to eliminate such a problem in the future the C1 developers would need to understand how it happened in the first place and the log files are probably the best options as a starting point for that journey of discovery.
0
Post is closed for comments.
Comments
5 comments