Skip to main content

Feature Request: Realtime Masks

Comments

7 comments

  • Tx

    It is frustrating, at first I thought the problem with the layers was solved, but it still exists.

    The masks of luminance layers are copied incompletely to other images when they are copied.

    The layers are always present but the luminance settings are not applied or only on two of three luminance layers.

    ___

    Sometimes it works sometimes not, maybe it has to do with the problem that masks are only displayed if you click on images before, there is a connection with floating tools.

    ____

    Great, the mask was copied but is not a luminance mask although the layer is one.

    I now have the imprint of the mask on my image from which I copied the luminance mask. :thumbup:

    So it is not a luminance mask

    0
  • BeO

    I now have the imprint of the mask on my image from which I copied the luminance mask. :thumbup:

    I think it is supposed to work like this:

    You first define a bitmap mask, e.g. by brushing or use a gradient tool, or select Fill mask for a 100% mask from the three dots tool menu. Then you define a Luma Range, which restricts the bitmap mask further.

    EDIT: gradient tool does not create a bitmap mask, but you got the idea.

    Then you copy the layer and apply it to another image. This should contain the same bitmap mask and the same Luma Range settings.

    That means if the original bitmap mask was not filled 100% then the layer on the target image bitmap mask would be incomplete and has an "imprint" from the original.

    So, has your orignial bitmap mask be filled 100%, before the copy command, or was it already incomplete in the first place?

     

    To your specific use case, have you tried to define a curve on the background layer to protect your highlights and copy this curve or use a preset/style?

     

    0
  • Tx

    If it works sometimes and sometimes not, it's certainly not my fault.

    When I select the mask of the imprint and press luma mask it calculates it correctly.

    So, its copied but not recalculated.

    0
  • BeO

    I am not talking about anybodys fault, just want to understand.

    So you say the

    1. the problem (bug) is the missing automatic recalculation after copy&apply a layer with Luma Range to a target image?
    2. and the "real time masks" feature request is to recalculate any layer with a Luma Range whenever the exposure of a pixel (or luminance value) is changed by a background layer adjustment (or an adjustment of any other layer beneath the respective Luma Range layer)?

    Did you file a bug report for no.1 in the past already?

    Did you try my tip as a workaround, maybe it suits your current needs? (it might save you 4500 steps...)

    0
  • Tx
    • So you say the
    • the problem (bug) is the missing automatic recalculation after copy&apply a layer with Luma Range to a target image?

    Yes, but not at the first two luma layers, those where ok, the layer with lower opacity was affected.

    • and the "real time masks" feature request is to recalculate any layer with a Luma Range whenever the exposure of a pixel (or luminance value) is changed by a background layer adjustment (or an adjustment of any other layer beneath the respective Luma Range layer)?

    Yes, if its a recalc at the stop of a processing or real realtime, must of course be evaluated by the programmer, depending on how this is done we have a very high load on the CPU or GPU. 

    • Did you file a bug report for no.1 in the past already?

    Yes, in the beta, actually the error was fixed but has now reappeared, possibly it has to do with the opacity. 

    C1-21 still has the bug completely.

    • Did you try my tip as a workaround, maybe it suits your current needs? (it might save you 4500 steps...)

    The way my style builds up, it's only possible afterwards.
    I can adjust it over even more layers but that is time-consuming.
    But would have less errors, because the Luma layers are quite buggy.

    The way my style is now I have a throughput of 283 images in 3 hours when editing wedding images.

    It is set so that you only have to adjust exposure, white balance and the highlight side of the tones, the retrieval of the absolute highlights is actually just an icing on the cake but should still work properly.

    If there is interest I can demonstrate this.

     

    0
  • BeO

    If you find the time, sure, I'm always interested in how others work.

     

    I wonder if the bug (not recalculating after apply) also occurs sometimes if you use the gradient tool to define a filled mask as the basis for the Luma Range. (Sharp falloff gradient, moved outside the image border so that only the 100% area remains within)

    By looking at the .comask file size I think the bitmap mask is stored also in this case, but maybe for the invocation of the recalc, when applying the layer to other images, it might make a difference.

    0
  • Tx

    Update:

    Simulation of a Realtime Mask with the tools C1 already offer to us.

    I use Capture One's layers to simulate automatic masks by mixing the HDR and Dehaze tools with the Exposure tool.

    The result is a dynamic behavior while changing the exposure to the background layer.

    https://youtu.be/R3i86dBwiQE 

    0

Please sign in to leave a comment.