Thanks Blake for another amazing video on what to do and why. I really do not know if you are a better teacher, a better PS expert, or a better artist. Hmmm....maybe all three rolled into one. I know now when and when not to use Smart Objects and what the reasons are.
Wow! Thanks so much! I feel like the artist in me is sacrificing for the others, but I get a lot of joy watching other people grow. It, for me, is more rewarding.
Great explanation! Perfect. The moral of the story is that if you, as the photographer and editor, put a little thought into what you already have (in terms of the raw image from your camera) and what you want to ultimately create (in terms of combining camera raw and photoshop editing) then that MENTAL IMAGE will guide you as to what type of layers (smart vs dumb) and edits you need to use. It is case by case. Based on your vision. If on the other hand you do not have any mental image, or creative plan/idea, and instead are just going to rely on randomly moving sliders and adjustments around until you happen to see something you like, then maybe going all smart objects all the time will give more chances to go back and play around some more until some good random thing happens. The biggest benefit of smart objects is being able to LINK to them if they are a reusable resource for many files. The most obvious example being a single, editable watermark file linked to many others as a smart object.
Hi, I just discovered your channel and would like to say thank you so much for the content. I have one question with regard to smart objects and layers etc. I have a photoshop document with numerous layer some of which are smart objects, however when I flatter or merge the layer I lose the effects that I have created. Please could you tell me what I may be doing wrong? Thanks in advance Jim
Alternatively, you can convert a Smart Object from 'embedded' to 'linked' in the object layer's context menu. PS will then ask you to save the NEF with a new file name (and/or location), to protect from changes to the original NEF file. It becomes important to keep the relative path from the PSD to the linked NEF consistent. This would keep your file sizes smaller. This is similar to how PS handles video layers, so not uncomfortable to those with video workflow experience. (Would also be nice if ACR offered 'Open object as linked...' and 'Open object as embedded...').
For sure, great tip. But actually the smart object as a raw file doesn't add too much to file size. It's when you convert pixel layers, like duplicate copies, to smart objects, that's when file size gets out of control.
RAW workflow: I like to keep the RAW adjustments handy early on, when I’m doing the basic tonal adjustments. You’re right that after you’ve got a huge stack of adjustment layers, going back to the RAW file could have unintended consequences, but it’s still useful earlier in the workflow. File size is not an issue for me because I flatten my files when I’m finished working on them.
@@marcelofarah8657 I don’t flatten until I’m finished and ready to move on. “Art is never finished, just abandoned.” If I go back to an image later, I’d rather start from a clean slate rather than reverse engineer what I was doing weeks earlier.
Smart object from camera raw can be quite handy when working with infrared, in my opinion. It gives me the ability to better adjust white balance and some other factors early in the process Plus I've sometimes added a Nik collection filter to the base layer, instead of having it created as a new layer on top, that i then need to delete and recreate if i spot a mistake
A quick question. When you open a image as a smart object in photoshop, this image still a raw file? Because I think photoshop only read image files and not data files. Is this correct?
Make up your mind Blake - do you like them or not? :P Just kidding, thank you for another instructive video. I do agree with your point here, that file size is a big point against using Smart Objects and while the storage is cheap now, I still don't feel well seeing these big fat files :)
the hilarious part here is that I stopped the video just to read the blackboard - After a minute or so looking at it I was like "dude whatcha doin? Keep watchin!"
Wow. Surprised you have not gotten a lot of feedback when you said you would ‘let her use smart objects cause she looks smart’. I think there are a lot of men that use smart objects that are not so smart 😂
You make a very good case for the pros and cons of using smart objects, Blake! Your demonstrations are so helpful to see what you are talking about.
Thanks! I think they are very useful when used for a purpose 😁
As always, great video Blake!
Glad you enjoyed it!
Thanks for the info!
Any time!
Clearly presented. I knew all the parts but you put it together perfectly. Thank you
Glad it was helpful!
Thanks, good info, very useful!
That was very informative Blake. Nothing new about being informative from your videos. I really appreciate your tutorials. Thank You
Thanks so much! I love doing this stuff!
Blake, great lesson...thanks for the comparison...
Glad you liked it!
Thanks!!! I can't tell you how often I've asked why would you not make everything a smart object. You've answered my question.
😁
I might have to tell you every video until I'm totally done with the course how great your Photoshop course actually is. It's amazing.
Wow, thanks! So glad to hear that :)
Thank you, thank you, thank you for sharing this information. I really had no clue what a smart object even was; this is so helpful.
So glad! I appreciate the feedback and I am just glad I can help :)
Thanks Blake for another amazing video on what to do and why. I really do not know if you are a better teacher, a better PS expert, or a better artist. Hmmm....maybe all three rolled into one. I know now when and when not to use Smart Objects and what the reasons are.
Wow! Thanks so much! I feel like the artist in me is sacrificing for the others, but I get a lot of joy watching other people grow. It, for me, is more rewarding.
Great explanation! Perfect.
The moral of the story is that if you, as the photographer and editor, put a little thought into what you already have (in terms of the raw image from your camera) and what you want to ultimately create (in terms of combining camera raw and photoshop editing) then that MENTAL IMAGE will guide you as to what type of layers (smart vs dumb) and edits you need to use.
It is case by case. Based on your vision.
If on the other hand you do not have any mental image, or creative plan/idea, and instead are just going to rely on randomly moving sliders and adjustments around until you happen to see something you like, then maybe going all smart objects all the time will give more chances to go back and play around some more until some good random thing happens.
The biggest benefit of smart objects is being able to LINK to them if they are a reusable resource for many files. The most obvious example being a single, editable watermark file linked to many others as a smart object.
Excellante!!
tyvm
oh that was really helpful thanks
My pleasure!
Hi, I just discovered your channel and would like to say thank you so much for the content. I have one question with regard to smart objects and layers etc. I have a photoshop document with numerous layer some of which are smart objects, however when I flatter or merge the layer I lose the effects that I have created. Please could you tell me what I may be doing wrong? Thanks in advance Jim
TRUE DAT BLAKE..cheers matey.
:) Thanks for watching!
Alternatively, you can convert a Smart Object from 'embedded' to 'linked' in the object layer's context menu. PS will then ask you to save the NEF with a new file name (and/or location), to protect from changes to the original NEF file. It becomes important to keep the relative path from the PSD to the linked NEF consistent. This would keep your file sizes smaller. This is similar to how PS handles video layers, so not uncomfortable to those with video workflow experience. (Would also be nice if ACR offered 'Open object as linked...' and 'Open object as embedded...').
For sure, great tip. But actually the smart object as a raw file doesn't add too much to file size. It's when you convert pixel layers, like duplicate copies, to smart objects, that's when file size gets out of control.
RAW workflow: I like to keep the RAW adjustments handy early on, when I’m doing the basic tonal adjustments. You’re right that after you’ve got a huge stack of adjustment layers, going back to the RAW file could have unintended consequences, but it’s still useful earlier in the workflow.
File size is not an issue for me because I flatten my files when I’m finished working on them.
I wonder if you have to do some changes after flattening your files, let's say a week later. What would you do?
I usually keep the PSD files of my professional/portfolio work. Most other images I am not too concerned with.
@@marcelofarah8657 I don’t flatten until I’m finished and ready to move on. “Art is never finished, just abandoned.”
If I go back to an image later, I’d rather start from a clean slate rather than reverse engineer what I was doing weeks earlier.
Smart object from camera raw can be quite handy when working with infrared, in my opinion. It gives me the ability to better adjust white balance and some other factors early in the process
Plus I've sometimes added a Nik collection filter to the base layer, instead of having it created as a new layer on top, that i then need to delete and recreate if i spot a mistake
A quick question. When you open a image as a smart object in photoshop, this image still a raw file? Because I think photoshop only read image files and not data files. Is this correct?
Is there a way to do smart object mockups without Photoshop using my own model mockup photos or videos?
possibly, but I need more context. I can't track with what you are asking. Can you describe specific example with more context?
Blake can you actually make a smart object larger than its original size without loosing quality? Thank you!
Unfortunately no. I mean you can make it bigger, but you will still be interpolating if you go larger than the original size.
@@f64Academy Thank you Blake!
Make up your mind Blake - do you like them or not? :P
Just kidding, thank you for another instructive video. I do agree with your point here, that file size is a big point against using Smart Objects and while the storage is cheap now, I still don't feel well seeing these big fat files :)
Lol, I like them for what works for me 😁 how about that?!?
the hilarious part here is that I stopped the video just to read the blackboard - After a minute or so looking at it I was like "dude whatcha doin? Keep watchin!"
Haha, Good Will Hunting over here... One of my favorite movies.
Can anyone explain why you can’t perform certain functions, such as cloning on a smart object? Is there a practical reason for this?
It's because a smart objects retains all original data it be was made smart from. Therefore you'd have to clone on another layer.
@@f64Academy another reason to not like them😂
Smart objects layer. When more than one filter applied to a layer they all have common mask instead of individual mask for each filter effect.
Yep, that's the only downside
Wow. Surprised you have not gotten a lot of feedback when you said you would ‘let her use smart objects cause she looks smart’. I think there are a lot of men that use smart objects that are not so smart 😂
haha, well lets face it our wives are smarter than us :)