Using Auto Mask with brush

I have watched tutorials on this and consider myself an advanced PC user but I am stuck here. When I read how other people use this tool, it shows them starting at a point on their photo then using the brush and the mask doesnt allow the brush to cover over different color areas than the one first selected. But..when I attempt this, all the photo sections are covered in the mask not just my starting point color...what am i doing wrong..how you can follow this.
thanks

From Lightroom news........
The auto-mask controls
The Auto Mask option cleverly masks the image as you paint with the Adjustment brush. It works by analyzing the color and tone of the area where you click with the Adjustment brush and only applies the effect to those areas that match the same tone and color.
In response to the middle point comment, that would kind of defeat the purpose of the tool. The tool is only suppose to mask the starting color not surrounding areas. Thats why its suppose to be so great.
check this out. http://lightroom-news.com/2008/07/31/auto-masking-in-lightroom-2/
unless im reading this wrong, its suppose to work like i said above.

Similar Messages

Masking with brush problem

Why in mask with brush set to white it makes parts erased with black reappear, but especially black isnt black anymore, with closer look I can see "tiles" of background....when I use Lasso tool on the same area and "delete" it while having set black color, the black on the image is "black" again...is there some way to get it "black" with brush too ?
Maybe I searched wrong keywords or just didnt know what to search, but I didnt find anyone asking about this problem.
Thanks

Looking at your screenshot, I think it may be because you have your color settings to "Grayscale Slider". If you are working on this image for the web you can change the color settings to "RGB Slider" or "CMYK Slider", for example. Basically, as long as you have it set on "Grayscale Slider" you will only get grayscale colors.
You can change this setting by clicking the dropdown in the Color tab in the upper right side of your screen. See image below. Let me know if this helps.

How to use auto numbering with ENG_ECO_PUB.PROCESS_ECO (EBS version 12.1.1)

Hi All,
I'm trying to create a new ECO using the PL/SQL API "ENG_ECO_PUB.PROCESS_ECO". I want the ECO name to be automatically assigned by the system but when leaving the ECO_NAME empty (in paramter P_ECO_REC) I get the error message:
"You must enter an ECO name and organization because they are the primary identifiers of a business object. Please ensure that these values exist in all your records and re-run the import process."
I have set the profile option "ENG: Change Order Autonumbering - System Administrator access" to yes.
I have set following fields in P_ECO_REC:
p_eco_rec.organization_code := 'V1';
p_eco_rec.change_type_code := 'ECO';
p_eco_rec.description := 'Test';
p_eco_rec.transaction_type := 'CREATE';
p_eco_rec.plm_or_erp_change := 'ERP'; -- also tried with 'PLM'
p_eco_rec.approval_status_name := 'Approved';
Do I need to set anything else?
Thanks,
Carolin

Hi Helios,
thanks for reply.
I checked note 1242524.1, but there's no advice what to configure for using auto numbering.
I tried it again with adapted sample code and leaving the ECO_NAME empty:
DECLARE
-- API Input variables
l_eco_name VARCHAR2(9) := '';
l_org_code VARCHAR2(3) := 'V1';
l_rev_item_number VARCHAR2(20):= 'CS_Test_Assem_10';
l_eff_date DATE := '8-SEP-2011';
l_new_revised_item_revision VARCHAR2(2) := 'A';
l_eco_rec Eng_Eco_Pub.Eco_Rec_Type := Eng_Eco_Pub.g_miss_eco_rec;
l_eco_revision_tbl Eng_Eco_Pub.Eco_Revision_Tbl_Type := Eng_Eco_Pub.g_miss_eco_revision_tbl;
l_revised_item_tbl Eng_Eco_Pub.Revised_Item_Tbl_Type := Eng_Eco_Pub.g_miss_revised_item_tbl;
l_rev_component_tbl Bom_Bo_Pub.Rev_Component_Tbl_Type := Eng_Eco_Pub.g_miss_rev_component_tbl;
l_sub_component_tbl Bom_Bo_Pub.Sub_Component_Tbl_Type := Eng_Eco_Pub.g_miss_sub_component_tbl;
l_ref_designator_tbl Bom_Bo_Pub.Ref_Designator_Tbl_Type := Eng_Eco_Pub.g_miss_ref_designator_tbl;
l_rev_operation_tbl Bom_Rtg_Pub.Rev_Operation_Tbl_Type := Eng_Eco_Pub.g_miss_rev_operation_tbl;
l_rev_op_resource_tbl Bom_Rtg_Pub.Rev_Op_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_op_resource_tbl;
l_rev_sub_resource_tbl Bom_Rtg_Pub.Rev_Sub_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_sub_resource_tbl;
-- API output variables
x_eco_rec Eng_Eco_Pub.Eco_Rec_Type := Eng_Eco_Pub.g_miss_eco_rec;
x_eco_revision_tbl Eng_Eco_Pub.Eco_Revision_Tbl_Type := Eng_Eco_Pub.g_miss_eco_revision_tbl;
x_revised_item_tbl Eng_Eco_Pub.Revised_Item_Tbl_Type := Eng_Eco_Pub.g_miss_revised_item_tbl;
x_rev_component_tbl Bom_Bo_Pub.Rev_Component_Tbl_Type := Eng_Eco_Pub.g_miss_rev_component_tbl;
x_sub_component_tbl Bom_Bo_Pub.Sub_Component_Tbl_Type := Eng_Eco_Pub.g_miss_sub_component_tbl;
x_ref_designator_tbl Bom_Bo_Pub.Ref_Designator_Tbl_Type := Eng_Eco_Pub.g_miss_ref_designator_tbl;
x_rev_operation_tbl Bom_Rtg_Pub.Rev_Operation_Tbl_Type := Eng_Eco_Pub.g_miss_rev_operation_tbl;
x_rev_op_resource_tbl Bom_Rtg_Pub.Rev_Op_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_op_resource_tbl;
x_rev_sub_resource_tbl Bom_Rtg_Pub.Rev_Sub_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_sub_resource_tbl;
-- Other API variables for return status / error handling / debugging
l_error_table Error_Handler.Error_Tbl_Type;
l_return_status VARCHAR2(1) := NULL;
l_msg_count NUMBER := 0;
l_output_dir VARCHAR2(500) := 'C:\temp';
l_debug_filename VARCHAR2(60) := 'su_debug_10_15.dbg';
-- WHO columns
l_user_id          NUMBER := -1;
l_resp_id          NUMBER := -1;
l_application_id     NUMBER := -1;
l_row_cnt          NUMBER := 1;
l_user_name          VARCHAR2(30) := 'MFG';
l_resp_name          VARCHAR2(30) := 'MFG_AND_DIST_SUPER_USER_APS';
BEGIN
-- Get the user_id
SELECT user_id
INTO l_user_id
FROM fnd_user
WHERE user_name = l_user_name;
-- Get the application_id and responsibility_id
SELECT application_id, responsibility_id
INTO l_application_id, l_resp_id
FROM fnd_responsibility
WHERE responsibility_key = l_resp_name;
FND_GLOBAL.APPS_INITIALIZE(l_user_id, l_resp_id, l_application_id); -- Mfg / Mfg & Dist Mgr / INV
dbms_output.put_line('Initialized applications context: '|| l_user_id || ' '|| l_resp_id ||' '|| l_application_id );
Error_Handler.Initialize;
l_return_status := NULL;
l_eco_rec.eco_name := l_eco_name;
l_eco_rec.organization_code := l_org_code;
l_eco_rec.change_type_code := 'ECO';
l_eco_rec.eco_department_name := NULL;
l_eco_rec.priority_code := NULL; --'Medium';
l_eco_rec.approval_list_name := NULL; --'SU_ONLY';
l_eco_rec.reason_code := NULL;
l_eco_rec.Approval_Status_Name:= 'Approved'; -- will default to Not submitted for Approval
l_eco_rec.Status_Name := 'Open';
l_eco_rec.description := 'ECO - '||l_eco_rec.eco_name||' API Test';
l_eco_rec.transaction_type := 'CREATE';
l_eco_rec.plm_or_erp_change := 'ERP'; -- or 'PLM'
l_eco_rec.return_status := NULL;
dbms_output.put_line('Initialized ECO Header');
l_revised_item_tbl(l_row_cnt).eco_name := l_eco_name;
l_revised_item_tbl(l_row_cnt).organization_code := l_org_code;
l_revised_item_tbl(l_row_cnt).revised_item_name := l_rev_item_number;
l_revised_item_tbl(l_row_cnt).new_revised_item_revision := l_new_revised_item_revision;
l_revised_item_tbl(l_row_cnt).start_effective_date := l_eff_date;
l_revised_item_tbl(l_row_cnt).alternate_bom_code := NULL;
l_revised_item_tbl(l_row_cnt).status_type := 1; -- 'Open'
l_revised_item_tbl(l_row_cnt).change_description := 'Test';
l_revised_item_tbl(l_row_cnt).transaction_type := 'CREATE'; -- transaction type : CREATE / UPDATE
dbms_output.put_line('Initialized ECO revised items');
-- Add RS_BOM_C3, acd_type = 1
l_rev_component_tbl(l_row_cnt).eco_name := l_eco_name;
l_rev_component_tbl(l_row_cnt).organization_code:= l_org_code;
l_rev_component_tbl(l_row_cnt).revised_item_name := l_rev_item_number;
l_rev_component_tbl(l_row_cnt).new_revised_item_revision := l_new_revised_item_revision;
l_rev_component_tbl(l_row_cnt).start_effective_date := l_eff_date;
l_rev_component_tbl(l_row_cnt).operation_sequence_number := 1;
l_rev_component_tbl(l_row_cnt).component_item_name := 'CS_Sub_Item_10_D'; -- Add RS_BOM_C3
l_rev_component_tbl(l_row_cnt).alternate_bom_code := NULL;
l_rev_component_tbl(l_row_cnt).acd_type := 1;
l_rev_component_tbl(l_row_cnt).item_sequence_number := 40; -- new item sequence number
l_rev_component_tbl(l_row_cnt).quantity_per_assembly := 5;
l_rev_component_tbl(l_row_cnt).transaction_type := 'CREATE'; -- transaction type : CREATE / UPDATE
-- Change RS_BOM_C1, acd_type = 2
l_row_cnt := l_row_cnt + 1;
l_rev_component_tbl(l_row_cnt).eco_name := l_eco_name;
l_rev_component_tbl(l_row_cnt).organization_code:= l_org_code;
l_rev_component_tbl(l_row_cnt).revised_item_name := l_rev_item_number;
l_rev_component_tbl(l_row_cnt).new_revised_item_revision := l_new_revised_item_revision;
l_rev_component_tbl(l_row_cnt).start_effective_date := l_eff_date; -- effective date
l_rev_component_tbl(l_row_cnt).operation_sequence_number := 1;
l_rev_component_tbl(l_row_cnt).component_item_name := 'CS_Sub_Item_10_B'; -- Change qty for RS_BOM_C1
l_rev_component_tbl(l_row_cnt).alternate_bom_code := NULL;
l_rev_component_tbl(l_row_cnt).acd_type := 2;
l_rev_component_tbl(l_row_cnt).old_effectivity_date := to_date('29-APR-2011 10:09:38', 'dd-MON-yyyy hh24:mi:ss'); -- old effectivity date from bill
l_rev_component_tbl(l_row_cnt).old_operation_sequence_number := 1; -- old operation sequence number from bill
l_rev_component_tbl(l_row_cnt).item_sequence_number := 20;
l_rev_component_tbl(l_row_cnt).quantity_per_assembly := 5; -- existing comp qty on Bill = 2
l_rev_component_tbl(l_row_cnt).transaction_type := 'CREATE'; -- transaction type : CREATE / UPDATE
-- Disable RS_BOM_C2, acd_type = 3
l_row_cnt := l_row_cnt + 1;
l_rev_component_tbl(l_row_cnt).eco_name := l_eco_name;
l_rev_component_tbl(l_row_cnt).organization_code:= l_org_code;
l_rev_component_tbl(l_row_cnt).revised_item_name := l_rev_item_number;
l_rev_component_tbl(l_row_cnt).new_revised_item_revision := l_new_revised_item_revision;
l_rev_component_tbl(l_row_cnt).start_effective_date := l_eff_date;
l_rev_component_tbl(l_row_cnt).disable_date := l_eff_date + 2; -- disable date is 2 day from effective_date
l_rev_component_tbl(l_row_cnt).operation_sequence_number := 1;
l_rev_component_tbl(l_row_cnt).component_item_name := 'CS_Sub_Item_10_C'; -- disable RS_BOM_C2
l_rev_component_tbl(l_row_cnt).alternate_bom_code := NULL;
l_rev_component_tbl(l_row_cnt).acd_type := 3;
l_rev_component_tbl(l_row_cnt).old_effectivity_date := to_date('29-APR-2011 10:09:38', 'dd-MON-yyyy hh24:mi:ss'); -- old effectivity date from bill
l_rev_component_tbl(l_row_cnt).old_operation_sequence_number := 1; -- old operation sequence number from bill
l_rev_component_tbl(l_row_cnt).transaction_type := 'CREATE'; -- transaction type : CREATE / UPDATE
dbms_output.put_line('Initialized ECO revised components');
-- call API to create eco
DBMS_OUTPUT.PUT_LINE('=======================================================');
DBMS_OUTPUT.PUT_LINE('Calling Eng_Eco_PUB.Process_Eco API');
Eng_Eco_PUB.Process_Eco( p_api_version_number => 1.0
, p_init_msg_list => TRUE
, x_return_status => l_return_status
, x_msg_count => l_msg_count
, p_bo_identifier => 'ECO'
, p_eco_rec => l_eco_rec
, p_eco_revision_tbl => l_eco_revision_tbl
, p_revised_item_tbl => l_revised_item_tbl
, p_rev_component_tbl => l_rev_component_tbl
, p_ref_designator_tbl => l_ref_designator_tbl
, p_sub_component_tbl => l_sub_component_tbl
, p_rev_operation_tbl => l_rev_operation_tbl
, p_rev_op_resource_tbl => l_rev_op_resource_tbl
, p_rev_sub_resource_tbl => l_rev_sub_resource_tbl
, x_eco_rec => x_eco_rec
, x_eco_revision_tbl => x_eco_revision_tbl
, x_revised_item_tbl => x_revised_item_tbl
, x_rev_component_tbl => x_rev_component_tbl
, x_ref_designator_tbl => x_ref_designator_tbl
, x_sub_component_tbl => x_sub_component_tbl
, x_rev_operation_tbl => x_rev_operation_tbl
, x_rev_op_resource_tbl => x_rev_op_resource_tbl
, x_rev_sub_resource_tbl => x_rev_sub_resource_tbl
, p_debug => 'Y'
, p_output_dir => l_output_dir
, p_debug_filename => l_debug_filename
dbms_output.put_line('x_eco_rec.eco_name:'|| x_eco_rec.eco_name );
dbms_output.put_line('x_eco_rec.org_code:'|| x_eco_rec.organization_code);
DBMS_OUTPUT.PUT_LINE('=======================================================');
DBMS_OUTPUT.PUT_LINE('Return Status: '||l_return_status);
IF (l_return_status <> FND_API.G_RET_STS_SUCCESS) THEN
dbms_output.put_line('x_msg_count:' || l_msg_count);
Error_Handler.GET_MESSAGE_LIST(x_message_list => l_error_table);
DBMS_OUTPUT.PUT_LINE('Error Message Count :'||l_error_table.COUNT);
FOR i IN 1..l_error_table.COUNT LOOP
DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||l_error_table(i).entity_index||':'||l_error_table(i).table_name);
DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||l_error_table(i).message_text);
END LOOP;
END IF;
DBMS_OUTPUT.PUT_LINE('=======================================================');
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('Exception Occured :');
DBMS_OUTPUT.PUT_LINE(SQLCODE ||':'||SQLERRM);
DBMS_OUTPUT.PUT_LINE('=======================================================');
RAISE;
END;
But with this example I again get same error message...
Any idea?
Thanks,
Carolin

Prevent Agents from disabling Headset Button hen using Auto Answer With Headset

Help!!!
When you enable "Auto Answer with Headset" an agent can still press the Headset button and break that function. Is there a way to keep the agent from being able to disable the Headset button on the phone (Cisco IP Phone 7962g) while maintaining the ability to force Auto Answer with Headset??
Thanks for any ideas!

Hi,
It sounds more like training or organizational issue. If agents do it accidentally, usually this behavior disappeas in a couple of days (if agents were using other phones). And if they do it on-purpose, then supervisors should take care for this issue.
Technically this issue may be resolved by placing some kind of plastic cap over the headset button, but then you should have a mechanism to activate a headset button, if it was deactivated (for excample, afther the phone reboots).
Alternatively you may use longer cord and place the phone out of reach (not exactly "far-far away", but at least out of the hand reach. Plus, depending on the CallCenter software you use, agent may never need touch a phone, in most cases all interaction happens on the PC.
Good luck,
Mike / CCNP, CCVP, CCSP, CCDP, MCSE, CCIE Voice (written), etc.
Headset Adapters for Cisco IP Phones

Using Auto Fill with web sites often used

How do I turn on the "Auto Fill" Name and Pass Word, For a site I previously stated " Never for this site?
So that I can quickly access the site without filling in all the details when ever I wanty to use the site.

Try the Tiny Menu extension. I am using an older version of Tiny Menu on Lucid with Firefox 3.6.x and it works fine.

How to use auto increment with "nchar" data type

Hello
I have a table that I want the value in one column to be generated automatically with "T-XXX" pattern which
"XXX" is a number. Can Microsoft SQL Server do that?

Hello,
Not directly.
You could use an integer column with "Identity" and then add a calculated column to generate the required pattern, like
'T' + convert(varchar, YourIntColumn)
Olaf Helper
[ Blog] [ Xing] [ MVP]

Using 'Auto-Tune' with Final Cut Express HD...

Is it possible to use the program 'Auto Tune' (or a similar program) to correct the pitch imperfections on an audio track of an AIFF file - then re-import it into the audio track of a Final Cut Express HD project?
Thanks,
Jim

I have never used such a program, but it stands to reason that this should work as long as you export it from the program to a FCE-friendly format.

Using Auto-Install with Cisco 2504 WLC

I have a config file that would like to deploy to multiple 2504 controllers.
I am trying to get Auto-Install to upload my config file but I keep getting the 'no interfaces registered' message.
I have my config file on the root of the tftpd32 folder and have TFTP and DHCP servers enabled.
Any ideas what could be causing this?
Thanks

Did you configure DHCP option 150, so that the WLC knows where to find the TFTP server? This should be possible in tftp32.
See for more info this document, it is kinda aged but still accurate.

Lethargic adjustment brush with auto mask on

Hello everyone ...
I am a new to this forum. I've been hanging out as an observer and have decided to get my feet wet with my first posting.
I'm a wedding photographer and have been a Lightroom user since the first beta release and totally love the program. I am using a mac G5 dual 2.7 with 6 GB of ram. Up until release 1.4 Lightroom has been great.
Release 2.0 has been another story. I have installed all updates including the newly released 2.1. It appears there is still an issue with the adjustment brush. If I use the brush without 'auto mask' the brush flows smoothly. As soon as 'auto mask' is engaged the tool becomes useless. The flow is slow and choppy, plus I have to contend with an almost constant spinning beach ball.
Has anyone else been experiencing this problem? Is there a fix? Or, might this be an issue that Adobe is still working on.
Sorry for the long post, just wanted to introduce myself and any help with this issue would be most appreciated.
Thanks ... Fred

From the Known Issues sections of the release notes:
>We are still working on additional methods to improve the performance of the new Localized Correction features.
As you've already observed, leaving the Auto Mask off is the best way of avoiding poor brush performance.

Fuzziness slider for Auto-Mask

The number one way I wreck my images in LR is by using automask with the adjustment brush, and getting harsh transitions where LR decides that a color changes, instead of recognizing it as a gradient, as in the case where an object is partially lit and partially in shadow.
A fuzziness slider could allow the user to adjust fuzziness by Hue or brightness, and thus avoid these ugly transitions.

>As it is now, it's not a feature that is usable, in my opinion.
Then I would argue you STILL do not know how to USE the Auto Mask (and when for what purpose).
The guy who originally worked on Auto Mask was the same guy who wrote the Background Eraser for Photoshop. They operate in a similar manner. What YOU need to do is practice to get the right combination of brush size, feather & flow so you can keep the cursor center always in the color you wish to mask while working the size, feather & flow to already help minimize the amount of cut back that Auto Mask has to do. You also need to work zoomed in enough to localize whatever are you are working on. If you use it correctly, you can produce a remarkably accurate mask but then the question is, what are ya gonna do with it?
There are limits to the strength of the change you can apply in the parameters. You can't paint in a deep blue sky if the sky was burned out to nothing. Using Auto Mask to subtly adjust specific areas that have a substantial difference in tone or color is very easy to do well with practice. And that's all this tool was designed to do.
Camera Raw ain't Photoshop. There are limits to what you can (and WANT to do) in Camera Raw vs. Photoshop. If you need to very accurately mask an area for substantial modification, I wouldn't even bother trying to do it in Camera Raw. If you need to tweak areas that already have enough difference in tone and color to give Auto Mask the teeth to bite into it, sure, go right ahead. In either case, you need to know the tools well enough to know when to use which for what task.
But, proclaiming the tool unusable is a pretty good way of assuring that you will NEVER know how to use itwhile the rest of us learn how and when to use it and therefore benefit from something you gave up on.

Soft Mask with Type 1 (Function-based) Shading

I want to use a custom function as the soft mask - Type 1 (Function-based) Shading
But a function, does not generate alpha to be used with SMask, so my questions are
Is there a way to make a Type 1 (Function-based) Shading to return alpha?
Is there a way to transfer R, G or B layer into alfa?
If not, sould I use Soft mask with Luminosity?
Any examples somewhere of using functions as soft masks (with alpha or luminosity types)?
Thank you!

You should be able to do that just fine by using a standard alpha-based soft mask. Use a DeviceGray-based shading and you should be fine.

Reset the Previous Import catalog when using auto import

I'm using auto import with a watched folder to add scanned slides to a new catalog. Works fine. My question is about the Previous Import "catalog" that new imports are automatically added to. I had thought that this catalog would be reset after each session (i.e. after closing and restarting LR), but it never resets and still shows every slide that I've automatically imported over the last couple of weeks. Is there any way to clear or reset this?
I'm using LR3.3

Unfortunately, the Previous Import count cannot be reset without deleting the previous import from the catalog. Silly? Yes!
Also, Previous Import only records the number of files imported during the last import (i.e. via import window, auto import or import from catalog), not the total number of images previously imported. So, I'm not sure why you're getting your total shows the sum of all previous imports.

Mask with Shape

Hi there.
I'm really excited to use the "mask with shape" feature in iWeb for some photos. Can anyone tell me if this is supported by all browsers on mac and windows platforms?
thanks!
Message was edited by: timpalin
Message was edited by: timpalin

Welcome to the Apple Discussions. You might try a method that Koeklin introduced to us for converting photos with reflections, drop shadows, etc. to a simple JPEG file that event the lowest IE can render correctly.
I created a tutorial on his method: #7 - Converting Photos w/Frames, Drop Shadows and/or Reflections into a Single JPG Image. It should also work for Mask with Shapes objects. It will also help "lighten" the page so it will load faster.
OT

Use brush mask with another adjustment brick?

Hi. I'm pretty sure this is not possible, but I want to make sure and find out if anyone has a work-around.
Is there any way to re-use a mask created for one adjustment brick with another?
This would, IMHO, double the usefulness of the program. (I can't really understand why it is not included.)

You cannot from within Aperture but you can... if you feel like going into the guts of the library. The brush masks are stored as simple tiff files if you create and adjustment and brush any old mask the tiff file will be created - copy the mask you want to the same file name as the mask you just created and viola = reused mask. Not a simple and easy solution.
Much easier just to use PS IMO
RB

LR3.3 adjustment brush auto mask problem

I appreciate any and all help with this issue.
When I use the adjustment brush in LR 3.3 with the auto mask selected I get a speckled result. If I deslect the auto mask it works fine. I was hoping that 3.3 update would fix the issue but no luck.
My OS is Vista 64bit
thanks for your time.
Dave

+1 vote.
Auto-mask has great potential, but is not quite there yet...
I'd like to see a little more control - what exactly you are trying to mask, and what not... - ya now: some tolerances/thresholds for color and luminosity and texture... - and maybe the ability to enhance the edges after the fact.
R

Using Auto Mask with brush

Similar Messages

Maybe you are looking for