Strange behavior when masking in layers.
I have an issue that the ON1 staff seems to be unable to help with and I am putting this here as maybe you had the issue and found a resolution.
When I mask a layer in Layers the mask is showing the brush lines when I invert the image. Lets say you have a grey sky and want to replace it with a blue sky with clouds, so you select a luminosity mask, adjust it for the best you can get. Next there are things popping up in areas that require brushing so you use the brush to paint out or paint in the areas that are affected - looks nice black and white, invert and the brush marks are there and the mask is screwed up.
Staff has requested a couple of videos and have not been able to duplicate it at ON1. They sent me a new release and instructed me to get rid of anything RAW 2019 including any downloads and the problem is still there.
This is happening on a Windows 10 64 bit machine with 16 Gb ram and a 2 Gb Nvidia GT-730 video card BUT the computer is 8 YO and has an I5-760 processor. The only thing I would suspect is slowness due to age not functionality.
Any thoughts?
Thanks for looking!
-
Eigil, you're the one with the examples of the problem. Not sure if Brian sees this. I don't on my system.
Go ahead and submit a request.
https://on1help.zendesk.com/hc/en-us/requests/new
Make sure you attach examples and describe clearly what's happening. Also, include the info requested here...
0 -
Rick, rasterizing is converting the brush strokes that have to continually be rendered into an actual pixel based grayscale image. The luminosity mask is rasterized.
I am seeing this it's just not as visible because of how I do my masking and because like Rick I don't use the Density slider very much. I let you pass this one along to them Eigil. :)
0 -
Rick,
... I don't know what the rasterizing is all about, but that's not how On1 works.
Neither do I know - and have no clue about how these systems work deep under the hood.
"Rasterize" is the term used by Adobe and Capture One when a unit with dynamic properties is made static - i.e. "relieved" from a number of computational dependencies, a Smart object becomes a brush-able layer in Photoshop, and a luminosity mask becomes editable with a brush in Capture One. I think of the old "raster" newspaper image technology - an image build on a matrix of dots (or pixels now) or whatever units are suitable for the purpose. It could be simple coordinates within the x and y axis opposed to vector rendering. I don't know. But that's how I got the "rasterize" expression.
Two separate layers with different computational dependencies would explain why they don't work so well together in PR.
I would prefer the option to "melt" such layers together, when it serves my editing.
0 -
Well, Rick - Brian explained it.
Are you really not seeing this problem on a Mac (?) - Is it exclusively a Windows problem?
Anyway, I will submit a request, and refer to my haunted Win 10 platform ;O\
0 -
The term raster comes from the way images are drawn on a CRT. The electron beam that illuminates the pixels is scanned back and forth and it is called the raster. Rasterization is how a vector graphics image is converted into a pixel based image. Wikipedia has some interesting info if you really care. :)
Yes I am seeing this Eigil. I just didn't see it as quickly because of how I do my masking and because I rarely use the Density slider. Let us know what support has to say.
0 -
I'm on Windows and I'm NOT seeing it.
0 -
Rick,
Have you repeated this sequence?:
1. Create a luminosity mask from Lumen and refine it with the Levels sliders to the strongest black and white contrast.
2. Refine it with the Mask Brush, remove white from blocked areas and black from transition areas.
3. Reduce the mask Density on the slider.
The last point will reveal black brush strokes in former black parts of the luminosity mask now greying faster out than the brush strokes. That's what I get here, and apparently Brian can see it too, though I'm in doubt whether he has the problem on a Mac or a Win computer.
0 -
I'm primarily a Mac guy but I do run it in a Windows 10 VM for testing. Performance testing doesn't count there. 😉
0 -
Well, ok. If I take it to extremes, I can finally see a difference. This is at 100% density...
and this is at 50%...
But again, I never use Density, so it's never been a problem for me. If you haven't reported this yet, go ahead and do it.
For comparison, this is what it looks like without the levels adjustment and this is a correct mask. With this mask, the density slider works properly. It's showing that only the paint out strokes aren't being handled properly when levels are applied.
0 -
There you go, Rick, nice example.
I reported the problem yesterday and will update here, if anything of interest comes back.
0 -
Rick,
What is this bird doing? It looks like a diving configuration, but how is the branch? implicated ...?
0 -
This is just one of the photos in my test folder where I can try different things without messing up my actual library.
0 -
Rick,
I get the perspective now. It's a close angle.
Brian,
You are primarily a Mac person, you say, running a virtual Windows platform on your Mac.
But could you replicate this "bug" on your Mac as a genuine Mac?
0
Please sign in to leave a comment.
Comments
43 comments