Non-destructive layer mask editing?

I just finished sweetening a mult-layered texture I was creating and suddenly had a thought - I create my texture in overlaid layers so that I can endlessly tweak, and my process is non destructive, but when I create layer masks for each layer, those have to be edited destructively... so I dupe layers in case I decide I want to go back. This makes for lots of extra backup layers.
So - is there some clever way of non-destructively editing a layer mask? It sounds kinda crazy, but would be super cool if there was a feature to have nested layers just for my layer mask.

Well, you could save as alphas, but then you are still doing destructive edits and archiving them. Only now, they are removed from the layers palette, and it would be easier to forget what goes where. If I leave the copies in the layers palette and turn them off, at least I can group in folders or something - I have a clearer picture of what goes with what.

Similar Messages

Bug report: [layer mask] editing colors

Sometimes it appears that the white/black color combination that is automatically selected in layer mask editing may override the selected color combination outside of layer mask editing.
Example:
1) Open Photoshop.
2) Select two colors: white/white.
3) Create two blank documents, each with an empty Layer 1.
4) In one document, add a layer mask to Layer 1. The colors should have been automatically switched to black/white as the layer mask is selected.
5) In this document, use the gradient tool to fill the layer mask with black/white.
6) Switch to the other document, and notice that the color selection is again white/white.
7) In this other document, use the gradient tool to fill Layer 1. Notice that the layer is filled with black/white instead of white/white as selected.
Tested on: PS CS6, Windows 7, 64-bit.

On further testing I think the issue may not be directly related to layer masks at all.
Basically the issue is that the Gradient tool colors don't update to the 'default foreground/background colors' in cases where it seems that they should.
One example of such a case (as illustrated in the original post) is when the Gradient tool keeps the black/white color combo used for a layer mask in a previous document after switching to the current document where a non-masked layer is targeted and the default fg/bg colors have correctly reverted to white/white.
Example:
layer mask targeted in doc1 - notice synchronised Gradient and default fg/bg colors
after switching to non-masked layer in doc2, Gradient is still black/white although default fg/bg colors have reverted appropriately to white/white
Bug or not, it's something I wanted to point out as it seems inconsistent.

Non destructive method to edit clips?

Is there a non destructive way to edit clips? I am creating a multi camera edit, and 2 different but synched channels of audio. What i have been doing up until now is simply using the cut tool for deleting sections of the timeline to show or hide one cameras perspective. Already this has resulted in one big mistake where I accidentally cut video I meant to keep.
Seems to me there must be a better way. Can you simply hide sections of video / audio to get the same effect without permanently deleting them from your timeline?
Thanks in advance.
Using premiere pro CC.

If you right-click on any clip in the timeline, you will see the word "Enable" in the menu that pops up, with a check-mark next to it. Uncheck this and the clip will remain in your timeline but won't be visible (or audible).
Alternatively, if you click the eyeball icon to the left of each video track, this will hide the whole track from view.
Also, for multicamera files that are already synced, if you hightlight them all and right click and select "Nest" this will nest them together. Right click on the nested clip and select "Multi-Camera > Enable." Now you can easily switch between cameras. Not sure what computer you use, but you should be able to do this by just hitting 1 and 2 to move between cameras.

PS CC (since JAN 2014 update) Layer-mask editing causes hangs/crashes

ONLY since JAN 2014 update, PS CC has been hanging/crashing when I paint/edit a layer mask. All may be well at first (or not), but suddenly the display of the mask (or mask overlay on the layer itself, as shown when hitting backslash key) is not shown in full but renders in s-l-o-w-l-y in rectilinear pieces <snapshot below was taken before video card upgraded but is still typical of what I mean>. When I view Windows' Task Manager for PS, I see my CPUs are each working at their upper limits (up to 80+-90+%), varying only by a few points, over a VERY long time... which could be MANY minutes. OR the System has decided PS is Not Responding.
In any case, whenever this happens, it means in all practicality PS CC is not working, so I either kill it or it's crashed.
Now, here's the thing: that VERY file, can immediately be opened in PS CS6 (which I have fortunately kept installed on my computer), and the mask will be as I thought it should be, and I can edit it as I always could, just fine! So it's obviously a PS CC thing, and I do NOT recall this happening prior to the JAN update. It is still a problem after the two subsequent updates.
I have not been able to determine the specific instances when this happens, as it seems to happen whenever I am editing a mask, no matter what size/softness/color brush, what magnification, what view mode, many or few layers, big or small file, etc.
I did upgrade my NVIDIA card (from GeForce GTX 260 [with current driver] to GTX660), just in case it was a factor (maybe kept it from crashing as fast? hard to tell... but it's still an unworkable problem). You can see from my Sys Info shown here from the PS CC Help menu that it should be more than sufficient for any PS CC task, and it's running the latest driver:
Adobe Photoshop Version: 14.2.1 (14.2.1 20140207.r.570 2014/02/07:23:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:14, Stepping:5 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2
Physical processor count: 4
Processor speed: 2664 MHz
Built-in memory: 16379 MB
Free memory: 12453 MB
Memory available to Photoshop: 14697 MB
Memory used by Photoshop: 60 %
Image tile size: 1024K
Image cache levels: 4
Font Preview: Medium
TextComposer: Latin
Display: 1
Display Bounds: top=0, left=0, bottom=1200, right=1920
OpenGL Drawing: Enabled.
OpenGL Allow Old GPUs: Not Detected.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
AIFCoreInitialized=1
AIFOGLInitialized=1
OGLContextCreated=1
NumGPUs=1
gpu[0].OGLVersion="3.0"
gpu[0].MemoryMB=2048
gpu[0].RectTextureSize=16384
gpu[0].Renderer="GeForce GTX 660/PCIe/SSE2"
gpu[0].RendererID=4544
gpu[0].Vendor="NVIDIA Corporation"
gpu[0].VendorID=4318
gpu[0].HasNPOTSupport=1
gpu[0].DriverVersion="9.18.13.3221"
gpu[0].Driver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um"
gpu[0].DriverDate="20131219000000.000000-000"
gpu[0].CompileProgramGLSL=1
gpu[0].TestFrameBuffer=1
gpu[0].OCLPresent=1
gpu[0].OCLVersion="1.1"
gpu[0].CUDASupported=1
gpu[0].CUDAVersion="6.0.1"
gpu[0].OCLBandwidth=1.16816e+011
gpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.40 NVIDIA via Cg compiler"
gpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[16384]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
gpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
gpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
gpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
gpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]
I work on digital-photography files, and use a layer mask in almost every file, so this relatively-recent bug is a big PITA, having to switch back and forth between CS6 and CC!
Until there's a fix... is there a way to roll-back my PS CC version to BEFORE the JAN 15, 2014 update?

I am not qualified to comment on technical issues; I'm just a user whose son in IT is my 'technical support department.' (But he's not much of a PS user.)
I'm pretty sure, however, that all my Prefs were set to the same things BEFORE the Jan 16, 2014 PS CC update as after (unless the update itself changed something I was unaware of... the settings APPEARED to be the same but I can't easily locate my notes of what my Prefs were from long ago).
And they were the same as the PS CS6 I have had installed on this same system for a very long time, with older video card with older driver, with newer driver; newer video card with newest driver, etc. Yet after that CC update, CC has not (until this workaround) worked re 'the masking bug' for me, yet CS6 has always worked just the same.
So I conclude that the only variable (other than the video card upgrade I did in an attempt to solve this and of course those Windows auto-updates) in this scenario IS something to do with PS *CC*, and after Jan 16, 2014.
As for restarting the machine vs. restarting PS, well, PS is the major player of my system, so when I shut that (and LR) down, I might as well 'clean things up' by Restarting. BTW, I am in the habit of closing and reopening PS (CC or CS6) whenever I finish with a file and load another, in order to get back some of that memory which PS never seems to want to let go. (This is not new to the latest versions, I think. My son says it's a 'memory hog'? ;-) ) I track its memory use in Windows' Task Manager and find that seems to let it 'refresh' itself. (See, I told you I'm not a technical person. ;-) ) But I do not think this has anything to do with the bug. Just a quirk of PS. Like when a tool goes all wonky (for example, its little icon becomes just a 'plus' sign even though the tool is still performing correctly, it's telling me, I think, that it would like to be restarted. And that makes it feel all better... I mean, tool icon reappears.)
Anyway... it's up to Adobe to figure out IF and what may be wrong with PS CC -- it still doesn't work for me as I had it configured at first, and I think it should, right? -- and to fix that... PLEASE. SOON.

Brush Tool Error with Layer Masks

I've identified a layer mask bug in Photoshop 14.2.1 for Mac. When working with non-vector layer masks, the brush tool will not paint a darker value than the white level present in the mask. For instance:
when a layer mask is created from the icon at the bottom of the layers window, the mask itself is white, representing full visibility in the masked layer. If you attempt to use the brush tool with 100% black (to actually mask something in the applicable layer), it does not function. I am able to use the paint bucket tool and the pencil tool to fill black in the mask, but not the brush tool. If the mask is 67% grey, and my brush tool is set to 66% grey, it still will not affect the mask; the white level cannot be decreased, only increased with the brush tool. Bug!

Sure. A mask is just a greyscale image and the blending mode is a property of the brush tool not the mask.
It is actually a very useful feature especially for extracting hair. When painting with black/white in overlay mode you can easily clean up the edges without affecting the pure black/white parts of the mask.

How to create a non-destructive luminosity/b&w mask for (de)saturation?

Someone asked me this question: CG renders (created in Modo, Max, Blender, Maya, Vray, Octane, etc) can be made to look more realistic by desaturating the colours in the highlights. It was also requested that this move would be done in 32bpc as well (something that is often required in a CG compositing workflow).
This is easy enough to do: create a selection based on luminosity (or a black and white version of the image), and use that as a layer mask in the Hue/Saturation adjustment layer, and turn down the saturation.
However, this is a destructive action: suppose we want to import an external file as a smart object, and then we need the option to have the file automatically update with any change we make to the original artwork.
In that case we would have to recreate that luminosity mask again and again as well.
Ideally, an update of the external file will result in an automatic update of the entire layer stack.
Now, in Photoline this is easy to do:
Since layer masks behave like regular layers in PL, and layers can be virtually cloned (not unlike smart objects), it is a mere case of cloning the original external file layer twice, and adding adjustment layers. Finally, that one instanced layer is used as a layer mask for the adjustment layer that controls the saturation. Done.
Replacing or editing the original source will then automatically update and cascade the changes through the entire layer stack.
This is a very handy technique to have! Since I teach Photoshop classes, I thought this would also be handy to know how to do in Photoshop, and I tried several methods (clipping masks included), but I cannot seem to achieve the same non-destructive result. Clipping masks do not work with adjustment layers. Groups cannot be used as clipping masks. Layer masks cannot reference a smart object.
I have a feeling there ought to be a reasonably straightforward method to achieve this, but how?
Would anyone have a suggestion how to solve this in Photoshop in a non-destructive way?

csuebele wrote:
I'm still not seeing it. Your example does not have a pixel based layer clipped to the group which is causing my problem. I hope I can explain this. See below. the layers in the group create the "mask". In this case a b&w adjustment layer was added to control how the "mask" is converted to b&w. You can see what these layers look like in the mid section top section of the image. any color showing though is from the very bottom layer, as the group has a blend if on it allowing the shadows to come through. The top image has a curve layer with no adjustment, while the bottom image has a curve layer to clip more of the shadows. You can see this change in the upper right corner of both images. The curves are allowing more of the image to be clipped in the area is masked out on layer "Layer 0 copy 1", as more of the color of the base layer is showing though. However, that b&w areas are suppose to be just the mask and you should see the b&w, just color as seen in the bottom image. However, the curves are not changing the transparency in the areas that have the layer to return the color.
I don’t get it – what good is the pixel Layer ("Layer 0 copy 2") clipped to the Group supposed to do? Don’t you want to use the Mask on an Adjustment?
Edit: Maybe this can help clarify how I suppose the issue would be approached.

I Dislike the Terms "Destructive" and "Non-Destructive" Editing

Some folks in the Photoshop realm use the terms "destructive" and "non-destructive" to describe ways of using Photoshop in which transforms are applied directly to pixel values vs. being applied via layers or smart filters or smart objects or other means.
Do you realize that the term "destructive" is actually mildly offensive to those who know what they're doing and choose to alter their pixel values on purpose?
I understand that teaching new people to use Photoshop in a way that doesn't "destroy" their original image data is generally a good thing, and I'm willing to overlook the use of the term as long as you don't confront me and tell me what I'm doing when I choose to alter pixel values is "wrong" (or when I choose to advise others on doing so).
For that people who claim editing pixel values is "destructive", I offer this one response, which is generally valuable advice, in return:
Never overwrite your original file.
There. The "destruction" has ceased utterly.
It's common sense, really. You might want to use that file for something else in the future.
If you shoot in raw mode with a digital camera, then you actually can't overwrite your raw files. That's a handy side effect, though some don't use raw mode or even start working with digital photographs.
In any case, when you open your image consider getting in the habit of immediately doing File - Save As and creating a .psd or .tif elsewhere, so that you can subsequently do File - Save to save your intermediate results.
There can actually be many advantages to altering pixel values, if you know what you're doing and choose to do so. But sometimes even the most adept Photoshop user might find that a given step created a monster; that's okay, there's a multi-step History palette for going back. I normally set mine to keep a deep history, to give me a safety net if I DO do something wrong, though I tend to use it rarely.
And for those who would tout the disadvantages to editing "destructively", there can be huge disadvantages to doing it "non-destructively" as well... Accumulating a large number of layers slows things down and can use a lot of RAM... With downsized zooms the mixing can yield posterization that isn't really there, or gee whiz, just TRY finding a computer fast enough to use smart filters in a meaningful way. Just the concept of layers, if one hasn't worked out how layer data is combined in one's own mind, can be daunting to a new person!
So I ask that you please stop saying that the "only" or "best" way to use Photoshop is to edit "non-destructively". There are folks who feel that is offensive and arrogant. I think the one thing everyone can agree upon is that THERE IS NO ONE OR BEST WAY TO USE PHOTOSHOP!
You go ahead and do your editing your way. I prefer to do "constructive" editing.
Thanks for listening to my rant.
-Noel
Man who say it cannot be done should not interrupt man doing it.

function(){return A.apply(null,[this].concat($A(arguments)))}
Aegis Kleais wrote:
When you alter image data in a manner that cannot be reverted, you have destroyed it.
Really?
That's one of those things that one is not supposed to question. It just sounds so right!
Problem is, it's insufficient in and of itself, and misleading... It's a rule of thumb that's way too general.
What IS "data" anyway? Arrangement of magnetic spots on a disk? My disk is still whole, so we're not talking about physical destruction here.
One could argue that all the data is all still there in many cases of pixel-value-change editing (e.g., where there has been no resizing). The image file is the same size! Same amount of data.
Upsampling, or making a copy of an image is actually creating more data, not destroying data. Thus there is no general "destruction", but the terms "construction" or "creation" could be used.
But wait, perhaps you're really talking about destroying information, not data... Well...
As it turns out the term "destructive" is still off base. I have altered the information, possibly even adding important information. If I make a copy this is a no brainer. Even if I don't, depending on a person's skill in editing, the altered result could still carry all the original information that was important plus information added by editing, and be quite possibly better for its intended purpose (human consumption) than the image before the edit. That's the goal!
So now we're talking about important information vs. unimportant information. And of course we're talking about fitness for a future purpose.
As with anything, there are multiple ways to get there and multiple ways to interpret the words.
The term "destructive" in my opinion was invented to further someone's agenda.
-Noel

I am unable to click on a layer mask for editing. CS6 OS10.10

I have been working on a file and all of a sudden I am unable to click on a layer mask in order to edit that mask. I am still able to do the following things:
Create a new adjustment layer. When I do this a new mask is formed for that layer and automatically selected for editing. I can edit this mask. As soon as I click off of it I cannot go back to it.
I am able to shift-click and command-click on layer masks and get those options/selections.
I am able to drag an existing mask to a new adjustment layer.
Hide/unhide the mask-overlay
Pretty much everything but click ON the mask and have it selected for editing.
I have tried the following:
Closing and re-opening the file.
Restarting photoshop.
Restarting my computer.
Deleting/recreating the preferences files.
Any insight out there?

I discovered my problem by trying to paint on whatever I was selected on. It laid down the mask overlay. I thought about it and realized that I must have bumped the 'Q' key and put myself in Quick Mask mode.
So now this is here in case anyone else makes this mistake! :-)

Problem editing a layer mask in curves

I am trying to edit a layer mask to add more contrast to it. when i go to curves i cannot see the layer mask channel in the drop down menu in the curves dialoge.
I want to add contrast to a mask for a noise reduction layer.
anyone know what i am doing wrong?

just make sure that the mask is active and not the layer (it should have a border, click on the mask thumbnail if it doesn't) and then go to Image->Adjustments->Curves

Bypassing the non destructive editing for emptying trash

Hey.
I am completey at my wits end over this. I have footage imported to three separate imovie projects. I have to try and combine these on the one timeline. However everytime I try to move anything it tells me I don't have enough memory. Fair enough so I empty the trash but it is restoring no memory to my hard drive or iMovie - From looking this up it seems to be because of the non detructive editing feature but I don't want to go back on any cuts or keep anything I've deleted just in case. I really need the space so I can begin to move clips around again and finish the project. Is there anyway of telling the programme to just empty the trash and ignore the non destructive editing feature?

Then I open a new blank iMovie project. I drag the desired clips to that project and save.
That, too, preserves the total lengths of the underlying media clips.
iMovie 5-6 dropped the ability to trim unwanted parts of the media clips. iMovie 1-4 allowed the user to do this at the expense of a more fragile project structure.
The workaround to trim the media clips is to:
1. export to tape and import back. Pros: preserves separate clips. Cons: clumsy & slow. Occasional dropped frames may make the process lossy.
2. export to Full Quality .dv and import back. Pros: No dropped frames -- truly non-lossy. Faster. Cons: clumsy, you have to manually break clips into scenes after import.
Cons for 1&2: effects are permanently burned into the image.
Regarding #2 see also this import shortcut:
http://www.sjoki.uta.fi/~shmhav/iMovieHD_6_bugs.html#quick_DVimport

Destructive vs. non-destructive editing

If I send a sequence from FCP to a multitrack project in STP it will be a non destructive edit. Once I am in STP I right click on a track and select "Open in Editor" to take out clicks/pops, etc. Does opening this track in the editor from STP now change the edit to a destructive edit? I want to edit everything from my FCP project non-destructively in STP. Does creating a multitrack project in STP and THEN opening a track in the editor in STP change this to a destructive edit or is it still non-destructive?

Hi Brian:
I read the manual to see the difference between destructive and non-destructive editing in STP ...
What is STP?
This forum refers to DVD Studio Pro, the app to author DVDs.
FCP (Final Cut Pro is a non-destructive video edition software.
As far as I know iMovie (Apple entry level video edition software) is a destructive editing tool . . . no matter you can use some tricks to avoid source "destruction" (... I have not used it from some time ago).
Please, clarify your post and you'll get an answer for your problem for sure.

Any way to non-destructively edit in PSE and save edits ?

any way to non-destructively edit in PSE ? or is this only available in CS and LR ....I would like to use Viveza and to be able to save my edits.
thanks

It is the way Apple has chose to deal with external editor edits.... as I have wrote below in various other threads so no one else has to talk to someone for over two hours on the same thing....
Okay.... so after being on the phone with an Apple senior developer for 2 hrs and 29 minutes, the duplicating of originals has been completely intentional.
Basically, in a nutshell, we have lost the ability to revert back to previous versions of a photo. So, KEEP YOUR ORIGINAL!!!!!!!! Once you make an edit in an external editor, there is no going back unless you go back to the original. There is no reversing any edit in an external edit.
It only makes a copy off the original. So, if you make an edit of an edit, you will only have access to the photo where it is after the second edit. The revert to original does not work on external edits.
I gave suggestions on how to make an original automatically hide or be tagged somehow so it can be hidden and also a check before you delete..... I discussed many different ways of going about this (other than reverting to the way '09 worked)... not sure what they will come up with. But, I played around a lot with this new way of editing... and I could give a full scenario of what is happening with your photos as you edit... but, basically, it seems that Apple has met Windows in this '11 upgrade in that if you want to access different steps of a series of edits, you need to make copies as you go.

Non destructive crop preserved when you "Edit in Photoshop"

I hope that there would be an option in the future to crop an image in lightroom, then when you open to "edit in photoshop" the image would be cropped using photoshop new non destructive crop. So that i can tweak color and retouch the whole image then close and i can do final cropping back in LR.

Sometimes, people crop pictures in LR before making many adjustments just to see if the image works, then go on to the next image etc... then batch export to psd or even edit in PS one by one to retouch. Its painstaking to make a virtual copy, reset the crop, export/edit in psd, then copy the original crop from the master raw, then paste it to the psd file. Another way, adobe can make this work is to have an option to have "Edit in Photoshop" command to not apply the crop from LR. Open the full image, then when it imports it back to LR have LR apply the non destructive crop.

Can't select or edit layer mask in CS5.1 extended

In our class, we have photoshop CS5 on MACs
I started a project in class which involves creating a layer mask. I was about done with the mask, but brought it home to finish. I opened the file on my WIN XP running photoshop CS5.1 extended, which I installed this morning. In class I was able to click on the mask to select it, then use the brush to edit the details, painting black or white as needed to refine the edge.
When I brought the .psd file home and opened it in the newer version of Photoshop, it won't allow me to select the mask for editing. I selected the layer then clicked on the mask thumbnail in the layer pallette but didn't see the corner outlines that usually show when the layer thumbnail is selected. When I tried brushing on what I thought was the mask (of the layer selected) I got the pink overlay as is usually seen in quickmask. (fore and background colors were black and white).
Does v5.1 behave differently with masks from v5.0? I didn't change any of the factory default settings and in class it is standard practice to reset to the default when we begin.
any ideas?

sweet. That did the trick Noel.
I didn't turn quickmask on. I just loaded the file from my flash drive and first thing I tried was to select the layer mask. I'll have to try another file to see if PS is starting in quickmask mode itself.
I had an inkling I was in quickmask mode from the pink painting, but hadn't selected it and didn't know about the q hotkey. newbie here just a few weeks into the intro course.
again, thanks for the fast reply. I just might be able to finish this assignment yet tonight.

Non destructive editing

Can any of you go into detail all the premise of non destruction editing in
LR? I mean, in the term in which LR goes about edit file. Does this mean
that the original file can 'never' be affected, changed, etc...? How does
one make sure of this?
I do ensure that I have backups, but I felt that I didn't quite understand
'enough' on Adobe's approach to this.
Any other detail in this matter is much appreciated! Look forward to what
some of you have to say on this! Thanks much!

thanks for the info! <[email protected]> wrote in message news:[email protected].. > You seem to have a "lot" of very basic questions. So, you might be best > spending some time reading the material already provided on the subject > rather than asking other users to do the work for you. See the first > article on the linked page > <a href=http://www.adobe.com/digitalimag/ps_pro_primers.html> > > You should find that some of the other articles address questions you've > already asked, etc

Non-destructive layer mask editing?

Similar Messages

Maybe you are looking for